Data Transmission Service (DTS) supports data transmission between various data sources, such as relational database management systems (RDBMSs), NoSQL databases, and online analytical processing (OLAP) databases. This topic describes the database types, migration types, synchronization types, synchronization topologies, and data change types that are supported by DTS.
For information about terms related to migration types, synchronization types, and change tracking, see Terms.
Data synchronization
You can use DTS to synchronize data between data sources in real time. This feature is suitable for the following scenarios: active geo-redundancy, geo-disaster recovery, zone-disaster recovery, cross-border data synchronization, query load balancing, cloud business intelligence (BI) systems, and real-time data warehousing.
For information about the supported database types, database engine versions, synchronization types, and how to configure a data synchronization task, see the following tables or Data synchronization scenarios.
If your source database type is not supported by DTS, you can use the data shipping feature.Database Type For more information, see Data shipping.
Synchronize data from a self-managed MySQL database or an ApsaraDB RDS for MySQL instance
ImportantA database in a PolarDB-X 1.0 instance must be created based on one or more ApsaraDB RDS for MySQL instances. DTS does not support PolarDB-X 1.0 databases that are created based on PolarDB for MySQL clusters.
For a data synchronization task that synchronizes data to a PolarDB-X 1.0 instance, schema synchronization or initial schema synchronization is not supported. Schema synchronization and initial schema synchronization are supported for a data synchronization task that synchronizes data to a PolarDB-X 2.0 instance.
A database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend that you update the instance to version 5.4.11 or later. For more information about how to update the version of an instance, see View and update the version of an instance.
Source database
Destination database
Synchronization type
Synchronization topology
References
Self-managed MySQL database
Version 5.1, 5.5, 5.6, 5.7, or 8.0
ApsaraDB RDS for MySQL instance
All versions
Self-managed MySQL database
Version 5.1, 5.5, 5.6, 5.7, or 8.0
ApsaraDB RDS for MySQL instance
All versions
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Two-way synchronization
PolarDB for MySQL cluster
All versions
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Two-way synchronization
Oracle database (RAC or non-RAC architecture)
Version 9i, 10g, 11g, 12c, 18c, or 19c
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from an ApsaraDB RDS for MySQL instance to a self-managed Oracle database
PolarDB-X 1.0 instance
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from an ApsaraDB RDS for MySQL instance to a PolarDB-X instance
PolarDB-X 2.0 instance
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from an ApsaraDB RDS for MySQL instance to a PolarDB-X 2.0 instance
AnalyticDB for MySQL cluster
Version 2.0 or 3.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from an ApsaraDB RDS for MySQL instance to an AnalyticDB for MySQL V3.0 cluster
Synchronize data from an ApsaraDB RDS instance to an AnalyticDB for MySQL cluster
Self-managed PostgreSQL database
Version 9.5.x, 9.6.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, or 16.x
ApsaraDB RDS for PostgreSQL instance
Version 9.4, 10, 11, 12, 13, 14, 15, or 16
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from an ApsaraDB RDS for MySQL instance to an ApsaraDB RDS for PostgreSQL instance
AnalyticDB for PostgreSQL instance
Version 4.3, 6.0, or 7.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from an ApsaraDB RDS for MySQL instance to an AnalyticDB for PostgreSQL instance
ApsaraMQ for Kafka instance
Versions 0.10.1.0 to 2.x
Self-managed Kafka cluster
Versions 0.10.1.0 to 2.7.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
ApsaraDB for ClickHouse cluster
Version 20.8 or later
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from an ApsaraDB RDS for MySQL instance to an ApsaraDB for ClickHouse cluster
DataHub project
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from an ApsaraDB RDS for MySQL instance to a DataHub project
Elasticsearch cluster
Version 5.5, 5.6, 6.x, or 7.x
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a self-managed MySQL database hosted on ECS to an Elasticsearch cluster
MaxCompute project
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from an ApsaraDB RDS for MySQL instance to a MaxCompute project
ApsaraDB for Redis Community Edition instance (cluster, standard, or read/write splitting architecture)
Version 4.0, 5.0, 6.0, or 7.0
ApsaraDB for Redis Enhanced Edition (Tair) instance (cluster, standard, or read/write splitting architecture)
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from an ApsaraDB RDS for MySQL instance to a Tair or ApsaraDB for Redis instance
Tablestore (OTS) instance
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from an ApsaraDB RDS for MySQL instance to a Tablestore instance
Function Compute function
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from an ApsaraDB RDS for MySQL instance to a Function Compute function
Synchronize data from a PolarDB for MySQL cluster
ImportantA database in a PolarDB-X 1.0 instance must be created based on one or more ApsaraDB RDS for MySQL instances. DTS does not support PolarDB-X 1.0 databases that are created based on PolarDB for MySQL clusters.
For a data synchronization task that synchronizes data to a PolarDB-X 1.0 instance, schema synchronization or initial schema synchronization is not supported. Schema synchronization and initial schema synchronization are supported for a data synchronization task that synchronizes data to a PolarDB-X 2.0 instance.
A database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend that you update the instance to version 5.4.11 or later. For more information about how to update the version of an instance, see View and update the version of an instance.
Source database
Destination database
Synchronization type
Synchronization topology
References
PolarDB for MySQL cluster
All versions
PolarDB for MySQL cluster
All versions
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Two-way synchronization
Self-managed MySQL database
Version 5.1, 5.5, 5.6, 5.7, or 8.0
ApsaraDB RDS for MySQL instance
All versions
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Two-way synchronization
From a PolarDB for MySQL cluster to an ApsaraDB RDS for MySQL instance
PolarDB-X 1.0 or PolarDB-X 2.0 instance
Full data synchronization
Incremental data synchronization
One-way synchronization
Two-way synchronization
AnalyticDB for MySQL cluster
Version 2.0 or 3.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
AnalyticDB for PostgreSQL instance
Version 4.3, 6.0, or 7.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
From a PolarDB for MySQL cluster to an AnalyticDB for PostgreSQL instance
ApsaraMQ for Kafka instance
Versions 0.10.1.0 to 2.x
Self-managed Kafka cluster
Versions 0.10.1.0 to 2.7.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
From a PolarDB for MySQL cluster to a self-managed Kafka cluster
DataHub project
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB for MySQL cluster to a DataHub project
ApsaraDB for ClickHouse cluster
Version 20.8 or later
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB for MySQL cluster to an ApsaraDB for ClickHouse cluster
Elasticsearch cluster
Version 5.5, 5.6, 6.x, or 7.x
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB for MySQL cluster to an Elasticsearch cluster
MaxCompute project
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB for MySQL cluster to a MaxCompute project
Oracle database (RAC or non-RAC architecture)
Version 9i, 10g, 11g, 12c, 18c, or 19c
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB for MySQL cluster to a self-managed Oracle database
Synchronize data from a PolarDB for PostgreSQL cluster
Source database
Destination database
Synchronization type
Synchronization topology
References
PolarDB for PostgreSQL cluster
Version 11 or 14
Self-managed PostgreSQL database
Version 9.5.x, 9.6.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, or 16.x
ApsaraDB RDS for PostgreSQL instance
Version 9.4, 10, 11, 12, 13, 14, 15, or 16
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Two-way synchronization
Synchronize data from a PolarDB for PostgreSQL cluster to an ApsaraDB RDS for PostgreSQL instance
PolarDB for PostgreSQL cluster
Version 11 or 14
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Two-way synchronization
AnalyticDB for PostgreSQL instance
Version 4.3, 6.0, or 7.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB for PostgreSQL cluster to an AnalyticDB for PostgreSQL instance
Synchronize data from a PolarDB-X instance
ImportantA database in a PolarDB-X 1.0 instance must be created based on one or more ApsaraDB RDS for MySQL instances. DTS does not support PolarDB-X 1.0 databases that are created based on PolarDB for MySQL clusters.
For a data synchronization task that synchronizes data to a PolarDB-X 1.0 instance, schema synchronization or initial schema synchronization is not supported. Schema synchronization and initial schema synchronization are supported for a data synchronization task that synchronizes data to a PolarDB-X 2.0 instance.
A database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend that you update the instance to version 5.4.11 or later. For more information about how to update the version of an instance, see View and update the version of an instance.
Source database
Destination database
Synchronization type
Synchronization topology
References
PolarDB-X 1.0 instance
PolarDB-X 1.0 instance
Full data synchronization
Incremental data synchronization
One-way synchronization
Self-managed MySQL database
Version 5.1, 5.5, 5.6, 5.7, or 8.0
ApsaraDB RDS for MySQL instance
All versions
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB-X 1.0 instance to an ApsaraDB RDS for MySQL instance
PolarDB for MySQL cluster
All versions
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB-X 1.0 instance to a PolarDB for MySQL cluster
AnalyticDB for MySQL cluster
Version 3.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB-X 1.0 instance to an AnalyticDB for MySQL V3.0 cluster
DataHub project
Schema synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB-X 1.0 instance to a DataHub project
AnalyticDB for PostgreSQL instance
Version 4.3, 6.0, or 7.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB-X 1.0 instance to an AnalyticDB for PostgreSQL instance
ApsaraMQ for Kafka instance
Versions 0.10.1.0 to 2.x
Self-managed Kafka cluster
Versions 0.10.1.0 to 2.7.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB-X 1.0 instance to an ApsaraMQ for Kafka instance
Elasticsearch cluster
Version 5.5, 5.6, 6.x, or 7.x
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB-X 1.0 instance to an Elasticsearch cluster
PolarDB-X 2.0 instance
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB-X 1.0 instance to a PolarDB-X 2.0 instance
PolarDB-X 2.0 instance
PolarDB-X 2.0 instance
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Two-way synchronization
Self-managed MySQL database
Version 5.1, 5.5, 5.6, 5.7, or 8.0
ApsaraDB RDS for MySQL instance
All versions
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB-X 2.0 instance to an ApsaraDB RDS for MySQL instance
PolarDB for MySQL cluster
All versions
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB-X 2.0 instance to a PolarDB for MySQL cluster
AnalyticDB for MySQL cluster
Version 3.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB-X 2.0 instance to an AnalyticDB for MySQL V3.0 cluster
ApsaraMQ for Kafka instance
Versions 0.10.1.0 to 2.x
Self-managed Kafka cluster
Versions 0.10.1.0 to 2.7.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB-X 2.0 instance to an ApsaraMQ for Kafka instance
DataHub project
Schema synchronization
Incremental data synchronization
One-way synchronization
Synchronize incremental data from a PolarDB-X 2.0 instance to a DataHub project
MaxCompute project
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB-X 2.0 instance to a MaxCompute project
AnalyticDB for PostgreSQL instance
Version 4.3, 6.0, or 7.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB-X 2.0 instance to an AnalyticDB for PostgreSQL instance
Elasticsearch cluster
Version 5.5, 5.6, 6.x, or 7.x
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB-X 2.0 instance to an Elasticsearch cluster
Oracle database (RAC or non-RAC architecture)
Version 9i, 10g, 11g, 12c, 18c, or 19c
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB-X 2.0 instance to a self-managed Oracle database
OTS instance
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB-X 2.0 instance to a Tablestore instance
Synchronize data from a PolarDB for PostgreSQL (Compatible with Oracle) cluster
Source database
Destination database
Synchronization type
Synchronization topology
References
PolarDB for PostgreSQL (Compatible with Oracle) cluster
All versions
PolarDB for PostgreSQL (Compatible with Oracle) cluster
All versions
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Two-way synchronization
ApsaraMQ for Kafka instance
Versions 0.10.1.0 to 2.x
Self-managed Kafka cluster
Versions 0.10.1.0 to 2.7.0
Incremental data synchronization
One-way synchronization
Synchronize data from a PolarDB for Oracle cluster to a self-managed Kafka cluster
AnalyticDB for MySQL cluster
Version 3.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from an Oracle database
ImportantYou can configure a data synchronization task for this scenario only in the DTS console of the new version.
A destination database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend that you update the instance to version 5.4.11 or later. For more information about how to update the version of an instance, see View and update the version of an instance.
Source database
Destination database
Synchronization type
Synchronization topology
References
Self-managed Oracle database (RAC or non-RAC architecture)
Version 9i, 10g, 11g, 12c, 18c, or 19c
AnalyticDB for PostgreSQL instance
Version 4.3, 6.0, or 7.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a self-managed Oracle database to an AnalyticDB for PostgreSQL instance
DataHub project
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a self-managed Oracle database to a DataHub project
PolarDB-X 2.0 instance
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a self-managed Oracle database to a PolarDB-X 2.0 instance
PolarDB for MySQL cluster
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a self-managed Oracle database to a PolarDB for MySQL cluster
MaxCompute project
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Available soon
PolarDB for PostgreSQL (Compatible with Oracle) cluster
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Available soon
ApsaraMQ for Kafka instance
Versions 0.10.1.0 to 2.x
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a self-managed Oracle database to an ApsaraMQ for Kafka instance
Synchronize data from a self-managed PostgreSQL database or an ApsaraDB RDS for PostgreSQL instance
ImportantA serverless ApsaraDB RDS for PostgreSQL instance can serve as the destination database but not as the source database.
Source database
Destination database
Synchronization type
Synchronization topology
References
Self-managed PostgreSQL database
Version 9.5.x, 9.6.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, or 16.x
ApsaraDB RDS for PostgreSQL instance
Version 9.4, 10, 11, 12, 13, 14, 15, or 16
Self-managed PostgreSQL database
Version 9.5.x, 9.6.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, or 16.x
ApsaraDB RDS for PostgreSQL instance
Version 9.4, 10, 11, 12, 13, 14, 15, or 16
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Two-way synchronization
PolarDB for PostgreSQL cluster
Version 11 or 14
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Two-way synchronization
Synchronize data from an ApsaraDB RDS for PostgreSQL instance to a PolarDB for PostgreSQL cluster
AnalyticDB for PostgreSQL instance
Version 4.3, 6.0, or 7.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Self-managed MySQL database
Version 5.1, 5.5, 5.6, 5.7, or 8.0
ApsaraDB RDS for MySQL instance
All versions
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from an ApsaraDB RDS for PostgreSQL instance to an ApsaraDB RDS for MySQL instance
PolarDB for PostgreSQL (Compatible with Oracle) cluster
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a self-managed SQL Server database or an ApsaraDB RDS for SQL Server instance
ImportantThe source self-managed SQL Server database must be one of the following editions: Enterprise, Developer, Enterprise Evaluation, and Standard.
The destination self-managed SQL Server database must be one of the following editions: Enterprise, Developer, Enterprise Evaluation, and Standard.
DTS supports SQL Server clusters and SQL Server Always On availability groups (AOAGs).
The source database cannot be a self-managed SQL Server database of version 2015 or an ApsaraDB RDS for SQL Server database of version 2008 or 2008R2.
If the SQL Server Incremental Synchronization Mode parameter is set to Log-based Parsing for Non-heap Tables and CDC-based Incremental Synchronization for Heap Tables, data is synchronized in the hybrid log-based parsing mode and the following versions of source databases are supported:
Self-managed SQL Server or ApsaraDB RDS for SQL Server database of the Enterprise or Enterprise Evaluation edition: version 2012, 2014, 2016, or 2019.
Self-managed SQL Server or ApsaraDB RDS for SQL Server database of the Standard edition: version 2016 or 2019.
Source database
Destination database
Synchronization type
Synchronization topology
References
Self-managed SQL Server database
Version 2008 R2, 2012, 2014, 2016, 2017, 2019, or 2022
ApsaraDB RDS for SQL Server instance
Version 2012, 2014, 2016, 2017, 2019, or 2022
Self-managed SQL Server database
Version 2008 R2, 2012, 2014, 2016, 2017, 2019, or 2022
ApsaraDB RDS for SQL Server instance
Version 2008 R2, 2012, 2014, 2016, 2017, 2019, or 2022
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data between ApsaraDB RDS for SQL Server instances
Self-managed MySQL database
Version 5.1, 5.5, 5.6, 5.7, or 8.0
ApsaraDB RDS for MySQL instance
All versions
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from an ApsaraDB RDS for SQL Server instance to an ApsaraDB RDS for MySQL instance
PolarDB for MySQL cluster
All versions
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a self-managed SQL Server database to a PolarDB for MySQL cluster
AnalyticDB for MySQL cluster
Version 3.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
AnalyticDB for PostgreSQL instance
Version 4.3, 6.0, or 7.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
DataHub project
Schema synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from an ApsaraDB RDS for SQL Server instance to a DataHub project
Synchronize data from an ApsaraDB RDS for MariaDB instance
Source database
Destination database
Synchronization type
Synchronization topology
References
ApsaraDB RDS for MariaDB TX instance
Self-managed MariaDB Database
ApsaraDB RDS for MariaDB TX instance
Self-managed MariaDB Database
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
ApsaraDB RDS for MySQL instance
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from an ApsaraDB RDS for MariaDB TX instance to an ApsaraDB RDS for MySQL instance
ApsaraDB RDS for PostgreSQL instance
Version 9.4, 10, 11, 12, 13, 14, 15, or 16
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a self-managed MongoDB database or an ApsaraDB MongoDB instance
Source database
Destination database
Synchronization type
Synchronization topology
References
Replica set instances
Self-managed MongoDB database
Versions 2.8 to 6.0
ApsaraDB for MongoDB instance
Version 3.4, 4.0, 4.2, 4.4, 5.0, or 6.0
Replica set or sharded cluster architecture
Self-managed MongoDB database
Versions 2.8 to 6.0
ApsaraDB for MongoDB instance
Version 3.4, 4.0, 4.2, 4.4, 5.0, or 6.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Sharded cluster instances
Self-managed MongoDB database
Versions 2.8 to 6.0
ApsaraDB for MongoDB instance
Version 3.4, 4.0, 4.2, 4.4, 5.0, or 6.0
Replica set or sharded cluster architecture
Self-managed MongoDB database
Versions 2.8 to 6.0
ApsaraDB for MongoDB instance
Version 3.4, 4.0, 4.2, 4.4, 5.0, or 6.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Replica set or sharded cluster architecture
Self-managed MongoDB database
Versions 2.8 to 6.0
ApsaraDB for MongoDB instance
Version 3.4, 4.0, 4.2, 4.4, 5.0, or 6.0
Function Compute function
Incremental data synchronization
One-way synchronization
Replica set or sharded cluster architecture
Self-managed MongoDB database
Versions 2.8 to 6.0
ApsaraDB for MongoDB instance
Version 3.4, 4.0, 4.2, 4.4, 5.0, or 6.0
Lindorm instance
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from an ApsaraDB for MongoDB instance to a Lindorm instance
ApsaraDB for MongoDB sharded cluster instance
Version 4.0, 4.2, 4.4, 5.0, or 6.0
ApsaraDB for MongoDB sharded cluster instance
Version 4.0, 4.2, 4.4, 5.0, or 6.0
Schema synchronization
Full data synchronization
Incremental data synchronization
Two-way synchronization
Configure two-way data synchronization between ApsaraDB for MongoDB sharded cluster instances
ApsaraDB for MongoDB replica set instance
Version 4.0, 4.2, 4.4, 5.0, or 6.0
ApsaraDB for MongoDB replica set instance
Version 4.0, 4.2, 4.4, 5.0, or 6.0
Schema synchronization
Full data synchronization
Incremental data synchronization
Two-way synchronization
Configure two-way data synchronization between ApsaraDB for MongoDB replica set instances
Synchronize data from a self-managed Redis database or an ApsaraDB for Redis instance
ImportantA Redis database is a NoSQL database and does not require schema synchronization.
Two-way data synchronization supports only Tair instances that use local disks, Tair dynamic random access memory (DRAM)-based instances that use cloud disks, and Tair persistent memory-optimized instances that use cloud disks.
If the source database is a self-managed Redis database or an ApsaraDB for Redis Community Edition instance, full data synchronization and incremental data synchronization are supported and collectively displayed as Incremental Data Synchronization.
Source database
Destination database
Synchronization type
Synchronization topology
References
Self-managed Redis database (standalone or cluster architecture)
Version 2.8, 3.0, 3.2, 4.0, 5.0, 6.0, or 7.0
ApsaraDB for Redis Community Edition instance (cluster, standard, or read/write splitting architecture)
Version 4.0, 5.0, 6.0, or 7.0
Tair instance (cluster, standard, or read/write splitting architecture)
Self-managed Redis database (standalone or cluster architecture)
Version 2.8, 3.0, 3.2, 4.0, 5.0, 6.0, or 7.0
ApsaraDB for Redis Community Edition instance (cluster, standard, or read/write splitting architecture)
Version 4.0, 5.0, 6.0, or 7.0
Tair instance (cluster, standard, or read/write splitting architecture)
Full data synchronization
Incremental data synchronization
One-way synchronization
Two-way synchronization
Synchronize data from a TiDB database
Source database
Destination database
Synchronization type
Synchronization topology
References
TiDB database
AnalyticDB for MySQL cluster
Version 2.0 or 3.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a self-managed TiDB database to an AnalyticDB for MySQL cluster
Synchronize data from a Db2 for LUW database
ImportantThe Db2 for LUW database is displayed as DB2 for LUW in the console.
A destination database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend that you update the instance to version 5.4.11 or later. For more information about how to update the version of an instance, see View and update the version of an instance.
Source database
Destination database
Synchronization type
Synchronization topology
References
Db2 for LUW database
Version 9.5, 9.7, 10.1, 10.5, 11.1, or 11.5
Self-managed MySQL database
Version 5.1, 5.5, 5.6, 5.7, or 8.0
ApsaraDB RDS for MySQL instance
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a Db2 for LUW database to an ApsaraDB RDS for MySQL instance
AnalyticDB for MySQL cluster
Version 3.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a Db2 for LUW database to an AnalyticDB for MySQL V3.0 cluster
PolarDB for MySQL cluster
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a Db2 for LUW database to a PolarDB for MySQL cluster
PolarDB-X 2.0 instance
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a Db2 for LUW database to a PolarDB-X 2.0 instance
AnalyticDB for PostgreSQL instance
Version 4.3, 6.0, or 7.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a Db2 for LUW database to an AnalyticDB for PostgreSQL instance
ApsaraMQ for Kafka instance
Versions 0.10.1.0 to 2.x
Self-managed Kafka cluster
Versions 0.10.1.0 to 2.7.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a Db2 for LUW database to a self-managed Kafka cluster
Synchronize data from a Db2 for i (AS/400) database
ImportantThe iSeries DB2 (AS/400) database is displayed as DB2 iSeries (AS/400) in the console.
Source database
Destination database
Synchronization type
Synchronization topology
References
Db2 for i database
Version 7.3 or 7.4
Self-managed MySQL database
Version 5.1, 5.5, 5.6, 5.7, or 8.0
ApsaraDB RDS for MySQL instance
All versions
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Available soon
PolarDB for MySQL cluster
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Available soon
Synchronize data from a DMS logical database
ImportantA logical database in Data Management (DMS) must be created based on the database shards of multiple PolarDB for MySQL clusters.
Source database
Destination database
Synchronization type
Synchronization topology
References
DMS logical database
AnalyticDB for MySQL cluster
Version 3.0
Schema synchronization
Full data synchronization
Incremental data synchronization
One-way synchronization
Synchronize data from a DMS logical database to an AnalyticDB for MySQL V3.0 cluster
Data migration
You can use DTS to migrate data between homogeneous and heterogeneous data sources. Typical scenarios include data migration to Alibaba Cloud, data migration between instances within Alibaba Cloud, and database splitting and scale-out.
For information about the supported databases, database engine versions, migration types, and how to configure a data migration task, see the following tables or Data migration scenarios.
Migrate data from a self-managed MySQL database or an ApsaraDB RDS for MySQL instance
ImportantA database in a PolarDB-X 1.0 instance must be created based on one or more ApsaraDB RDS for MySQL instances. DTS does not support PolarDB-X 1.0 databases that are created based on PolarDB for MySQL clusters.
For a data migration task whose destination database is a PolarDB-X 1.0 instance, schema migration is not supported. Schema migration is supported for a data migration task whose destination database is a PolarDB-X 2.0 instance.
A database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend that you update the instance to version 5.4.11 or later. For more information about how to update the version of an instance, see View and update the version of an instance.
Data migration to an AnalyticDB for MySQL 2.0 cluster is not supported in the new DTS console. You can configure a data migration task for this scenario only in the old DTS console.
Source database
Destination database
Migration type
References
Self-managed MySQL database
Version 5.1, 5.5, 5.6, 5.7, or 8.0
ApsaraDB RDS for MySQL instance
All versions
Self-managed MySQL database
Version 5.1, 5.5, 5.6, 5.7, or 8.0
ApsaraDB RDS for MySQL instance
All versions
Schema migration
Full data migration
Incremental data migration
PolarDB for MySQL cluster
All versions
Schema migration
Full data migration
Incremental data migration
PolarDB-X 1.0 or PolarDB-X 2.0 instance
Full data migration
Incremental data migration
AnalyticDB for MySQL cluster
Version 2.0 or 3.0
Schema migration
Full data migration
Incremental data migration
Migrate data from an ApsaraDB RDS for MySQL instance to an AnalyticDB for MySQL V3.0 cluster
AnalyticDB for PostgreSQL instance
Version 4.3, 6.0, or 7.0
Schema migration
Full data migration
Incremental data migration
Migrate data from an ApsaraDB RDS for MySQL instance to an AnalyticDB for PostgreSQL instance
Self-managed PostgreSQL database
Version 9.4.8 or later, such as 9.5, 9.6, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, or 16.x
ApsaraDB RDS for PostgreSQL instance
Version 9.4, 10, 11, 12, 13, 14, 15, or 16
Schema migration
Full data migration
Incremental data migration
Migrate data from an ApsaraDB RDS for MySQL instance to an ApsaraDB RDS for PostgreSQL instance
ApsaraMQ for Kafka instance
Versions 0.10.1.0 to 2.x
Self-managed Kafka cluster
Versions 0.10.1.0 to 2.7.0
Schema migration
Full data migration
Incremental data migration
Migrate data from an ApsaraDB RDS for MySQL instance to an ApsaraMQ for Kafka instance
ApsaraDB for ClickHouse cluster
Version 20.8 or later
Schema migration
Full data migration
Incremental data migration
Migrate data from an ApsaraDB RDS for MySQL instance to an ApsaraDB for ClickHouse cluster
DataHub project
All versions
Schema migration
Full data migration
Incremental data migration
Migrate data from an ApsaraDB RDS for MySQL instance to a DataHub project
Elasticsearch cluster
Version 5.5, 5.6, 6.x, or 7.x
Schema migration
Full data migration
Incremental data migration
Migrate data from an ApsaraDB RDS for MySQL instance to an Elasticsearch cluster
MaxCompute project
Schema migration
Full data migration
Incremental data migration
Migrate data from an ApsaraDB RDS for MySQL instance to a MaxCompute project
Db2 for LUW database
Version 9.5, 9.7, 10.1, 10.5, 11.1, or 11.5
Db2 for iSeries (AS/400) database
Version 7.3 or 7.4
Schema migration
Full data migration
Incremental data migration
Migrate data from an ApsaraDB RDS for MySQL instance to a Db2 for LUW database
Self-managed Oracle database (RAC or non-RAC architecture)
Version 9i, 10g, 11g, 12c, 18c, or 19c
Schema migration
Full data migration
Incremental data migration
Migrate data from an ApsaraDB RDS for MySQL instance to a self-managed Oracle database
ApsaraDB for Redis Community Edition instance (cluster, standard, or read/write splitting architecture)
Version 4.0, 5.0, 6.0, or 7.0
ApsaraDB for Redis Enhanced Edition (Tair) instance (cluster, standard, or read/write splitting architecture)
Full data migration
Incremental data migration
Migrate data from an ApsaraDB RDS for MySQL instance to a Tair or ApsaraDB for Redis instance
Tablestore instance
Schema migration
Full data migration
Incremental data migration
Migrate data from an ApsaraDB RDS for MySQL instance to a Tablestore instance
Migrate data from an ApsaraDB RDS for MariaDB instance
Source database
Destination database
Migration type
References
ApsaraDB RDS for MariaDB TX instance
Self-managed MariaDB database
ApsaraDB RDS for MariaDB TX instance
Self-managed MariaDB database
Schema migration
Full data migration
Incremental data migration
ApsaraDB RDS for MySQL instance
Schema migration
Full data migration
Incremental data migration
Migrate data from an ApsaraDB RDS for MariaDB instance to an ApsaraDB RDS for MySQL instance
ApsaraDB RDS for PostgreSQL instance
Schema migration
Full data migration
Incremental data migration
Migrate data from an ApsaraDB RDS for MariaDB instance to an ApsaraDB RDS for PostgreSQL instance
Migrate data from an ApsaraDB RDS for PPAS instance
Source database
Destination database
Migration type
References
ApsaraDB RDS for PPAS instance
All versions
PolarDB for PostgreSQL (Compatible with Oracle) cluster
All versions
Schema migration
Full data migration
Incremental data migration
Migrate data from an ApsaraDB RDS for PPAS instance to a PolarDB for Oracle cluster
Migrate data from a PolarDB for MySQL cluster
ImportantA database in a PolarDB-X 1.0 instance must be created based on one or more ApsaraDB RDS for MySQL instances. DTS does not support PolarDB-X 1.0 databases that are created based on PolarDB for MySQL clusters.
For a data migration task whose destination database is a PolarDB-X 1.0 instance, schema migration is not supported. Schema migration is supported for a data migration task whose destination database is a PolarDB-X 2.0 instance.
A database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend that you update the instance to version 5.4.11 or later. For more information about how to update the version of an instance, see View and update the version of an instance.
Source database
Destination database
Migration type
References
PolarDB for MySQL cluster
All versions
PolarDB for MySQL cluster
All versions
Schema migration
Full data migration
Incremental data migration
Self-managed MySQL database
Version 5.1, 5.5, 5.6, 5.7, or 8.0
ApsaraDB RDS for MySQL instance
All versions
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB for MySQL cluster to an ApsaraDB RDS for MySQL instance
PolarDB-X 1.0 or PolarDB-X 2.0 instance
Full data migration
Incremental data migration
Migrate data from a PolarDB for MySQL cluster to a PolarDB-X 2.0 instance
AnalyticDB for MySQL cluster
Version 3.0
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB for MySQL cluster to an AnalyticDB for MySQL V3.0 cluster
AnalyticDB for PostgreSQL instance
Version 4.3, 6.0, or 7.0
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB for MySQL cluster to an AnalyticDB for PostgreSQL instance
ApsaraMQ for Kafka instance
Versions 0.10.1.0 to 2.x
Self-managed Kafka cluster
Versions 0.10.1.0 to 2.7.0
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB for MySQL cluster to a Kafka cluster
DataHub project
All versions
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB for MySQL cluster to a DataHub project
ApsaraDB for ClickHouse cluster
Version 20.8 or later
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB for MySQL cluster to an ApsaraDB for ClickHouse cluster
Self-managed Oracle database (RAC, PDB, or non-RAC architecture)
Version 9i, 10g, 11g, 12c, 18c, or 19c
Schema migration
Full data migration
Incremental data migration
Available soon
Elasticsearch cluster
Version 5.5, 5.6, 6.x, or 7.x
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB for MySQL cluster to an Elasticsearch cluster
MaxCompute project
Schema migration
Full data migration
Incremental data migration
Available soon
Migrate data from a PolarDB for PostgreSQL (Compatible with Oracle) cluster
Source database
Destination database
Migration type
References
PolarDB for PostgreSQL (Compatible with Oracle) cluster
All versions
PolarDB for PostgreSQL (Compatible with Oracle) cluster
All versions
Schema migration
Full data migration
Incremental data migration
Migrate data between PolarDB for PostgreSQL (Compatible with Oracle) clusters
Self-managed Oracle database (RAC, PDB, or non-RAC architecture)
Version 9i, 10g, 11g, 12c, 18c, or 19c
Full data migration
Incremental data migration
ApsaraMQ for Kafka instance
Versions 0.10.1.0 to 2.x
Self-managed Kafka cluster
Versions 0.10.1.0 to 2.7.0
Incremental data migration
Available soon
AnalyticDB for MySQL cluster
Version 3.0
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB-X instance
ImportantYou can configure a data migration task for this scenario only in the new DTS console.
A database in a PolarDB-X 1.0 instance must be created based on one or more ApsaraDB RDS for MySQL instances. DTS does not support PolarDB-X 1.0 databases that are created based on PolarDB for MySQL clusters.
A database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend that you update the instance to version 5.4.11 or later. For more information about how to update the version of an instance, see View and update the version of an instance.
Source database
Destination database
Migration type
References
PolarDB-X 1.0 instance
PolarDB-X 2.0 instance
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB-X 1.0 instance to a PolarDB-X 2.0 instance
AnalyticDB for MySQL cluster
Version 3.0
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB-X 1.0 instance to an AnalyticDB for MySQL V3.0 cluster
AnalyticDB for PostgreSQL instance
Version 4.3, 6.0, or 7.0
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB-X 1.0 instance to an AnalyticDB for PostgreSQL instance
DataHub project
Schema migration
Incremental data migration
Migrate data from a PolarDB-X 1.0 instance to a DataHub project
Elasticsearch cluster
Version 5.5, 5.6, 6.x, or 7.x
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB-X 1.0 instance to an Elasticsearch cluster
ApsaraMQ for Kafka instance
Versions 0.10.1.0 to 2.x
Self-managed Kafka cluster
Versions 0.10.1.0 to 2.7.0
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB-X 1.0 instance to an ApsaraMQ for Kafka instance
Self-managed MySQL database
Version 5.1, 5.5, 5.6, 5.7, or 8.0
ApsaraDB RDS for MySQL instance
All versions
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB-X 1.0 instance to an ApsaraDB RDS for MySQL instance
PolarDB-X 2.0 instance
PolarDB-X 2.0 instance
Schema migration
Full data migration
Incremental data migration
Self-managed MySQL database
Version 5.1, 5.5, 5.6, 5.7, or 8.0
ApsaraDB RDS for MySQL instance
All versions
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB-X 2.0 instance to an ApsaraDB RDS for MySQL instance
PolarDB for MySQL cluster
All versions
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB-X 2.0 instance to a PolarDB for MySQL cluster
AnalyticDB for MySQL cluster
Version 3.0
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB-X 2.0 instance to an AnalyticDB for MySQL V3.0 cluster
AnalyticDB for PostgreSQL instance
Version 4.3, 6.0, or 7.0
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB-X 2.0 instance to an AnalyticDB for PostgreSQL instance
MaxCompute project
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB-X 2.0 instance to a MaxCompute project
ApsaraMQ for Kafka instance
Versions 0.10.1.0 to 2.x
Self-managed Kafka cluster
Versions 0.10.1.0 to 2.7.0
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB-X 2.0 instance to a Message Queue for Apache Kafka instance
DataHub project
All versions
Schema migration
Incremental data migration
Migrate data from a PolarDB-X 2.0 instance to a DataHub project
Elasticsearch cluster
Version 5.5, 5.6, 6.x, or 7.x
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB-X 2.0 instance to an Elasticsearch cluster
Self-managed Oracle database (RAC or non-RAC architecture)
Version 9i, 10g, 11g, 12c, 18c, or 19c
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB-X 2.0 instance to a self-managed Oracle database
Tablestore instance
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB-X 2.0 instance to a Tablestore instance
Migrate data from a PolarDB for PostgreSQL cluster
Source database
Destination database
Migration type
References
PolarDB for PostgreSQL cluster
Version 11 or 14
PolarDB for PostgreSQL cluster
Version 11 or 14
Schema migration
Full data migration
Incremental data migration
Available soon
Self-managed PostgreSQL database
Version 9.5.x, 9.6.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, or 16.x
ApsaraDB RDS for PostgreSQL instance
Version 9.4, 10, 11, 12, 13, 14, 15, or 16
Schema migration
Full data migration
Incremental data migration
Migrate data from a PolarDB for PostgreSQL cluster to an ApsaraDB RDS for PostgreSQL instance
Self-managed Oracle database (RAC or non-RAC architecture)
Version 9i, 10g, 11g, 12c, 18c, or 19c
Full data migration
Incremental data migration
Migrate data from a PolarDB for PostgreSQL cluster to a self-managed Oracle database
AnalyticDB for PostgreSQL instance
Version 4.3, 6.0, or 7.0
Schema migration
Full data migration
Incremental data migration
Available soon
Migrate data from a MaxCompute project
Source database
Destination database
Migration type
References
MaxCompute project
All versions
Self-managed MySQL database
Version 5.1, 5.5, 5.6, 5.7, or 8.0
ApsaraDB RDS for MySQL instance
All versions
Schema migration
Full data migration
Migrate data from a MaxCompute project to an ApsaraDB RDS for MySQL instance
Migrate data from an Oracle database
ImportantA database in a PolarDB-X 1.0 instance must be created based on one or more ApsaraDB RDS for MySQL instances. DTS does not support PolarDB-X 1.0 databases that are created based on PolarDB for MySQL clusters.
For a data migration task whose destination database is a PolarDB-X 1.0 instance, schema migration is not supported. Schema migration is supported for a data migration task whose destination database is a PolarDB-X 2.0 instance.
A database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend that you update the instance to version 5.4.11 or later. For more information about how to update the version of an instance, see View and update the version of an instance.
Source database
Destination database
Migration type
References
Self-managed Oracle database (RAC or non-RAC architecture)
Version 9i, 10g, 11g, 12c, 18c, or 19c
PolarDB for PostgreSQL (Compatible with Oracle) cluster
All versions
Schema migration
Full data migration
Incremental data migration
Self-managed Oracle database (RAC or non-RAC architecture)
Version 9i, 10g, 11g, 12c, 18c, or 19c
Schema migration
Full data migration
Incremental data migration
Self-managed MySQL database
Version 5.1, 5.5, 5.6, 5.7, or 8.0
ApsaraDB RDS for MySQL instance
All versions
Schema migration
Full data migration
Incremental data migration
Migrate data from a self-managed Oracle database to an ApsaraDB RDS for MySQL instance
PolarDB for MySQL cluster
All versions
Schema migration
Full data migration
Incremental data migration
Migrate data from a self-managed Oracle database to a PolarDB for MySQL cluster
PolarDB for PostgreSQL cluster
Version 11 or 14
Schema migration
Full data migration
Incremental data migration
Available soon
PolarDB-X 1.0 or PolarDB-X 2.0 instance
Full data migration
Incremental data migration
Migrate data from a self-managed Oracle database to a PolarDB-X 1.0 instance
AnalyticDB for MySQL cluster
Version 3.0
Schema migration
Full data migration
Incremental data migration
Migrate data from a self-managed Oracle database to an AnalyticDB for MySQL V3.0 cluster
AnalyticDB for PostgreSQL instance
Version 4.3, 6.0, or 7.0
Schema migration
Full data migration
Incremental data migration
Migrate data from a self-managed Oracle database to an AnalyticDB for PostgreSQL instance
Self-managed PostgreSQL database
Version 9.4.8 or later, such as 9.5, 9.6, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, or 16.x
ApsaraDB RDS for PostgreSQL instance
Version 9.4, 10, 11, 12, 13, 14, 15, or 16
Schema migration
Full data migration
Incremental data migration
ApsaraMQ for Kafka instance
Versions 0.10.1.0 to 2.x
Self-managed Kafka cluster
Versions 0.10.1.0 to 2.7.0
Schema migration
Full data migration
Incremental data migration
Migrate data from a self-managed Oracle database to an ApsaraMQ for Kafka instance
DataHub project
All versions
Schema migration
Full data migration
Incremental data migration
Available soon
Migrate data from a self-managed PostgreSQL database or an ApsaraDB RDS for PostgreSQL instance
Source database
Destination database
Migration type
References
Self-managed PostgreSQL database
Version 9.4.8 or later, such as 9.5, 9.6, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, or 16.x
ApsaraDB RDS for PostgreSQL instance
Version 9.4, 10, 11, 12, 13, 14, 15, or 16
Self-managed PostgreSQL database
Version 9.4.8 or later, such as 9.5, 9.6, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, or 16.x
ApsaraDB RDS for PostgreSQL instance
Version 9.4, 10, 11, 12, 13, 14, 15, or 16
Schema migration
Full data migration
Incremental data migration
PolarDB for PostgreSQL cluster
Version 11 or 14
Schema migration
Full data migration
Incremental data migration
Migrate data from a self-managed PostgreSQL database to a PolarDB for PostgreSQL cluster
Self-managed MySQL database
Version 5.1, 5.5, 5.6, 5.7, or 8.0
ApsaraDB RDS for MySQL instance
All versions
Full data migration
Incremental data migration
Migrate data from an ApsaraDB RDS for PostgreSQL instance to an ApsaraDB RDS for MySQL instance
PolarDB for PostgreSQL (Compatible with Oracle) cluster
All versions
Full data migration
Incremental data migration
AnalyticDB for PostgreSQL instance
Version 4.3, 6.0, or 7.0
Schema migration
Full data migration
Incremental data migration
Migrate data from a self-managed PostgreSQL database to an AnalyticDB for PostgreSQL instance
Migrate data from a self-managed SQL Server database or an ApsaraDB RDS for SQL Server instance
ImportantThe source self-managed SQL Server database must be one of the following editions: Enterprise, Developer, Enterprise Evaluation, and Standard.
The destination self-managed SQL Server database must be one of the following editions: Enterprise, Developer, Enterprise Evaluation, and Standard.
If the version of the self-managed SQL Server database is 2005 or the version of the ApsaraDB RDS for SQL Server instance is 2008 or 2008 R2, incremental data migration is not supported for this scenario.
DTS supports SQL Server clusters and SQL Server Always On availability groups (AOAGs).
If the SQL Server Incremental Synchronization Mode parameter is set to Log-based Parsing for Non-heap Tables and CDC-based Incremental Synchronization for Heap Tables, data is migrated in the hybrid log-based parsing mode and the following versions of source databases are supported:
Self-managed SQL Server or ApsaraDB RDS for SQL Server database of the Enterprise or Enterprise Evaluation edition: version 2012, 2014, 2016, 2019, or 2022.
Self-managed SQL Server or ApsaraDB RDS for SQL Server database of the Standard edition: version 2016, 2019, or 2022.
Source database
Destination database
Migration type
References
Self-managed SQL Server database
Version 2005, 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019 or 2022
ApsaraDB RDS for SQL Server instance
Version 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019, or 2022
Self-managed SQL Server database
Version 2005, 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019 or 2022
ApsaraDB RDS for SQL Server instance
Version 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019, or 2022
Schema migration
Full data migration
Incremental data migration
Self-managed MySQL database
Version 5.1, 5.5, 5.6, 5.7, or 8.0
ApsaraDB RDS for MySQL instance
All versions
Schema migration
Full data migration
Incremental data migration
Migrate data from an ApsaraDB RDS for SQL Server instance to an ApsaraDB RDS for MySQL instance
PolarDB for MySQL cluster
All versions
Schema migration
Full data migration
Incremental data migration
Migrate data from an ApsaraDB RDS for SQL Server instance to a PolarDB for MySQL cluster
AnalyticDB for MySQL cluster
Version 3.0
Schema migration
Full data migration
Incremental data migration
Migrate data from an ApsaraDB RDS for SQL Server instance to an AnalyticDB for MySQL V3.0 cluster
AnalyticDB for PostgreSQL instance
Version 4.3, 6.0, or 7.0
Schema migration
Full data migration
Incremental data migration
Migrate data from a self-managed SQL Server database to an AnalyticDB for PostgreSQL instance
DataHub project
Schema migration
Incremental data migration
Migrate data from an ApsaraDB RDS for SQL Server instance to a DataHub project
Migrate data from a self-managed MongoDB database or an ApsaraDB for MongoDB instance
Source database
Destination database
Migration type
References
Standalone architecture
Self-managed MongoDB database
Versions 2.8 to 6.0
ApsaraDB for MongoDB instance
Version 3.4 or 4.0
Standalone, replica set, or sharded cluster architecture
Self-managed MongoDB database
Versions 2.8 to 6.0
ApsaraDB for MongoDB instance
Version 3.4, 4.0, 4.2, 4.4, 5.0, or 6.0
Schema migration
Full data migration
Replica set architecture
Self-managed MongoDB database
Versions 2.8 to 6.0
ApsaraDB for MongoDB instance
Version 3.4, 4.0, 4.2, 4.4, 5.0, or 6.0
Replica set or sharded cluster architecture
Self-managed MongoDB database
Versions 2.8 to 6.0
ApsaraDB for MongoDB instance
Version 3.4, 4.0, 4.2, 4.4, 5.0, or 6.0
Schema migration
Full data migration
Incremental data migration
Sharded cluster architecture
Self-managed MongoDB database
Versions 2.8 to 6.0
ApsaraDB for MongoDB instance
Version 3.4, 4.0, 4.2, 4.4, 5.0, or 6.0
Replica set or sharded cluster architecture
Self-managed MongoDB database
Versions 2.8 to 6.0
ApsaraDB for MongoDB instance
Version 3.4, 4.0, 4.2, 4.4, 5.0, or 6.0
Schema migration
Full data migration
Incremental data migration
Replica set or sharded cluster architecture
Self-managed MongoDB database
Versions 2.8 to 6.0
ApsaraDB for MongoDB instance
Version 3.4, 4.0, 4.2, 4.4, 5.0, or 6.0
Lindorm instance
Full data migration
Incremental data migration
Migrate data from an ApsaraDB for MongoDB instance to a Lindorm instance
Migrate data from a self-managed Redis database or an ApsaraDB for Redis instance
ImportantA Redis database is a NoSQL database and does not require schema migration.
If the source database is a self-managed Redis database or an ApsaraDB for Redis Community Edition instance, full data migration and incremental data migration are supported and collectively displayed as Incremental Data Migration.
Source database
Destination database
Migration type
References
Self-managed Redis database (standalone or cluster architecture)
Version 2.8, 3.0, 3.2, 4.0, 5.0, 6.0, or 7.0
ApsaraDB for Redis Community Edition instance (standard or read/write splitting architecture)
Version 4.0, 5.0, 6.0, or 7.0
Tair instance (standard or read/write splitting architecture)
Self-managed Redis database (standalone or cluster architecture)
Version 2.8, 3.0, 3.2, 4.0, 5.0, 6.0, or 7.0
ApsaraDB for Redis Community Edition instance (cluster, standard, or read/write splitting architecture)
Version 4.0, 5.0, 6.0, or 7.0
Tair instance (cluster, standard, or read/write splitting architecture)
Full data migration
Incremental data migration
Migrate data from a TiDB database
ImportantYou can configure a data migration task for this scenario only in the old DTS console.
Source database
Destination database
Migration type
References
TiDB database
Self-managed MySQL database
Version 5.1, 5.5, 5.6, 5.7, or 8.0
ApsaraDB RDS for MySQL instance
All versions
Schema migration
Full data migration
Incremental data migration
PolarDB for MySQL cluster
All versions
Schema migration
Full data migration
Incremental data migration
Available soon
AnalyticDB for MySQL cluster
Version 3.0
Schema migration
Full data migration
Incremental data migration
Available soon
Migrate data from a Db2 for LUW database
ImportantThe Db2 for LUW database is displayed as DB2 for LUW in the DTS console.
A destination database in a PolarDB-X 2.0 instance must be compatible with MySQL 5.7. We recommend that you update the instance to version 5.4.11 or later. For more information about how to update the version of an instance, see View and update the version of an instance.
Source database
Destination database
Migration type
References
Db2 for LUW database
Version 9.5, 9.7, 10.1, 10.5, 11.1, or 11.5
Self-managed MySQL database
Version 5.1, 5.5, 5.6, 5.7, or 8.0
ApsaraDB RDS for MySQL instance
All versions
Schema migration
Full data migration
Incremental data migration
Migrate data from a self-managed Db2 database to an ApsaraDB RDS for MySQL instance
PolarDB-X 2.0 instance
Full data migration
Incremental data migration
Migrate data from a Db2 for LUW database to a PolarDB-X 2.0 instance
AnalyticDB for PostgreSQL instance
Version 4.3, 6.0, or 7.0
Schema migration
Full data migration
Incremental data migration
Migrate data from a Db2 for LUW database to an AnalyticDB for PostgreSQL instance
ApsaraMQ for Kafka instance
Versions 0.10.1.0 to 2.x
Self-managed Kafka cluster
Versions 0.10.1.0 to 2.7.0
Schema migration
Full data migration
Incremental data migration
Migrate data from a Db2 for LUW database to an ApsaraMQ for Kafka instance
PolarDB for MySQL cluster
Schema migration
Full data migration
Incremental data migration
Migrate data from a Db2 for LUW database to a PolarDB for MySQL cluster
AnalyticDB for MySQL cluster
Version 3.0
Schema migration
Full data migration
Incremental data migration
Available soon
Migrate data from a self-managed Db2 for i database
ImportantThe Db2 for iSeries (AS/400) database is displayed as DB2 for iSeries (AS/400) in the DTS console.
Source database
Destination database
Migration type
References
Db2 for iSeries (AS/400) database
Version 7.3 or 7.4
Self-managed MySQL database
Version 5.1, 5.5, 5.6, 5.7, or 8.0
ApsaraDB RDS for MySQL instance
All versions
Schema migration
Full data migration
Incremental data migration
Available soon
PolarDB for MySQL cluster
Schema migration
Full data migration
Incremental data migration
Available soon
Migrate data from a Teradata database
ImportantYou can configure a data migration task for this scenario only in the new DTS console, and the data migration instance must reside in the China (Shanghai), China (Qingdao), or China (Zhangjiakou) region.
Source database
Destination database
Migration type
References
Teradata database
Version 17 or earlier
AnalyticDB for PostgreSQL instance
Version 4.3, 6.0, or 7.0
Schema migration
Full data migration
Migrate data from a Teradata database to an AnalyticDB for PostgreSQL instance
Migrate data from a self-managed HBase database
ImportantYou can configure a data migration task for this scenario only in the new DTS console.
Source database
Destination database
Migration type
References
Self-managed HBase database
Version 1.x
AnalyticDB for MySQL cluster
Version 3.0
Schema migration
Full data migration
Migrate data from a self-managed HBase database to an AnalyticDB for MySQL V3.0 cluster
Migrate data from a database hosted on a third-party cloud
You can use DTS to migrate data from a database hosted on a third-party cloud such as Amazon RDS for MySQL and Amazon RDS for Oracle to an Alibaba Cloud database, such as ApsaraDB RDS for MySQL.
Source database
Destination database
Migration type
References
Amazon RDS for MySQL instance
ApsaraDB RDS for MySQL instance
Schema migration
Full data migration
Incremental data migration
Migrate data from an Amazon RDS for MySQL instance to an ApsaraDB RDS for MySQL instance
Amazon RDS for Oracle instance
ApsaraDB RDS for MySQL instance
Schema migration
Full data migration
Incremental data migration
Migrate data from an Amazon RDS for Oracle instance to an ApsaraDB RDS for MySQL instance
Amazon RDS for PostgreSQL instance
ApsaraDB RDS for PostgreSQL instance
Schema migration
Full data migration
Incremental data migration
Schema migration
Full data migration
Amazon RDS for SQL Server instance
ApsaraDB RDS for SQL Server instance
Schema migration
Full data migration
Amazon Aurora MySQL cluster
ApsaraDB RDS for MySQL instance
Schema migration
Full data migration
Incremental data migration
Migrate data from an Amazon Aurora MySQL cluster to an ApsaraDB RDS for MySQL instance
PolarDB for MySQL cluster
Schema migration
Full data migration
Incremental data migration
Amazon Aurora PostgreSQL instance
ApsaraDB RDS for PostgreSQL instance
Schema migration
Full data migration
Migrate data from Amazon Aurora PostgreSQL to an ApsaraDB RDS for PostgreSQL instance
MongoDB Atlas database
ApsaraDB for MongoDB instance
Full data migration
Incremental data migration
Migrate data from a MongoDB Atlas database to ApsaraDB for MongoDB by using DTS
Data migration can partly achieve data synchronization in specific scenarios. However, data migration and data synchronization differ in scenarios, supported databases, features, and billing. For more information about the differences between data migration and data synchronization, see What are the differences between data migration and data synchronization?
If you need to migrate incremental data for a long period of time, we recommend that you use data synchronization, which can achieve better performance and network stability.
Change tracking
You can use DTS to track data changes from databases in real time. Then, you can consume the tracked data in the following scenarios: cache updates, asynchronous business decoupling, data synchronization between heterogeneous data sources, and data synchronization with extract, transform, and load (ETL) operations. Change tracking allows you to track incremental data of a variety of databases in real-time, such as a self-managed MySQL database and an ApsaraDB RDS for MySQL instance. You can use different clients to consume tracked data, such as SDK clients and Flink clients. For information about the supported change tracking solutions and how to configure a change tracking task, see the following table or Change tracking scenarios.
Source database | Data change type | Reference |
|
| |
PolarDB for MySQL All versions |
| |
PolarDB-X 1.0 Important A database in a PolarDB-X instance must be created based on ApsaraDB RDS for MySQL instances. DTS does not support PolarDB-X databases that are created based on PolarDB for MySQL clusters. |
| |
PolarDB-X 2.0 Important A database in a PolarDB-X instance must be created based on ApsaraDB RDS for MySQL instances. DTS does not support PolarDB-X databases that are created based on PolarDB for MySQL clusters. |
| |
PolarDB for PostgreSQL (Compatible with Oracle) All versions | Data update | |
Self-managed Oracle database (non-RAC architecture) Supported versions: 9i, 10g, and 11g |
| |
| Data update | Track data changes from an ApsaraDB RDS for PostgreSQL instance |
Data Management (DMS) logical database Important A logical database in DMS must be created based on the database shards of multiple PolarDB for MySQL clusters. | Data update | |
PolarDB for PostgreSQL Supported versions: 11 and 14 |
|