Supported databases for profiling data
The table below lists the databases supported from the Profiling perspective of Talend Studio. For a complete list about supported third-party systems, see Supported systems, databases, and business applications by Talend components.
Information noteTip: If the database you want to connect to is not
in the list but has a JDBC driver, like Snowflake, you can use a JDBC connection.
| Database name | Database version |
|---|---|
| Amazon Aurora | Amazon RDS for Aurora |
| Amazon Redshift | Initial release of Amazon Redshift |
| AS/400 | V7R1 to V7R3 |
| V6R1 to V7R2 | |
| Hive | See, Supported Hive distributions for profiling data. |
| IBM DB2 and IBM DB2 Z/OS 1 | 11.1 |
| 10.5 | |
| Impala (a sub-module of Cloudera) | CDH5.1 and above |
| MapR 6.1.0 (YARN mode) (deprecated) | |
| MapR 6.0.1 (YARN mode) (deprecated) | |
| MapR 6.0.0 (YARN mode) (deprecated) | |
| MapR 5.2.0 (YARN mode) (deprecated) | |
| MapR 5.1.0 (YARN mode) (deprecated) | |
| Informix | 11.50 |
| Ingres | 10.2 |
| Microsoft SQL Server | Amazon RDS for SQL Server |
| Azure SQL Database | |
| Azure Synapse Analytics | |
| 2017 | |
| 2016 | |
| 2014 | |
| MySQL | Amazon RDS for MySQL |
| Amazon RDS for MariaDB | |
| Azure Database for MySQL | |
| MySQL 8.0 | |
| MySQL 5.1/5.5/5.6 | |
| MariaDB | |
| Netezza | 7.2 |
| 6 | |
| Oracle with SID | Amazon RDS for Oracle |
| Oracle 19c | |
| Oracle 18c | |
| Oracle 12c Release 1 | |
| Oracle with service name | Amazon RDS for Oracle |
| Oracle 19c | |
| Oracle 18c | |
| Oracle 12c Release 1 | |
| PostgreSQL | Amazon RDS for PostgreSQL |
| Azure Database for PostgreSQL | |
| 12.1 | |
| 10 | |
| 9.1+ | |
| 8.3 | |
| SAP HANA 2 | 2.0 |
| SQLite | 3.6.7 |
| Sybase (ASE and IQ)QLite | 16.0 |
| 15.7 | |
| 15.2 | |
| 12.7 | |
| 12.5 | |
| Teradata | 16 |
| 15 | |
| 14 | |
| 13 | |
| 12 | |
| Vertica | 9.x |
1 Binary large objects (BLOBs) are not supported.
2 SAP HANA is supported for Table, View, and Calculation View schemas.
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!