Edit a connection
Open a connection from the Connections list to edit it. On the list, select connections with the row checkboxes and use the Delete action in the bar above the grid to delete several at once. Opening one takes you into the Catalog, which is where connections are edited, so the breadcrumb at the top of the page reads Catalog, then the connection name. Verify and History are both items in the More actions menu at the top right, not buttons of their own.
The connection string is one field
Section titled “The connection string is one field”For SQL Server, Azure SQL Database, and Amazon RDS for SQL Server connections, the server, database, port, user name, and authentication method all roll up into a single connection string. The editor shows that string read-only, with one button above it and the password below it:
- Edit connection string… opens a dialog where you set the host, port, catalog (database), authentication method, and any advanced properties (for example Encrypt or TrustServerCertificate). The dialog has a freeform connection-string box at the top: paste a full string and the individual fields fill in for you.
- Connection string (read-only) is a summary of what you set in the dialog. It never shows the password.
- Password is the one editable secret on the form. Leave it blank when editing an existing connection to keep the stored password unchanged.
Properties you set in the Edit connection string dialog, including Encrypt, Trust Server Certificate, and any additional properties you add, are saved with the connection and shown in the read-only connection string on the connection screen.
The dialog itself also includes a Password field. When you are editing an existing connection it starts blank: leave it blank to keep the current password, or type a new value to replace it. The password is stored separately and never appears in the connection string.
Authentication
Section titled “Authentication”Inside the dialog, Authentication picks how the connection signs in:
- Username and password: the dialog shows a User Name field; the password is the separate field back on the form.
- Entra ID OAuth: the dialog shows Tenant ID and Client ID fields, and the form’s secret field becomes Client secret.
Choosing Windows authentication is not a separate option here. If you need it, add
Integrated Security=SSPI in the dialog’s Additional properties box; it round-trips
through the connection string like any other property.
Pasting a full connection string
Section titled “Pasting a full connection string”Paste a complete connection string, including a password, into the dialog’s connection-string box and commit. The host, database, port, and user name fill in, the password moves into the form’s Password field, and the stored connection string keeps only the non-secret parts. The password is never written into the connection string itself.
Other connectors
Section titled “Other connectors”Databricks, Snowflake, PostgreSQL, MySQL, and Oracle connections, and Azure Data Lake Storage, keep their field-by-field forms: host or workspace URL, catalog, compute, and the credential for the chosen authentication method. There is no connection-string dialog for these.
Source or target platform
Section titled “Source or target platform”One switch decides which way data moves. Turned on, its label reads Source connection and data is extracted from here. Turned off, it reads Target platform connection and data is landed to it.
The record source and Persist history used to sit beside that switch and no longer do. Both are project settings now, in the project editor’s Source options section, and the switch’s own help text says so: a source connection tells you that projects using it set their record source there.
To check the connection actually works, use Verify from the More actions menu. See Verify a connection for the execution modes and troubleshooting.
Delete a connection
Section titled “Delete a connection”Deleting a connection (from its actions menu on the Connections list, or in bulk from the bar above the grid) now removes every catalog, schema, table, and column discovered under it, along with any source-column mappings that pointed at those columns. This is a change from before, when a deleted connection left its catalogs, schemas, tables, and columns behind. The confirmation dialog previews the exact counts it is about to remove, so you know what you are clearing before you confirm.