All Collections
Supported Databases
Supported Databases

Know the types and versions of databases supported by the Digibee Platform.

Micaella Mazoni avatar
Written by Micaella Mazoni
Updated over a week ago

IMPORTANT: This documentation has been discontinued. Read the updated Supported Databases documentation on our new documentation portal.

The databases are accessed by components created specifically for that, such as:

If you want to know more about the components above, just click on their names or versions to read the respectives articles.

The Digibee Platform currently supports the following databases:

SQL Server

In these versions:

  • 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 String



In these versions:

  • 19.x

  • 18.3

  • 12.2 ou 12cR2

  • 12.1 ou 12cR1

  • 11.2 ou 11gR2

Connection Strings

  • Oracle Net Syntax


  • Syntax with Service Name


IMPORTANT: keep in mind that only the thin-type connections are supported. When accessing the databases specified in this connection string, you agree that you have the necessary Oracle licenses.


In these versions:

  • 5.6

  • 5.7

  • 8.0

Connection String


IMPORTANT: Digibee Platform disables the Maria DB strings interpretation by Mysql driver. However, it's possible to use Maria DB drive to connect to older versions of Mysql.

Maria DB

In the version:

  • 5.5.3+

Connection String


IMPORTANT: Digibee Platform disables the Maria DB strings interpretation by Mysql driver.


In the version:

  • OpenEdge 10.1.x+

Connection String



In the version:

  • SAP/Sybase ASE

Connection String



In all the versions

Connection String


OLAP DataSource via MDX

In these versions:

  • Hyperion Essbase 7

  • Microsoft Analysis Services 2005

  • Mondrian (sem informação de versão)

  • SAP BW 3.0a+

Connection Strings

  • MS SQL Server


  • Mondrian


  • SAP BW


IMPORTANT: this connection mode uses the XMLA standard (XML for Analysis), which must be enabled in the OLAP server to be accessed.

JTOpen for AS/400

No compatibility information

Connection String



  • The Database Access port (standard 8471) must be mapped according to the IBM documentation. Click here to access it.

  • Specify the “prompt=false” parameter for the driver not to request credentials, which are automatically provided.


No compatibility information

Connection String



In the versions:

  • 2.5+

Connection String


DB Informix

By accessing the databases specified in this connection string, you confirm to have the necessary IBM licenses.

No compatibility information

Connection String



By accessing the databases specified in this connection string, you confirm to have the necessary Netsuite licenses.

IMPORTANT: this database driver supports the SELECT operation only.

No compatibility information

Connection String

jdbc:ns://{Server Host}:{Server Port};ServerDataSource={Server Data Source};encrypted=1;Ciphersuites={Cipher Suite};CustomProperties=(AccountID={Account Id};RoleID={Role Id})


When accessing the databases specified in this string connection, you agree to have the necessary Snowflake licences.

In the versions:

  • 3.51.x +

Connection Strings

  • Syntax


  • Example


Click here to have more information about abou the string connection parameters configuration.


1. The 3.10.3 version of the JDBC driver is being used due to a limitation in its current versions - it's not possible to work with micro service by allocating a 64MB memory, configurations that refers to a small pipeline in the Digibee Platform. For more information about the change log of this driver, click here.

2. Snowflake doesn't support the CLOB or BLOB fields. Given that, the “Blob as File” option won't work for the DB and Stream DB componentes. Click here and here to obtain more information.

3. When the batch mode is used and there's an error, the Snowflake driver doesn't return the amount of successful transactions or the amount of errors. Only the first SQL execution error is returned and the rollback of the whole transaction is made even when the “rollbackOnError” option isn't selected.

4. Snowflake doesn't support the OUT and INOUT parameters, returning the SQLFeatureNotSupportedException error.

5. When the batch mode is used, the BINARY and VARBINARY fields aren't supported.

Did this answer your question?