Supported databases

更新时间:
复制 MD 格式

Data Transmission Service (DTS) supports data transmission between various data sources, such as relational database management systems (RDBMS), NoSQL, and online analytical processing (OLAP) databases. This topic describes the databases, migration types, initial synchronization types, synchronization topologies, and change tracking data types that DTS supports.

Note
  • For more information about terms such as migration types, synchronization types, and change tracking data types, see Terms.

  • Cross-region tasks are not supported if the destination database is Function Compute (FC). All other data links support cross-region tasks.

  • For data links where the source or destination is an RDS for MySQL database, Serverless ApsaraDB RDS for MySQL instances are supported. For data links where the source or destination is an RDS for PostgreSQL database, only Serverless ApsaraDB RDS for PostgreSQL instances used as a destination are supported. Serverless instances of ApsaraMQ for Kafka are not supported.

  • Whether you can create tasks across Alibaba Cloud accounts depends on the database type and connection type. If supported, you can find the Replicate Data Across Alibaba Cloud Accounts option when you configure the source or destination database instance. To create a cross-account task, set this option to Yes. For more information, see Configure a task across Alibaba Cloud accounts.

  • DTS can access database instances created in ApsaraDB for MyBase. To do so, set the Access Method to Alibaba Cloud Instance. You can then configure the task by following the instructions in the relevant documents listed in the tables below.

Data synchronization

The data synchronization feature helps you synchronize data between data sources in real time. This feature is suitable for various business scenarios, such as active geo-redundancy, geo-disaster recovery, on-premises data disaster recovery, cross-border data synchronization, query and report offloading, cloud business intelligence (BI), and real-time data warehouses.

For information about the supported databases, versions, synchronization types, and configuration documents, see the following tables or Overview of data synchronization solutions.

Note

If your source database type is not available in the Database Type list for the DTS data synchronization feature, you can use the data shipping feature. For more information, see Data shipping.

Data migration

The data migration feature helps you migrate data between homogeneous or disparate data sources. This feature is suitable for various business scenarios, such as data migration to the cloud, data migration between instances within Alibaba Cloud, and database sharding and scale-out.

For information about the supported databases, versions, migration types, and configuration documents, see the following tables or Overview of migration solutions.

Note
  • Data migration can be used for data synchronization in specific scenarios. However, data migration and data synchronization differ in terms of scenarios, supported databases, features, and billing. For more information, see What are the differences between data migration and data synchronization?.

  • For long-term incremental data migration, use the data synchronization feature. Data synchronization provides better network stability and more features.

Change tracking

The change tracking feature lets you retrieve real-time incremental data from a database. You can consume the incremental data to meet your business needs. For example, you can use the data for cache update policies, business asynchronous decoupling, real-time data synchronization between disparate data sources, and real-time data synchronization that involves complex extract, transform, and load (ETL) processes. You can subscribe to real-time incremental data from various databases, such as self-managed MySQL and RDS for MySQL. You can also use SDK clients, Flink clients, and other clients to consume the subscribed data. For information about the supported change tracking solutions and configuration documents, see the following table or Change tracking solutions.

Alibaba Cloud managed databases

Source databaseSupported versionsSupported change typesConfiguration guide
ApsaraDB RDS for MySQLAll versionsData updates, schema updatesCreate a change tracking task for an ApsaraDB RDS for MySQL instance
PolarDB for MySQLAll versionsData updates, schema updatesCreate a change tracking task for a PolarDB for MySQL cluster
PolarDB-X 1.0Data updates, schema updatesCreate a change tracking task for a PolarDB-X 1.0 instance
PolarDB-X 2.0Data updates, schema updatesCreate a change tracking task for a PolarDB-X 2.0 instance
PolarDB for PostgreSQL (Compatible with Oracle)All versionsData updates onlyCreate a change tracking task for a PolarDB for PostgreSQL (Compatible with Oracle) cluster
ApsaraDB RDS for PostgreSQL9.4, 10, 11, 12, 13, 14, 15, 16, 17Data updates onlyCreate a change tracking task for an ApsaraDB RDS for PostgreSQL instance
PolarDB for PostgreSQL11, 14, 15, 16Data updates, schema updatesCreate a change tracking task for a PolarDB for PostgreSQL cluster
Data Management (DMS) logical databaseData updates onlyCreate a change tracking task for a DMS logical database

PolarDB-X constraints: Databases in a PolarDB-X instance must be created from ApsaraDB RDS for MySQL instances. DTS does not support PolarDB-X databases created from PolarDB for MySQL clusters.

DMS logical database constraint: The logical database must be created from the database shards of multiple PolarDB for MySQL clusters.

Self-managed databases

Source databaseSupported versionsSupported change typesConfiguration guide
Self-managed MySQL5.1, 5.5, 5.6, 5.7, 8.0Data updates, schema updatesCreate a change tracking task for an ApsaraDB RDS for MySQL instance
Self-managed Oracle (non-RAC)9i, 10g, 11gData updates, schema updatesCreate a change tracking task for an Oracle database
Self-managed PostgreSQL9.4.8 and later, 9.5, 9.6, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.xData updates onlyCreate a change tracking task for an ApsaraDB RDS for PostgreSQL instance