Exasol

Connectivity Summary

An out-of-the-box connector is available for Exasol databases to support crawling database objects and profiling sample data.

The connectivity to Exasol is via the JDBC driver, which is included in the platform. 

The Exasol versions supported by the connector are mentioned below:

The drivers used by the connector are given below:

Driver / API: Exasol JDBC driver                         

Version: 6.2

Details: Is JDBC 4.2 compliant, uses JDK 8.0

https://www.exasol.com/portal/display/DOWNLOAD/7.0 

Note: Latest version is 7.0.7

Technical Specifications

The following are the connector capabilities mentioned below:

Crawling

Profiling

See this article Profile Data to know more  about Profiling.

Querying

By default, the service account provided for the connector will be used for any query operations. If the service account has to write privileges, then Insert / Update / Delete queries can be executed.

Pre-requisites:

To use the connector, the following need to be available:

• Connection details as specified in the following section should be available.
• An admin/service account with read privileges.
• JDBC driver is provided by default. In case it needs to be changed, add Exasol client drivers into the OvalEdge Jar path to communicate to the Exasol database.
• Check the Configuration section for further details on how to add the drivers to the jar path.

Connection Details

The following are the connection settings that needs to be added for connecting to an Exasol database:

• Database Type: Exasol
• Connection Name: Select a Connection name for the Exasol database. The name that you specify is a reference name to easily identify your Exasol database connection in OvalEdge. Example: Exasol Connection DB1
• Hostname / IP Address: Database instance URL (on-premises/cloud-based)
  Example:exasol.csklygkwz3dx.us-east-1.rds.amazonaws.com
• Port number: 8563
• Sid/Database: Name of the database to connect.
• Username: User account login credential Exasol Authentication
• Password: Password (only for <Exasol> Authentication)
• Driver Name: JDBC driver name for Exasol. It will be auto-populated.
  Example: com.exasol.jdbc.EXADriver
• Connection String:  Exasol connection string. Set the Connection string toggle button to automatic, to get the details automatically from the credentials provided. Alternatively, you can manually enter the string.
  Format: jdbc:exa://{servername}:{portnumber};schema= {sid}
  Example: jdbc:sqlserver://oval-exasol.csklygkwz3dx.us-east-1.rds. amazonaws.com:1433;schema=test

Once connectivity is established, additional configurations for Crawling and Profiling can be specified.

FAQs

1. What should I know when upgrading my driver?
   The Microsoft JDBC Driver 7.4 supports the JDBC 4.2, and 4.3 (partially) specifications and includes three JAR class libraries in the installation package as follows:
   

   JAR	JDBC Specification	JDK Version
   exajdbc-6.0.jar	JDBC 4.2	JDK 8.0

2. How much does the driver cost?
   The Microsoft JDBC Driver for Exasol is available at no additional charge.

3. Can I use the driver to access Exasol from a Linux computer?
   Yes, you can use the driver to access Exasol from Linux, Unix, and other non-Windows platforms.

4. Which authentication types are supported by the Exasol JDBC Driver for Exasol?
   The table below lists available authentication options.

   Platform	Authentication
   Any Platform	Authentication By Password, LDAP/AD, Kerberos/SSO