Skip to main content

SQL Database

Supported databases​

Via connections and the operators

  • Read Database
  • Write Database
  • Update Database
  • Execute SQL

Altair AI Cloud supports relational database systems offering a fully compliant JDBC driver.

Whitelists​

For the following databases, a subset of drivers are whitelisted:

Altair Graph Studio & Lakehouse​

driverchecksum
altair-graph-21.0.8171.jardf8bfc6bb59f4fe6c09fe9f98c0794e3

Apache Cassandra​

driverchecksum
cassandra-driver-extras-3.11.5.jar7ba1b270f9e62403e751f9e138bc0a5e

Apache Hive​

driverchecksum
hive-jdbc.jar6920f1b68b9c0eabf0e7a2a45f74006d

Databricks​

driverchecksum
DatabricksJDBC42.jar918a96cf1809f5788caa1e150e8d5c27
DatabricksJDBC42.jarc2adb7d313fa26073785e9dee901b09b

Google BigQuery​

Google BigQuery's JDBC driver performance is limited. We recommend using the Google Cloud connector instead, which supports OAuth 2.0 authentication with User Account, Service Account, or Workload Identity Federation protocols.

driverchecksum
GoogleBigQueryJDBC42.jar6ece0c00f0b4395b65b2772ec2951196

HSQLDB​

driverchecksum
hsqldb-2.5.0.jar3d1a26905a82ccb66da8f63efa443b5b
hsqldb-2.6.1.jar855805d373e8ea58e75913ded352338a
hsqldb-2.7.0.jar7a2c69826a293cb7bd67023360f62ecb
hsqldb-2.7.1.jar0d99b8af583b80eb114d9d483300bee5

MonetDB​

driverchecksum
monetdb.jar03ec16f702d64a55b108efdc482ee305
monetdb.jardac7e5b87e62dd843a60d48a7397dc08

MongoDB​

driverchecksum
mongo-java-driver-3.12.14.jar1b5d0f0594fd19a1dc6f83c6f246be35

MSSQL​

driverchecksum
mssql-jdbc-11.2.1.jre11.jar7e5ab3ba6926ade25378cf871e2ae6a8
mssql-jdbc-11.2.3.jre11.jara3979da723792811c5bb8db86102d557
mssql-jdbc-11.2.3.jre11.jar35acf0eb21d67f6e993de82c9922f5a5
mssql-jdbc-12.1.0.jre11-preview.jar7b8e148aa21b10f0f403aff24e82bf96
mssql-jdbc-12.1.0.jre11-preview.jare95a57ed0edbca6644b6b5869a78c6ba
mssql-jdbc-12.2.0.jre11.jardd6efff9a4af32a2114f7c442a917aac
mssql-jdbc-12.2.0.0.jar823b86fbaf6308b2e165418a27ae60ef

MYSQL / MariaDB​

driverchecksum
mariadb-java-client-3.0.7.jar505a77fb9ed11de08a84cd83c090f1dd
mysql-connector-java-8.0.30.jar923639aff48f9a47fa6c7c9025859f5c
mysql-connector-java-8.0.31.jarda96f0f83ff811921c044b8ea407f254
mysql-connector-java-8.0.32.jar3ba9d1a80e33ec5c5d55d752e0a76677

Oracle​

driverchecksum
ojdbc10-19.16.0.0.jar6a1563bd36d3590e55c354f0e73f5025
ojdbc11-21.7.0.0.jare2809f4d4a43cf59ff7fa1137a25d5e6
ojdbc11-21.8.0.0.jar4a5bd2c2ed6843ad2c34d22c2b46d9d2
ojdbc11-21.9.0.0.jar6aaaf331683c4972ada2ce65a03f4380

PostgreSQL​

driverchecksum
postgresql-42.3.3.jard4b8c2d0a3bc36aefb6a165c23498697
postgresql-42.5.1.jarc760d13432898f1225463ac4f85587fb
postgresql-42.5.2.jar33968b135f52c8a5aaf7cbf07f77ce16
postgresql-42.5.3.jar38ae934c5e1e7855081491285fbb4f9f

Redshift​

driverchecksum
redshift-jdbc42-2.1.0.12.jar5642139d76a38c5947d13e9ffe91685d
redshift-jdbc42-2.1.0.13.jar25a732f609c86dccdd19dc2973154b8c
redshift-jdbc42-2.1.0.14.jar8543fa6179d21891e7bb568775315a61

Snowflake​

driverchecksum
snowflake-jdbc-3.13.27.jarc6c15cc4bc870f66ee2fbd99e7c7ddb1
snowflake-jdbc-3.13.28.jarc83ad0878927f76e555d38f4a08bb5a2
snowflake-jdbc-3.13.29.jar5ec06629ac3859bf2d5e157da48e01d5
snowflake-jdbc-3.20.01.jara91e776687ecede6635a655a79ec9cf1

SAP Sybase​

driverchecksum
jtds.jar1b8f4ecce357e0679ecaa102560eb0ca
jtds-1.2.8.jar793d8021b715bdf05fdbc6d46fb8e914
jtds-1.3.0.jara0e43823e84f297f113ec60e33b1feba
jtds-1.3.1.jar079f16ab8ba61a17dfdee426d4392d88

Create a connection​

New database connection

To create a database connection, the following information is required:

  • Connection name - The name you give to the connection
  • System - The choice of database, given in the dropdown list
  • User - The user of the database
  • Password - The user's password
  • URL Prefix - The URL of the database
  • Host -
  • Port - The port on which the database is available, e.g. 5432 for PostgreSQL
  • Database -

Provide additional files for secure authentication​

Typically, you might connect to a database using a username and password. While convenient, this method can be vulnerable to cybersecurity attacks. You can configure hardened authentication using certificates (like .crt, .pem, .jks, or .p12 files).

To configure cert-based authentication, follow these steps:

  1. On the Database Connection configuration screen, open the Driver Settings section.

  2. Click the Import additional libraries button and browse for the certificates you need for the authentication.

  3. Reference the files in your configuration with the %{_internal_files/<filename with extension>} macro.

Database authentication

The same works for Manual JDBC URL configuration too. In that case, the JDBC connection string for the above connection takes the following form:

jdbc:postgresql://example.com:5432/testdb;ssl=1;sslfactory=org.postgresql.ssl.NonValidatingFactory;sslcert=%{_internal_files/cert.crt};sslkey=%{_internal_files/key.pem}

Certificate Authentication for Snowflake Connections​

When configuring a Snowflake connection with certificate authentication in AI Cloud, you must use a private key in PKCS#8 format with PBE-SHA1-3DES encryption.

If you have an existing encrypted PEM private key that needs to be converted to the correct format, follow these steps:

# Step 1: Convert the Private Key. Replace private_key_enc.pem with the path to your existing private key file.
openssl pkcs8 -in private_key_enc.pem -topk8 -v1 PBE-SHA1-3DES -out private_key.p8

# Step 2: Extract the Public Key
openssl rsa -in private_key.p8 -pubout -out public_key.pub

If you need to generate a new key pair from scratch, use the following commands:

# Step 1: Generate the Private Key
openssl genrsa 2048 | openssl pkcs8 -topk8 -inform PEM -v1 PBE-SHA1-3DES -out private_key.p8

# Step 2: Extract the Public Key
openssl rsa -in private_key.p8 -pubout -out public_key.pub