Skip to content

Connect a Data Source in the Data Studio

10 November 2026

  • The Data Studio opens on Data Sources. With the Right “Create Data Sources and Managed Databases”, you connect a database or data warehouse: PostgreSQL and its relatives (Supabase, Amazon RDS and Aurora, Neon, CockroachDB), MySQL and its relatives (MariaDB, PlanetScale, TiDB), SQL Server and Azure SQL, Amazon Redshift, Snowflake or Databricks SQL. See Connect a Data Source.
  • Paste the connection string as you have it: a URL, a JDBC URL, an ADO.NET or ODBC string, libpq’s key=value form, or a psql, mysql or sqlcmd command line. We recognise the database and show it with the host; you can correct it, and we ask when a string fits more than one.
  • A connection string we can’t use is refused with a message that says why and what to paste instead, such as a placeholder still in it or a sign-in that isn’t supported yet.
  • Test connection signs in, checks that the database exists and runs SELECT 1. If it fails, it names the step: the address, the network, the sign-in, TLS or the database. It warns you when the connection isn’t encrypted.
  • Add the CA certificate of a database whose certificate a CA of its own signed, such as Supabase or CockroachDB Cloud, to have it verified.
  • Choose Query tool only or Also in the Sandbox for where the connection string may be used.
  • The dialog lists the fixed addresses our queries come from, to allow on your firewall, and says that the agent can do whatever the database user may do.
  • The connection string and the CA certificate are stored encrypted and never shown again. Adding a Data Source is recorded in the Audit Log.
  • The agent doesn’t query Data Sources yet; that comes next.