Connections
Save named profiles per engine, choose TLS modes and driver parameters, and see when a password is stored.
Connections are saved as named profiles. A profile records how to reach the database: host, port, database, user, and TLS setting. It does not record the password.
Saving a profile
- Give the connection a recognizable name.
- Test Connection verifies reachability. Saving the profile stores the password. See Credential storage.
- Each connection remembers the last schema you used. The default database and default schema are a Settings choice (“Default query location”), not a flag on the profile itself.
Test Connection and save use a roughly 10 second connect timeout. That limit is separate from the query timeout. An authentication failure or an unreachable host is reported as a short message that names the user or host.
The connection card shows a Selected chip for the connection in use and a Default chip for the Settings default. The sidebar shows a reachability indicator for the selected connection: Connected or Not connected.
Supported engines
PostgreSQL, MySQL, SQL Server, Oracle, and Db2. Engine-specific trust behavior is covered in Credential storage.
Query plans on Db2 need explain tables. On LUW, create them with:
CALL SYSPROC.SYSINSTALLOBJECTS('EXPLAIN', 'C', CAST(NULL AS VARCHAR(128)), CAST(NULL AS VARCHAR(128))) Without those tables the plan is unavailable.
Transport security
Set TLS with the form’s TLS dropdown. It is not a JDBC property.
PostgreSQL and MySQL use these labels:
- SSL with hostname verification (recommended off localhost)
- SSL certificate verification only (no hostname check)
- SSL encrypt only (no cert check)
- SSL disabled (unencrypted)
SQL Server uses SSL with hostname verification, SSL encrypt only (no cert check), or SSL disabled (unencrypted). Oracle uses TCPS wording, and verified TCPS requires an Oracle wallet location. Db2 offers SSL with hostname verification or SSL disabled (unencrypted).
localhost, 127.0.0.1, and ::1 default to disabled; everything
else defaults to hostname verification.
Driver parameters
Each profile can include custom JDBC driver parameters for servers that require them.