Close
logodocs

Connect to Non-SQL Databases

On this page are instructions on how to configure database clients for non-SQL databases. If you use any of the below SQL databases, see the Connect to SQL Databases page.

  • MySQL
  • Aurora MySQL
  • Clustrix
  • MariaDB
  • MemSQL
  • 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 support@strongdm.com with details.
  4. Initiate the connection within your database client.

GUI Clients

The connection matrix below contains 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.

MongoDB

ClientHostnameUsernamePasswordInitial DBAdditional Settings
dbKodalocalhostemptyemptyempty
MongoDB Compasslocalhostemptyemptyempty
Mongotronlocalhostemptyemptyempty
NoSQLBoosterlocalhostemptyemptyempty
Robo 3T (Robomongo)localhostemptyemptyempty

Redshift

See the JDBC Drivers section for information on how to use the Redshift JDBC driver.

ClientHostnameUsernamePasswordInitial DBAdditional Settings
DBeaverlocalhostemptyemptyempty
DataGriplocalhostemptyemptyempty
DbVisualizerlocalhostemptyemptyany string
HeidiSQLlocalhostemptyemptyempty
Navicatlocalhostemptyemptyempty
Posticolocalhostemptyemptyempty
SQLPro Studiolocalhostany stringemptyempty
Tableaulocalhostany stringany stringany string
SQL Workbench/Jlocalhostany stringany stringempty

Snowflake

ClientHostnameUsernamePasswordInitial DBAdditional Settings
DBeaverlocalhostemptyemptyemptyany string as account property and false as SSL property under Driver Properties

Db2 LUW

ClientHostnameUsernamePasswordInitial DBAdditional Settings
DBeaverlocalhostany stringany stringany string
DbVisualizerlocalhostany stringany stringany string

Db2i

ClientHostnameUsernamePasswordInitial DBAdditional Settings
DBeaverlocalhostany stringany stringany stringFrom the Driver Properties settings, portNumber must be set to the SDM port-override value.
DbVisualizerlocalhostany stringany stringany stringLoad a driver compatible with DB2 iseries, such as: jt400-10.4.jar. Once added go to the Driver Properties and set the portNumber to the SDM port-override value.

Sybase ASE, Sybase IQ

ClientHostnameUsernamePasswordInitial DBAdditional Settings
DBArtisanlocalhostany stringany stringempty
DataGriplocalhostany stringany stringempty
Dbeaverlocalhostany stringany stringempty
DBVisualizerlocalhostany stringany stringempty
ERStudiolocalhostany stringany stringempty
RapidSQL127.0.0.1any stringany stringempty
SQL Workbench/Jlocalhostany stringany stringempty

JDBC Drivers

Some JDBC drivers have very specific connection string requirements. When using the below JDBC drivers, we recommend entering the connection string directly. Replace <port> with the configured port. Where it says any you can replace with any string, but a string must be there for proper functionality.

DriverConnection String
Athena (driver versions 2.0.5, 2.0.6)jdbc:awsathena://UseResultsetStreaming=0;ProxyHost=localhost;ProxyPort=port;Protocol=http;AwsRegion=us-any-1;UID=any;PWD=any;S3OutputLocation=s3://any/
jTDSjdbc:jtds:sqlserver://localhost:port/any;user=any;password=any;ssl=request
Redshiftjdbc:redshift://localhost:port/any?ssl=false&UID=any&PWD=any
Snowflakejdbc:snowflake://localhost:port/?account=any&SSL=FALSE

Command-line Clients

Database typeSample connection string with portSample connection string with database*
BigQuerybq --api http://localhost:20000 --disable_ssl_validation ls
Cassandracqlsh localhost port
DynamoDBdynamodb --endpoint-url http://localhost:port
Microsoft SQL Serversqlcmd -s 127.0.0.1,portsqlcmd -s 127.0.0.1 -d <database>
mssql-cli -S 127.0.0.1,port -U sdm -P sdmmssql-cli -S 127.0.0.1 -U sdm -P sdm -d <database>
MongoDBmongo --host localhost --port port
MySQL, Aurora MySQL, MariaDB, MemSQLmysql -h 127.0.0.1 -P port
PostgreSQL, Aurora PostgreSQL, Citus, Greenplum, Redshiftpsql -h localhost -p portpsql -h localhost -d <database>
Redisredis-cli -h localhost -p port
SnowflakeSNOWSQL_PWD=none snowsql -u sdm -a sdm -d <database> -s <schema> -w <warehouse> -h localhost -p port -D protocol=http

See the following section for why you may need to specify a database with these database types

REST API Connections

Some database types allow REST API access---Druid in fact requires it. To connect to these databases, replace the host and port in the URL with localhost and the configured port in strongDM.

Example for Druid: http://localhost:18090/druid/indexer/v1/task

If you have trouble connecting with your database client, please contact support@strongdm.com with details.

Previous
Connection to SQL Datasources
Next
Connecting to SSH