JDBC Driver

This section describes the JDBC driver provided by Exasol to connect third party applications to Exasol.

System Requirements

JRE Requirement

The JDBC driver requires a Java runtime environment (version 5.0 or later). You can use the driver on any platform with JRE version 7 or later.

Tested Systems

The driver has been tested on the following systems using the specified Java version with the latest available updates.

• Windows 10 (64-bit)

  • Java 1.8.0

  • Java 11.0.11

  • Java 17.0.2
    For Windows systems, Microsoft .NET Framework 4.0 Client Profile™ should be installed on your system. There is an automatic installation wizard for it.

• Linux (64-bit)

  • Red Hat / CentOS 7, OpenJDK JVM 1.8.0

  • Red Hat / CentOS 8, OpenJDK JVM 1.8.0

  • OpenSUSE Leap 15.2, OpenJDK JVM 1.8.0

  • Debian 10, OpenJDK JVM 11.0.12

  • Ubuntu 18.04 LTS, OpenJDK JVM 11.0.13

  • Ubuntu 20.04 LTS, OpenJDK JVM 11.0.13

• macOS (64-bit)

  • macOS Mojave (10.14), JVM 16.0.1

  • macOS Catalina (10.15), JVM 16.0.1

  • macOS Big Sur (11.6.1), JVM 1.8.0

  • macOS Monterey (12.0.1), JVM 1.8.0

• Free BSD (64-bit)

  • Free BSD 12.2, OpenJDK JVM 1.8.0

License

Each driver package includes the latest version of the license for the driver. The license allows you to bundle the driver with third-party software, for example when creating plugins for a BI tool. For more details, refer to the license file which is located in the folder where the driver was installed.

<dependencies>
    <dependency>
        <groupId>com.exasol</groupId>
        <artifactId>exasol-jdbc</artifactId>
        <version>7.0.0</version>
    </dependency>
</dependencies>

Exasol URL

The JDBC Driver uses the following URL structure for Exasol:

jdbc:exa:<host>:<port>[;<prop_1>=<value_1>]...[;<prop_n>=<value_n>]

The following table explains the elements of the URL structure.

Example from a Java program

import java.sql.*;
import com.exasol.jdbc.*;

public class jdbcsample
{
    public static void main(String[] args)
    {
        try { Class.forName("com.exasol.jdbc.EXADriver");
    } catch (ClassNotFoundException e) { 
            e.printStackTrace();
    }
    Connection con=null; 
    Statement stmt=null; 
    try {
        con = DriverManager.getConnection( 
            "jdbc:exa:192.168.6.11..14:8563;schema=SYS",
            "sys", 
            "exasol"
            );
        stmt = con.createStatement();
        ResultSet rs = stmt.executeQuery("SELECT * FROM CAT"); 
        System.out.println("Schema SYS contains:"); 
        while(rs.next())
        {
            String str1 = rs.getString("TABLE_NAME"); 
            String str2 = rs.getString("TABLE_TYPE"); 
            System.out.println(str1 + ", " + str2);
        }
    } catch (SQLException e) { 
        e.printStackTrace();
    } finally {
        try {stmt.close();} catch (Exception e) {e.printStackTrace();} 
        try {con.close();} catch (Exception e) {e.printStackTrace();}
        }
    }
}

The code sample above builds a JDBC connection to an Exasol database on servers in IP address range 192.168.6.11 to 192.168.6.14 using port 8563. User sys with the password exasol is logged in, and the schema sys is opened. After that, all tables in this schema are shown.

Schema SYS contains: 
EXA_SQL_KEYWORDS, TABLE 
DUAL, TABLE 
EXA_PARAMETERS, TABLE
...

Supported Driver Standards

The JDBC driver supports JDBC 4.1 Core API. Detailed information about the supported interfaces are provided in the API Reference which you can find in the html folder of the driver installation directory. If you want to learn more about JDBC, see JDBC Basics.

The standard includes the following:

• Access to the driver through the DriverManager API and configuration of the driver using the DriverPropertyInfo interface.
• Direct execution of SQL statements as a prepared statement and in batch mode.
• Support of more than one open ResultSet.
• Support of the DatabaseMetaData and ResultSetMetaData metadata APIs.

The following features are not supported:

• Savepoints
• User-defined data types and the types Blob, Clob, Array, and Ref.
• Stored procedures
• Read-only connections
• The API ParameterMetaData

If the rowcount of a query exceeds 2147483647 (2³¹-1), the JDBC driver will return the value 2147483647. This is because of the 32-bit limitation for this return value defined by the JDBC standard.

Supported Driver Properties

The following table describes all properties that can be transferred to the JDBC driver through the URL. Properties that are not listed in the table are not supported in this version of Exasol.

Property names are case sensitive.

Best Practices