Upgrade: Database Query🔗

The Data Productivity Cloud has a Database Query component that is equivalent to the Matillion ETL Database Query component. Vendor restrictions on shipping database drivers mean that we can't supply drivers for every possible source database, but there is a mechanism in the Data Productivity Cloud that allows you to upload additional database drivers.

Databases natively supported by the Database Query component are listed in this table. If the source database is one of those listed, the migration will work seamlessly. For databases not listed, you have other options, as described below.

Upgrade path🔗

The source database used by a Database Query component will determine which of the following upgrade paths is taken for that component.

Upgraded automatically🔗

Database Query components with the following source databases will migrate automatically with no issues and no manual intervention required:

Amazon Redshift
IBM DB2 for i
MariaDB
Microsoft SQL Server
Oracle
PostgreSQL
Sybase ASE
Snowflake
SQL Server (Microsoft driver)

Upgrade with a driver upload🔗

If the source database isn't supported by default, this is typically because we don't have legal permission to ship or use a driver for that source. In these cases, we have provided a new component, JDBC, that allows you to upload your own driver to the Data Productivity Cloud for any JDBC-compatible data source.

The upgrade process will check the Database Type property of any Database Query component it finds during a pipeline migration. If the database isn't one of the natively supported types (listed above), then the component will be automatically changed to the JDBC component, and the component properties will be configured where possible.

You must upload a suitable JDBC driver for each data source, following the process given in Uploading external drivers to the agent, and configure each JDBC component as necessary.

You must also create a manifest file, as described in the JDBC component documentation. The manifest file contains configuration information for your data sources.

Note

This option is available for Hybrid SaaS deployments only.

MySQL🔗

MySQL is a special case. Due to legal restrictions, we can't ship nor use the official MySQL driver. Instead, we use the open source MariaDB driver, which is compatible. During migration, Database Query components that use MySQL are automatically changed to refer to the MariaDB driver.

If you need to use the official MySQL driver, you must use the JDBC component and provide your own driver, as described above.