EN-US
Ask or search…
K
Links

Supported databases

Discover the types and versions of databases supported by the Digibee Integration Platform and how they can make integration pipeline creation easier for all users.
You can access databases using specific components, such as:
The database support mentioned here doesn't apply to deprecated versions of components. We recommend that you don't use deprecated components. Some examples of deprecated components are:
The Digibee Integration Platform currently supports the following databases:

DB2

The Digibee Integration Platform offers support for the JDBC IBM DB2 driver and covers the following versions:
  • DB2 level version: 11.5
  • Driver version: 4.26.14
Connection String
jdbc:db2://127.0.0.1:1724/dbtest
The available features are based on the official documentation of DB2. Your company's driver licensed by IBM must be activated to connect across supported database versions.
This process is handled by the Digibee support team, but you must provide the JDBC IBM DB2 driver for activation. This process is exclusive to the requesting customer's realm.

Apache Hive

The Digibee Integration Platform offers support for Apache Hive via JDBC Connector 2.6.17 for Cloudera Enterprise only and covers the following versions:
  • Apache Hive versions 1.0.0 to 3.1
Connection string
jdbc:hive2://localhost:10002
The available features are based on the official documentation of JDBC Cloudera driver. Your company's driver licensed by Cloudera must be activated to connect across supported database versions.
This process is handled by the Digibee support team, but you must provide the Cloudera JDBC driver for activation. This process is exclusive to the requesting customer's realm.

Teradata Database

The Digibee Integration Platform offers support for the following versions:
  • Teradata Database 16.10, 16.20, 17.00, 17.10 and 17.20.
Connection String
jdbc:teradata://192.168.64.2/DATABASE=DBC,DBS_PORT=1025
Your company's driver licensed by Teradata must be activated to connect across supported database versions. This process is handled by the Digibee support team, but you must provide the Teradata JDBC driver for activation. This process is exclusive to the requesting customer's realm.

SQL Server

The Digibee Integration Platform offers support for the following versions:
  • Microsoft SQL Server 2019
  • Microsoft SQL Server 2017
  • Microsoft SQL Server 2016
  • Microsoft SQL Server 2014
  • Microsoft SQL Server 2012
  • Microsoft SQL Server 2008 R2
  • Azure SQL Database
  • Azure SQL Data Warehouse or Parallel Data Warehouse
  • Azure SQL Managed Instance (Extended Private Preview)
Connection via Microsoft SQL 2019 version is supported, but some features of this version may not be available.
Connection String
jdbc:sqlserver://[serverName[\instanceName][:portNumber]]

Oracle

The Digibee Integration Platform offers support for the following versions:
  • 19.x
  • 18.3
  • 12.2 or 12cR2
  • 12.1 or 12cR1
  • 11.2 or 11gR2
Connection Strings
  • Oracle Net Syntax
jdbc:oracle:thin:@(DESCRIPTION=
(LOAD_BALANCE=on)
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCP)(HOST=host1) (PORT=5221))
(ADDRESS=(PROTOCOL=TCP)(HOST=host2)(PORT=5221)))
(CONNECT_DATA=(SERVICE_NAME=orcl)))
In the Oracle database, the connection string can contain multiple endpoints. If your connection string contains more than one endpoint, the Oracle driver will attempt to connect to each endpoint until it's successful or there is no other endpoint.
So if your connection string contains multiple endpoints and you set the "oracle.net.connect_timeout" parameter in the Custom Connection Properties for components such as DB V2, Stream DB V3, and Stored Procedure, it's important to know that the timeout applies to each specified endpoint individually. It doesn't apply to all endpoints at the same time.
  • Syntax with Service Name
jdbc:oracle:thin:@//localhost:5221/orcl
Only thin-type connections are supported. By accessing the databases specified in this connection string, you confirm that you have the required Oracle licenses.

MySQL

The Digibee Integration Platform offers support for the following versions:
  • 5.6
  • 5.7
  • 8.0
Connection String
jdbc:mysql://<host>:<port>/<database>
Digibee Integration Platform deactivates MySQL driver’s interpretation of Maria DB strings. However, you can use Maria DB’s drive to connect to older versions of MySQL.

