Connection to SQL Datasources

On this page are instructions on how to configure database clients for SQL databases. If your database type is not in the below list, see our Connect to Non-SQL Databases page.

  • MySQL
  • Aurora MySQL
  • Clustrix
  • MariaDB
  • SingleStore
  • PostgreSQL
  • Aurora PostgreSQL
  • Citus
  • Greenplum
  • Microsoft SQL Server

The Connection Process

  1. Connect to the datasource in your GUI by clicking on its name in the GUI or running sdm connect <name> at the command line.
  2. Ensure that there is a green lightning bolt next to the datasource name in the GUI or the datasource is listed as connected if you run sdm status at the CLI.
  3. Find your preferred database client from the tables below and use the specified parameters to configure the connection. Note that every client is different and if you do not use the correct parameters, the connection will fail! If your client is not listed below, please contact with details.
  4. Initiate the connection within your database client.

GUI Clients

The tables below contain required connection parameters for many popular database GUI clients. Please note that if you are using port overrides or custom ports you may need to change the default database port to the specific port specified in your local GUI, in addition to the hostname field.

If you are connecting to SQL Server, PostgreSQL, or a PostgreSQL derivative (e.g. Greenplum), please see the Database Overrides section below as you may need to specify a specific database to connect to.

MySQL, Aurora MySQL, Clustrix, MariaDB, SingleStore

In some versions of MySQL, you may need to add useSSL=false or the equivalent to your connection parameters.

ClientHostnameUsernamePasswordInitial DBAdditional Settings
DBeaverlocalhostemptyemptyexisting database name
DbVisualizerlocalhostemptyemptyexisting database name
MySQL Workbench127.0.0.1any stringemptyempty
Sequel Pro127.0.0.1emptyemptyempty
SQLPro Studiolocalhostany stringemptyempty
SQLyoglocalhostany stringemptyempty
TeamSQLlocalhostany stringemptyempty
SQL Workbench/Jlocalhostemptyemptyempty

PostgreSQL, Aurora PostgreSQL, Citus, Greenplum

ClientHostnameUsernamePasswordInitial DBAdditional Settings
DataGriplocalhostemptyemptyThe Authentication field should be set as User & Password, not pgpass
Navicat (Mac)localhostany stringemptyempty
Navicat (Windows)localhostemptyemptyempty
pgAdminlocalhostany stringemptyany string
Posticolocalhostemptyemptyexisting database name
SQLPro Studiolocalhostany stringemptyempty
Tableaulocalhostany stringemptyany string
TablePluslocalhostemptyemptyexisting database name
TeamSQLlocalhostany stringemptyany string
SQL Workbench/Jlocalhostany stringany stringempty

Microsoft SQL Server

ClientHostnameUsernamePasswordInitial DBAdditional Settings
Access127.0.0.1any stringemptyempty
Alteryx Designer127.0.0.1any stringany stringemptyUse system ODBC connection and SQL Server 10.x driver
Azure Data Studio127.0.0.1any stringemptyemptySDM port should be separated by a comma (i.e.,11433) and under Advanced... > Security set Trust server certificate to "true"
Excel127.0.0.1any stringemptyempty
Navicatlocalhostany stringemptyempty
SQL Server Management Studio127.0.0.1any stringemptyemptyChange Network Protocol from to TCP/IP, Server Name should be IP address, and SDM port separated by a comma (i.e.,11433)
Tableau127.0.0.1any stringemptyempty
SQL Workbench/Jlocalhostemptyemptyempty

Command-line Clients

Database typeSample connection string with portSample connection string with database*
Microsoft SQL Serversqlcmd -s,portsqlcmd -s -d <database>
mssql-cli -S -U sdm -P sdmmssql-cli -S,port -U sdm -P sdmmssql-cli -S -U sdm -P sdm -d <database>
MySQL, Aurora MySQL, MariaDB, SingleStoremysql -h -P port
PostgreSQL, Aurora PostgreSQL, Citus, Greenplum, Redshiftpsql -h localhost -p portpsql -h localhost -d <database>

Database Overrides

The SQL Server and PostgreSQL datasource types, as well as PostgreSQL derivatives like Greenplum and Redshift, have the option of database overrides. However, this option works differently between SQL Server and PostgreSQL.

Database override enabled


  • When a user connects to the datasource, they will be unable to change databases from the database configured in the datasource.
  • If they try, the command will appear to succeed but they will still be able to query only the original datasource.
  • In this configuration, the user does not need to specify a database when connecting to the datasource via strongDM.

SQL Server

  • When a user connects to the datasource, they will automatically connect to the database specified in the datasource configuration.
  • In this configuration, the user does not need to specify a database when connecting to the datasource via strongDM.

Database override disabled

(This applies to both PostgreSQL and SQL Server.)

  • If this checkbox is not enabled, the user will be able to change databases as normal.
  • In this configuration, the user DOES need to specify a database---any database that is accessible in the datasource---when connecting to the datasource via strongDM.

If you have trouble connecting with your database client, please contact with details.

User Guide — Previous
Connect to Resources
Connect to Non-SQL Databases