Exasol connection
To access your data in Exasol, create a connection asset for it.
Exasol is an in-memory, column-oriented, relational database management system.
Prerequisite
The Exasol connection requires a JAR file. The Cloud Pak for Data JDBC Driver is available from the Maven repository. Supported Exasol JDBC Driver version: 7.1.4.
See [Importing JDBC drivers]({{ site.data.keyword.swdocs }}/hub/admin/jdbc-drivers.html){: external} in the {{ site.data.keyword.swhub }} documentation for the procedure and required permissions to upload the JAR file to Cloud Pak for Data. Important: By default, uploading JDBC driver files is disabled and users cannot view the list of JDBC drivers in the web client. An administrator must [enable users to upload or view JDBC drivers]({{ site.data.keyword.swdocs }}/hub/admin/post-install-enable-jdbc-upload.html){: external} in the {{ site.data.keyword.swhub }} documentation.
Supported versions
Exasol 7.1 and 8.29.
Create a connection to Exasol
To create the connection asset, you need these connection details:
- Exasol JDBC Driver JAR file
- Database name (optional): If you do not enter a database name, you must enter the catalog name, schema name, and the table name in the properties for SQL queries.
- Fingerprint (optional)
- Hostname or IP address
- Port number
- Username and password
- SSL certificate (if required by the database server)
For Credentials and Certificates, you can use secrets if a vault is configured for the platform and the service supports vaults. For information, see Using secrets from vaults in connections.
Choose the method for creating a connection based on where you are in the platform
- In a project
- Click Assets > New asset > Prepare data > Connect to a data source. See Adding a connection to a project.
- In a catalog
- Click Add to catalog > Connection. See Adding a connection asset to a catalog.
- In a deployment space
- Click Import assets > Data access > Connection. See Adding data assets to a deployment space.
- In the Platform assets catalog
- Click New connection. See Adding platform connections.
Next step: Add data assets from the connection
Federal Information Processing Standards (FIPS) compliance
This connection can be used on a FIPS-enabled cluster (FIPS tolerant); however, it is not FIPS-compliant.
Learn more
Parent topic: Supported connections