Maria DB

The Digibee Integration Platform offers support for the following version:
  • 5.5.3+
Connection String
jdbc:mariadb://<host>:<port>/<database>
Digibee Integration Platform deactivates MySQL driver’s interpretation of Maria DB strings.

Progress

The Digibee Integration Platform offers support for the following version:
  • OpenEdge 10.1.x+
Connection String
jdbc:datadirect:openedge://hostname:port

Sybase

The Digibee Integration Platform offers support for the following version:
  • SAP/Sybase ASE
Connection String
jdbc:sybase:Tds:host:port

PostgreSQL

The Digibee Integration Platform offers support for all versions.
Connection String
jdbc:postgresql://host:port/database

OLAP DataSource via MDX

The Digibee Integration Platform offers support for the following versions:
  • Hyperion Essbase 7
  • Microsoft Analysis Services 2005
  • Mondrian (no version information)
  • SAP BW 3.0a+
Connection Strings
  • MS SQL Server
jdbc:jdbc4olap:http://<server>:<port>/OLAP/msmdpump.dll
  • Mondrian
jdbc:jdbc4olap:http://<server>:<port>/mondrian/xmla
  • SAP BW
jdbc:jdbc4olap:http://<server>:<port>/sap/bw/soap/xmla?sap-client=number
This type of connection uses the XML for Analysis (XMLA) standard, which must be enabled in the OLAP server to be accessed.

JTOpen for AS/400

No compatibility information
Connection String
jdbc:as400://<server>[:port];prompt=false
The Database Access port (standard 8471) must be mapped according to the IBM documentation. We also recommend specify the parameter prompt=false to prevent the driver from requesting credentials. These credentials are provided automatically.

SAP HANA

No compatibility information
Connection String
jdbc:sap://<server>:<port>

Firebird

The Digibee Integration Platform offers support for the following versions:
  • 2.5+
Connection String
jdbc:firebirdsql://<HOST>:<PORT>/C:\PATH_TO_DATABASE/DATABASE_FILE.FDB

DB Informix

No compatibility information
By accessing the databases specified in this connection string, you confirm that you have the required IBM licenses.
Connection String
jdbc:informix-sqli://<HOST>:<PORT>/<DATABASE>:informixserver=<INFORMIX_SERVER>

Netsuite

No compatibility information
By accessing the databases specified in this connection string, you confirm that you have the required Netsuite licenses.
This database driver supports only the SELECT operation.
Connection String
jdbc:ns://{Server Host}:{Server Port};ServerDataSource={Server Data Source};encrypted=1;Ciphersuites={Cipher Suite};CustomProperties=(AccountID={Account Id};RoleID={Role Id})

Snowflake

By accessing the databases specified in this connection string, you confirm that you have the required Snowflake licenses.
The Digibee Integration Platform offers support for the following versions:
  • 3.51.x +
Connection Strings
  • Syntax
jdbc:snowflake://<account_name>.snowflakecomputing.com/?<connection_params>
  • Example
jdbc:snowflake://wxyz.us-central1.gcp.snowflakecomputing.com/?db=snowflake_sample_data&sfSchema=TPCH_SF100
Read Snowflake's documentation to know more about configuring connection string parameters.
  • We are currently using the legacy version 3.10.3 of the JDBC driver due to a limitation in more recent versions: it's not possible to work with micro service by allocating a 64MB memory (this configuration refers to a small pipeline in the Digibee Integration Platform). Visit Snowflake’s change log documentation for further information.
  • Snowflake does not support CLOB or BLOB fields. For this reason, the "Blob as file" option doesn't work for the DB and Stream DB components. Read Snowflake's documentation about unsupported data types and binary input and output for more information.
  • When batch mode is used and an error occurs, the Snowflake driver doesn't return the number of successful transactions or the number of errors. Only the first SQL execution error is returned and the entire transaction is rolled back, even if the "rollbackOnError" option is deactivated.
  • Snowflake doesn't support OUT and INOUT parameters. If you try to use these parameters, Snowflake returns a SQLFeatureNotSupportedException error.
  • When the batch mode is used, the BINARY and VARBINARY fields aren't supported.
Last modified 2mo ago