USER MANUALS


Supported JDBC Data Sources

The following table lists the databases for which Virtual DataPort provides a JDBC adapter.

Consider this:

  • To connect to a database that is not listed here, use the adapter “Generic”.

  • To connect to a database that is listed here but the version you are connecting to is newer than the versions listed here, use the most recent adapter for this database.

  • Some database vendors forbid other software companies to distribute their drivers (in the table below, see the databases with the column Driver Included in Denodo = Driver not included):

    • To connect to one of these databases, download the official driver of the database, not the driver of another third-party company. Consider this:

      1. We conduct the tests of each adapter using the official driver.

      2. Only the official driver is really supported. If you use the driver of another company and something does not work, the Denodo Support Team will try to provide assistance but may not be able to provide a solution.

    • To import a driver, use the wizard of the menu File > Extension management to import the driver. The page Importing a JDBC Driver explains how to do this.

  • The Denodo Platform includes the drivers of the databases to make it easier for developers to create connections to data sources. Periodically, we upgrade these drivers so our customers benefit from bugfixes and enhancements. However, we cannot fix bugs in the drivers of other companies (only in the drivers developed by Denodo). If any issue arises due to bugs in these drivers, we will try to provide a workaround to the best of our ability but ultimately, it is up to the database vendors to fix the bugs in their own drivers.

JDBC adapters included in the Denodo Platform

Database

Version

Notes

Driver Included in Denodo

AlloyDB for PostgreSQL

12

Driver included

Alibaba ApsaraDB for OceanBase MySQL

2

Driver not included

Alibaba ApsaraDB for OceanBase Oracle

2

Driver not included

Alibaba ApsaraDB RDS for MySQL

8

Driver not included

Alibaba ApsaraDB RDS for PostgreSQL

12

Driver included

Alibaba ApsaraDB RDS for Microsoft SQL Server

2019

Driver included

Alibaba ApsaraDB PolarDB for MySQL

8

Driver not included

Alibaba ApsaraDB PolarDB for PostgreSQL

12

Driver included

Alibaba ApsaraDB AnalyticDB for MySQL

5

Driver not included

Alibaba ApsaraDB AnalyticDB for PostgreSQL

12

Driver included

Amazon Redshift

N/A

Driver included

Amazon Athena

1.0

Driver included

Amazon Aurora MySQL

5

Driver not included

Amazon Aurora PostgreSQL

12

Driver included

Apache Derby

10 and higher

Driver included

Apache Spark SQL

1.5

Driver not included

1.6

2.x

3.x and higher

Azure SQL

N/A

Driver included

Azure Synapse SQL (previously known as Azure SQL Data Warehouse)

N/A

Driver included

Cassandra

3.x

Using DbSchema/DataStax JDBC Driver for Apache Cassandra

Driver included

ClickHouse

N/A

Driver included

Databricks

N/A

It also supports Databricks SQL Serverless

Driver included

Elasticsearch

6.4

Driver included

6.7

Exasol

7.1

Driver included

Google BigQuery

Driver not included

Google Spanner

Includes support for the service Spanner Data Boost

Driver included

GCP (Google Cloud) SQL for MySQL

N/A

Driver not included

GCP (Google Cloud) SQL for PostgreSQL

N/A

Driver included

Greenplum

4.2

Driver included

Hive

0.13.0 (Hive Server 2)

Driver not included (*)

1.1.0 (Hive Server 2)

2.0.0 (Hive Server 2)

3.1.2 and higher (Hive Server 3)

Hive for Cloudera

1.1.0

Driver not included

Hive for Hortonworks

1.2.1

Driver not included

IBM DB2

8.2

Driver not included

9

9 for z/OS

10

10 for z/OS

11 and higher

11 for z/OS

Impala

1.2.4

Driver not included (**)

2.3

3.x Kudu

Informix

7

Driver not included

12

Microsoft SQL Server

2000

Denodo uses the official Microsoft JDBC driver to connect to the versions 2019, 2017, 2016 and 2014.

You can choose the jTDS or the official Microsoft JDBC driver to connect to the versions 2008, 2008R2 and 2012.

Denodo uses the jTDS JDBC driver to connect to the versions 2000 and 2005.

Both drivers are included

2005

2008

2008R2

2012

2014

2016

2017

2019 and higher

MySQL

4

Driver not included

5

8 and higher

Netezza

4.6

Driver not included

5.0

6.0

7.0 and higher

Oracle

8i

Driver included

9i

10g

11g

12c

12c In-Memory

E-Business Suite 12

18c

19c and higher

Oracle TimesTen

11g

The connection URI is different, depending on if there is a DSN in the same host as Virtual DataPort that points to Oracle TimesTen, or not.

With DSN: jdbc:timesten: client:<client DSN>

Without DSN: jdbc:timesten: client:ttc_server= <host>;tcp_port= <port>; ttc_server_dsn= <server_dsn>

Driver included

PostgreSQL

8

Driver included

9

10

11

12 and higher

PrestoDB

N/A

Driver included

Trino

N/A

Driver included

SAP HANA

1.0

Driver not included

2.0

SAS

9.4

Driver not included

Snowflake

N/A

Driver included

Sybase ASE / SAP ASE

12

Either you can use the Sybase driver or the jTDS open source driver.

Yes: Denodo uses the jTDS driver.

15

SAP IQ (formerly known as Sybase IQ)

16

To connect to this data source you need to use the jConnect driver included in the SAP IQ installation.

Driver not included

Teradata

12

Driver not included

13

14

15

16

17

Vertica

7

Driver included

9

Driver included

Denodo Virtual DataPort

7

Driver included

8

Yellowbrick

N/A

Driver included

(*): To connect to Hortonworks Hive, selects its specific adapter; do not select one of the generic Apache Hive adapters. Also, when obtaining the driver, obtain the specific driver for Hortonworks. The same applies to Cloudera Hive.

(**): To connect to Impala, use a JDBC driver version 2.5.24 or higher. You can download the latest JDBC driver from the Cloudera website . You have to select the latest driver that IS NOT “C6 compatible”.

The adapters for Virtual DataPort version 7 and 8 can be used to connect to other Virtual DataPort servers and the adapter of 8, to connect to the Virtual DataPort server itself.

Add feedback