--- description: Open a data connection in Studio to check its health, browse its schema, see query stats, re-test it, change its credentials, or delete it. --- # Manage a data connection Each warehouse connection has its own page in Studio, where you can check its health, browse what it exposes, update credentials, and delete it. !!! info "Availability" - **Who can do this:** members with the **Edit** capability in the active Workspace. If **Restrict connection management** is on, editing, re-testing, and deleting also need the **Manage organization** capability. - **Deployment:** Actian SaaS and self-managed deployments. To open a connection, go to **Connections** in Studio and select it under **Warehouses**. You see only connections attached to your current Workspace. See [Data connections and Workspaces](connections-and-workspaces.md). The header has **Edit credentials**, **Re-test connection**, and a trash icon (**Delete connection**). Below it are three tabs: **Overview**, **Schema**, and **Query stats**. ## Overview The **Overview** tab has these sections: - **Connection health**: the latest **Status** (**OK**, **Slow**, or **Failed**), **Last checked**, and **Connect latency**, plus a row of dots with one dot per recent check and a summary line such as "N of M recent checks OK". If no check has run yet, it says "No probe yet. Re-test the connection to record one." See [Data Source Health Monitoring](data-source-health-monitoring.md). - **Connection summary**: the connection's **Name** and **Description (optional)**, which you can edit and save, plus its **Type**, its **Scope** (**Organization** or **This Workspace**), its non-secret settings (such as host, port, database, username, and schemas), **Created**, and **Created by**. Secret values are never shown. - **Workspaces**: which Workspaces can use the connection, or, for a private connection, the option to share it with the organization. See [Data connections and Workspaces](connections-and-workspaces.md). To rename a connection or change its description, edit the field and click **Save**. Names must stay unique: across the organization for an organization connection, or within the Workspace for a private one. ## Connection status A connection is either **Ready** or **Failed**. - It becomes **Ready** when you create it, when a re-test succeeds, or when you save new credentials. - It becomes **Failed** when a re-test fails, or when AI Analyst can't reach the warehouse while browsing it. The page then shows "This connection is unavailable. Re-test or update the credentials." Older connections can occasionally show **Pending setup**. Re-test the connection to update its status. ## Re-test a connection Click **Re-test connection**. Studio tests the saved settings and shows the result above the tabs. If the test fails, the message tells you what went wrong. See [If the test fails](connect-a-data-source/README.md#if-the-test-fails). ## Change credentials Use **Edit credentials** when a password, token, or key changes, or to change the host, schemas, or other connection settings. 1. Click **Edit credentials**. 2. Change the fields. Non-secret settings are prefilled. Secret fields start empty, so re-enter required secrets such as the password. You can also use **Paste a connection string** where the connector offers it. 3. Click **Test connection** and wait for a successful result. The **Schemas** (or, for Databricks, **Catalogs**) picker appears only after a successful test. 4. Click **Save credentials**. You can only save after a successful test, and the test must be less than 5 minutes old. Changing a field after the test clears the result, and ticking or unticking a schema or catalog counts as a change. For connectors that can't enforce read-only access, the dialog shows the same read-only warning as the create form (see [Read-only access and query limits](read-only-access.md)). ## Browse the schema The **Schema** tab lists what the connection exposes. Select a schema, then a table, to see its **Columns** and **Sample data (10 rows)**. On Databricks, select a catalog first. Connectors without schemas list tables directly. - Browsing needs a working connection. If the connection has failed, the tab shows "Browsing the schema needs a working connection. Re-test or update the credentials." - If you see "No tables are visible on this connection", there may be no tables, or the warehouse user may lack access. Check the grants in the connector's setup guide. To expose different schemas, open **Edit credentials**, re-enter the required secrets, and click **Test connection**. Change the selection. This closes the picker and clears the test result, so click **Test connection** again to bring the picker back with your selection kept, then click **Save credentials**. ## Query stats The **Query stats** tab shows **Total queries**, **Error rate**, and **Avg query latency**, plus charts of queries and average latency over time. Choose a **Time range** of **7d**, **30d**, or **3M**. ## Delete a connection !!! warning Deleting a connection also permanently deletes every Model built on it, and every Metric on those Models, anywhere in your organization, including in other Workspaces. Deleted Models and Metrics can't be restored. 1. Click the trash icon (**Delete connection**). 2. Read **Delete data connection?**. Deleting permanently removes the connection and its encrypted credentials. 3. If Models use the connection, the dialog lists them under **Models**, and the Metrics built on them under **Metrics**. Models and Metrics that were already deleted are tagged **Soft-deleted**. They are permanently deleted too. 4. If the dialog lists anything, tick **I understand models and metrics that use this connection will be permanently deleted.** 5. Click **Delete**. When the Models and Metrics go, everything attached to them goes too, such as their version history, Glossary term mappings, and AI Analyst access to them. Every delete is recorded in the [Audit log](../governance/audit-logs.md), including the Models and Metrics it removed. !!! tip To stop one Workspace from using an organization connection without deleting anything, change the connection's Workspaces instead. See [Data connections and Workspaces](connections-and-workspaces.md). ## When management is restricted If a member with **Manage organization** has turned on **Restrict connection management**, members without **Manage organization** see "Data connections are managed by your organization's Admins." on the connection's page. **Edit credentials** and the delete icon are hidden, **Re-test connection** is disabled, and **Name** and **Description (optional)** are read-only. You can still open the connection, browse its schema, and see its query stats.