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.
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.
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.
Synchronization solutions for a self-managed MySQL database or an RDS for MySQL instance
ImportantDatabases in PolarDB-X 1.0 must be created based on RDS for MySQL. DTS does not support databases created based on PolarDB for MySQL.
When PolarDB-X 1.0 is the destination, schema synchronization and initial schema synchronization are not supported. Both are supported when PolarDB-X 2.0 is the destination.
PolarDB-X 2.0 instances must be version 5.4.11 or later. For upgrade instructions, see View and upgrade the instance version.
Source database
Destination database
Synchronization type
Topology
Configuration guide
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
Schema synchronization, full data synchronization, incremental data synchronization
One-way, two-way
Synchronize data from a self-managed MySQL database to an RDS for MySQL instance / One-way synchronization between RDS for MySQL instances / Two-way synchronization between MySQL databases / Synchronize RDS for MySQL instances across Alibaba Cloud accounts
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
PolarDB for MySQL (all versions)
Schema synchronization, full data synchronization, incremental data synchronization
One-way, two-way
Synchronize data from RDS for MySQL to PolarDB for MySQL / Two-way synchronization between a MySQL database and a PolarDB for MySQL instance
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, 19c)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from RDS for MySQL to a self-managed Oracle database
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
PolarDB-X 1.0
Full data synchronization, incremental data synchronization
One-way
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
PolarDB-X 2.0
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
AnalyticDB for MySQL (2.0, 3.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from RDS for MySQL to AnalyticDB for MySQL 3.0 / Synchronize data from RDS to AnalyticDB for MySQL
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
Self-managed PostgreSQL (9.5.x–17.x) / RDS for PostgreSQL (9.4, 10–17)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
AnalyticDB for PostgreSQL (4.3, 6.0, 7.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from RDS for MySQL to AnalyticDB for PostgreSQL
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
Alibaba Cloud Message Queue for Kafka (0.10.1.0–2.x) / Self-managed Kafka (0.10.1.0–2.7.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from RDS for MySQL to Alibaba Cloud Message Queue for Kafka
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
ApsaraDB for ClickHouse cluster (version 20.8 and later)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from RDS for MySQL to an ApsaraDB for ClickHouse cluster
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
DataHub
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
Elasticsearch (5.5, 5.6, 6.x, 7.x, 8.x)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
MaxCompute
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
ApsaraDB for Tair (compatible with Redis) cluster/standard/read-write splitting (4.0, 5.0, 6.0, 7.0)
Full data synchronization, incremental data synchronization
One-way
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
Tablestore
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
Function Compute (FC) version 2.0
Full data synchronization, incremental data synchronization
One-way
Synchronize data from RDS for MySQL to Function Compute (FC)
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
ApsaraDB for SelectDB
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from RDS for MySQL to ApsaraDB for SelectDB
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
Lindorm
Full data synchronization, incremental data synchronization
One-way
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
Doris (version 1.2 and later)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from RDS for MySQL to a self-managed Doris cluster
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
ApsaraMQ for RocketMQ (4.x and 5.x)
Full data synchronization, incremental data synchronization
One-way
Synchronize data from RDS for MySQL to ApsaraMQ for RocketMQ
Synchronization solutions for a PolarDB for MySQL cluster
ImportantDatabases in PolarDB-X 1.0 must be created based on RDS for MySQL. DTS does not support databases created based on PolarDB for MySQL.
When PolarDB-X 1.0 is the destination, schema synchronization and initial schema synchronization are not supported. Both are supported when PolarDB-X 2.0 is the destination.
PolarDB-X 2.0 instances must be version 5.4.11 or later. For upgrade instructions, see View and upgrade the instance version.
Source database
Destination database
Synchronization type
Topology
Configuration guide
PolarDB for MySQL (all versions)
PolarDB for MySQL (all versions)
Schema synchronization, full data synchronization, incremental data synchronization
One-way, two-way
One-way synchronization between PolarDB for MySQL instances / Two-way synchronization between PolarDB for MySQL instances
PolarDB for MySQL (all versions)
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
Schema synchronization, full data synchronization, incremental data synchronization
One-way, two-way
PolarDB for MySQL (all versions)
PolarDB-X 1.0
Full data synchronization, incremental data synchronization
One-way
PolarDB for MySQL (all versions)
PolarDB-X 2.0
Schema synchronization, full data synchronization, incremental data synchronization
One-way
PolarDB for MySQL (all versions)
AnalyticDB for MySQL (2.0, 3.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from PolarDB for MySQL to AnalyticDB for MySQL 3.0 / Synchronize data from PolarDB for MySQL to AnalyticDB for MySQL
PolarDB for MySQL (all versions)
AnalyticDB for PostgreSQL (4.3, 6.0, 7.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from PolarDB for MySQL to AnalyticDB for PostgreSQL
PolarDB for MySQL (all versions)
Alibaba Cloud Message Queue for Kafka (0.10.1.0–2.x) / Self-managed Kafka (0.10.1.0–2.7.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from PolarDB for MySQL to Alibaba Cloud Message Queue for Kafka
PolarDB for MySQL (all versions)
DataHub
Schema synchronization, full data synchronization, incremental data synchronization
One-way
PolarDB for MySQL (all versions)
ApsaraDB for ClickHouse cluster (version 20.8 and later)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from PolarDB for MySQL to an ApsaraDB for ClickHouse cluster
PolarDB for MySQL (all versions)
Elasticsearch (5.5, 5.6, 6.x, 7.x, 8.x)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
PolarDB for MySQL (all versions)
MaxCompute
Schema synchronization, full data synchronization, incremental data synchronization
One-way
PolarDB for MySQL (all versions)
Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, 19c)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from PolarDB for MySQL to a self-managed Oracle database
PolarDB for MySQL (all versions)
ApsaraDB for SelectDB
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from PolarDB for MySQL to ApsaraDB for SelectDB
PolarDB for MySQL (all versions)
Doris (version 1.2 and later)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from PolarDB for MySQL to a self-managed Doris cluster
PolarDB for MySQL (all versions)
Lindorm
Full data synchronization, incremental data synchronization
One-way
Synchronization solutions for a PolarDB for PostgreSQL cluster
Source database
Destination database
Synchronization type
Topology
Configuration guide
PolarDB for PostgreSQL (versions 11, 14, 15, 16, 17)
Self-managed PostgreSQL (9.5.x–17.x) / RDS for PostgreSQL (9.4, 10–17)
Schema synchronization, full data synchronization, incremental data synchronization
One-way, two-way
Synchronize data from PolarDB for PostgreSQL to RDS for PostgreSQL / Two-way synchronization between PolarDB for PostgreSQL and RDS for PostgreSQL
PolarDB for PostgreSQL (versions 11, 14, 15, 16, 17)
PolarDB for PostgreSQL (versions 11, 14, 15, 16, 17)
Schema synchronization, full data synchronization, incremental data synchronization
One-way, two-way
One-way synchronization between PolarDB for PostgreSQL instances / Two-way synchronization between PolarDB for PostgreSQL instances
PolarDB for PostgreSQL (versions 11, 14, 15, 16, 17)
AnalyticDB for PostgreSQL (4.3, 6.0, 7.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from PolarDB for PostgreSQL to AnalyticDB for PostgreSQL
PolarDB for PostgreSQL (versions 11, 14, 15, 16, 17)
ApsaraDB for SelectDB
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from PolarDB for PostgreSQL to ApsaraDB for SelectDB
Synchronization solutions for a PolarDB-X instance
ImportantDatabases in PolarDB-X 1.0 must be created based on RDS for MySQL. DTS does not support databases created based on PolarDB for MySQL.
When PolarDB-X 1.0 is the destination, schema synchronization and initial schema synchronization are not supported. Both are supported when PolarDB-X 2.0 is the destination.
PolarDB-X 2.0 instances must be version 5.4.11 or later. For upgrade instructions, see View and upgrade the instance version.
Source database
Destination database
Synchronization type
Topology
Configuration guide
PolarDB-X 1.0
PolarDB-X 1.0
Full data synchronization, incremental data synchronization
One-way
PolarDB-X 1.0
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
PolarDB-X 1.0
PolarDB for MySQL (all versions)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
PolarDB-X 1.0
AnalyticDB for MySQL (version 3.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from PolarDB-X 1.0 to AnalyticDB for MySQL 3.0
PolarDB-X 1.0
DataHub
Schema synchronization, incremental data synchronization
One-way
PolarDB-X 1.0
AnalyticDB for PostgreSQL (4.3, 6.0, 7.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from PolarDB-X 1.0 to AnalyticDB for PostgreSQL
PolarDB-X 1.0
Alibaba Cloud Message Queue for Kafka (0.10.1.0–2.x) / Self-managed Kafka (0.10.1.0–2.7.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from PolarDB-X 1.0 to Alibaba Cloud Message Queue for Kafka
PolarDB-X 1.0
Elasticsearch (5.5, 5.6, 6.x, 7.x, 8.x)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
PolarDB-X 1.0
PolarDB-X 2.0
Schema synchronization, full data synchronization, incremental data synchronization
One-way
PolarDB-X 2.0
PolarDB-X 2.0
Schema synchronization, full data synchronization, incremental data synchronization
One-way, two-way
One-way synchronization between PolarDB-X 2.0 instances / Two-way synchronization between PolarDB-X 2.0 instances
PolarDB-X 2.0
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
PolarDB-X 2.0
PolarDB for MySQL (all versions)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
PolarDB-X 2.0
AnalyticDB for MySQL (version 3.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from PolarDB-X 2.0 to AnalyticDB for MySQL 3.0
PolarDB-X 2.0
Alibaba Cloud Message Queue for Kafka (0.10.1.0–2.x) / Self-managed Kafka (0.10.1.0–2.7.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from PolarDB-X 2.0 to Alibaba Cloud Message Queue for Kafka
PolarDB-X 2.0
DataHub
Schema synchronization, incremental data synchronization
One-way
PolarDB-X 2.0
MaxCompute
Schema synchronization, full data synchronization, incremental data synchronization
One-way
PolarDB-X 2.0
AnalyticDB for PostgreSQL (4.3, 6.0, 7.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from PolarDB-X 2.0 to AnalyticDB for PostgreSQL
PolarDB-X 2.0
Elasticsearch (5.5, 5.6, 6.x, 7.x, 8.x)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
PolarDB-X 2.0
Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, 19c)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from PolarDB-X 2.0 to a self-managed Oracle database
PolarDB-X 2.0
Tablestore
Schema synchronization, full data synchronization, incremental data synchronization
One-way
PolarDB-X 2.0
PolarDB-X 1.0
Full data synchronization, incremental data synchronization
One-way
PolarDB-X 2.0
ApsaraDB for SelectDB
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from PolarDB-X 2.0 to ApsaraDB for SelectDB
Synchronization solutions for a PolarDB for PostgreSQL (Compatible with Oracle) cluster
Source database
Destination database
Synchronization type
Topology
Configuration guide
PolarDB for PostgreSQL (Compatible with Oracle) (all versions)
PolarDB for PostgreSQL (Compatible with Oracle) (all versions)
Schema synchronization, full data synchronization, incremental data synchronization
One-way, two-way
One-way synchronization between PolarDB for PostgreSQL (Compatible with Oracle) clusters / Two-way synchronization between PolarDB for PostgreSQL (Compatible with Oracle) clusters
PolarDB for PostgreSQL (Compatible with Oracle) (all versions)
Alibaba Cloud Message Queue for Kafka (0.10.1.0–2.x) / Self-managed Kafka (0.10.1.0–2.7.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
PolarDB for PostgreSQL (Compatible with Oracle) (all versions)
AnalyticDB for MySQL (version 3.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronization solutions for an Oracle database
ImportantThis source type can only be configured in the new DTS console.
The destination PolarDB-X 2.0 instance must be version 5.4.11 or later. For upgrade instructions, see View and upgrade the instance version.
Source database
Destination database
Synchronization type
Topology
Configuration guide
Self-managed Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, 19c)
AnalyticDB for PostgreSQL (4.3, 6.0, 7.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from a self-managed Oracle database to AnalyticDB for PostgreSQL
Self-managed Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, 19c)
DataHub
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from a self-managed Oracle database to DataHub
Self-managed Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, 19c)
PolarDB-X 2.0
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from a self-managed Oracle database to PolarDB-X 2.0
Self-managed Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, 19c)
PolarDB for MySQL (all versions)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from a self-managed Oracle database to PolarDB for MySQL
Self-managed Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, 19c)
MaxCompute
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from a self-managed Oracle database to MaxCompute
Self-managed Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, 19c)
PolarDB for PostgreSQL (Compatible with Oracle) (all versions)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Self-managed Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, 19c)
Alibaba Cloud Message Queue for Kafka (0.10.1.0–2.x)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from a self-managed Oracle database to Alibaba Cloud Message Queue for Kafka
Synchronization solutions for a self-managed PostgreSQL database or an RDS for PostgreSQL instance
ImportantRDS for PostgreSQL Serverless instances are not supported as a source database but are supported as a destination database.
Source database
Destination database
Synchronization type
Topology
Configuration guide
Self-managed PostgreSQL (9.5.x–17.x) / RDS for PostgreSQL (9.4, 10–17)
Self-managed PostgreSQL (9.5.x–17.x) / RDS for PostgreSQL (9.4, 10–17)
Schema synchronization, full data synchronization, incremental data synchronization
One-way, two-way
Two-way synchronization between PostgreSQL databases / One-way synchronization between RDS for PostgreSQL instances / Synchronize data from a self-managed PostgreSQL database to an RDS for PostgreSQL instance
Self-managed PostgreSQL (9.5.x–17.x) / RDS for PostgreSQL (9.4, 10–17)
PolarDB for PostgreSQL (versions 11, 14, 15, 16, 17)
Schema synchronization, full data synchronization, incremental data synchronization
One-way, two-way
Synchronize data from RDS for PostgreSQL to PolarDB for PostgreSQL / Two-way synchronization between RDS for PostgreSQL and PolarDB for PostgreSQL
Self-managed PostgreSQL (9.5.x–17.x) / RDS for PostgreSQL (9.4, 10–17)
AnalyticDB for PostgreSQL (4.3, 6.0, 7.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from RDS for PostgreSQL to AnalyticDB for PostgreSQL
Self-managed PostgreSQL (9.5.x–17.x) / RDS for PostgreSQL (9.4, 10–17)
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Self-managed PostgreSQL (9.5.x–17.x) / RDS for PostgreSQL (9.4, 10–17)
PolarDB for PostgreSQL (Compatible with Oracle) (all versions)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Self-managed PostgreSQL (9.5.x–17.x) / RDS for PostgreSQL (9.4, 10–17)
ApsaraDB for SelectDB
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from RDS for PostgreSQL to ApsaraDB for SelectDB
Synchronization solutions for a self-managed SQL Server database or an RDS for SQL Server instance
ImportantSupported editions for self-managed SQL Server (both source and destination): Enterprise, Developer, Enterprise Evaluation, Standard, and Web.
SQL Server clusters and SQL Server Always On availability groups are supported.
If the source database is Azure SQL Database, set SQL Server Incremental Synchronization Mode to Polling and querying CDC instances for incremental synchronization.
Self-managed SQL Server 2005 and RDS for SQL Server 2008 and 2008 R2 are not supported as a source.
Hybrid log parsing mode (Log-based Parsing for Non-heap Tables and CDC-based Incremental Synchronization for Heap Tables (Hybrid Log-based Parsing)) supports:
Enterprise or Enterprise Evaluation Edition: versions 2012, 2014, 2016, 2019, or 2022.
Standard Edition: versions 2016, 2019, or 2022.
Web Edition sources support only Incremental Synchronization Based on Logs of Source Database (Heap tables are not supported).
Source database
Destination database
Synchronization type
Topology
Configuration guide
Self-managed SQL Server (2008 R2, 2012, 2014, 2016, 2017, 2019, 2022) / RDS for SQL Server (2012, 2014, 2016, 2017, 2019, 2022)
Self-managed SQL Server (2008 R2, 2012, 2014, 2016, 2017, 2019, 2022) / RDS for SQL Server (2008 R2, 2012, 2014, 2016, 2017, 2019, 2022)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Self-managed SQL Server (2008 R2, 2012, 2014, 2016, 2017, 2019, 2022) / RDS for SQL Server (2012, 2014, 2016, 2017, 2019, 2022)
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Self-managed SQL Server (2008 R2, 2012, 2014, 2016, 2017, 2019, 2022) / RDS for SQL Server (2012, 2014, 2016, 2017, 2019, 2022)
PolarDB for MySQL (all versions)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from a self-managed SQL Server database to PolarDB for MySQL
Self-managed SQL Server (2008 R2, 2012, 2014, 2016, 2017, 2019, 2022) / RDS for SQL Server (2012, 2014, 2016, 2017, 2019, 2022)
AnalyticDB for MySQL (version 3.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from RDS for SQL Server to AnalyticDB for MySQL 3.0
Self-managed SQL Server (2008 R2, 2012, 2014, 2016, 2017, 2019, 2022) / RDS for SQL Server (2012, 2014, 2016, 2017, 2019, 2022)
AnalyticDB for PostgreSQL (4.3, 6.0, 7.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from a self-managed SQL Server database to AnalyticDB for PostgreSQL / Synchronize data from RDS for SQL Server to AnalyticDB for PostgreSQL
Self-managed SQL Server (2008 R2, 2012, 2014, 2016, 2017, 2019, 2022) / RDS for SQL Server (2012, 2014, 2016, 2017, 2019, 2022)
RDS for PostgreSQL (9.4, 10–17)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from a self-managed SQL Server database to RDS for PostgreSQL
Self-managed SQL Server (2008 R2, 2012, 2014, 2016, 2017, 2019, 2022) / RDS for SQL Server (2012, 2014, 2016, 2017, 2019, 2022)
DataHub
Schema synchronization, incremental data synchronization
One-way
Synchronization solution for a MariaDB source
Source database
Destination database
Synchronization type
Topology
Configuration guide
RDS for MariaDB (10.x) / Self-managed MariaDB (10.x, 11.0–11.4)
RDS for MariaDB / Self-managed MariaDB
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data between RDS for MariaDB instances / Synchronize data from a self-managed MariaDB database to an RDS for MariaDB instance
RDS for MariaDB (10.x) / Self-managed MariaDB (10.x, 11.0–11.4)
RDS for MySQL
Schema synchronization, full data synchronization, incremental data synchronization
One-way
RDS for MariaDB (10.x) / Self-managed MariaDB (10.x, 11.0–11.4)
RDS for PostgreSQL (9.4, 10–17)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronization scenarios for self-managed MongoDB or ApsaraDB for MongoDB
Source database
Destination database
Synchronization type
Topology
Configuration guide
Self-managed MongoDB (3.0–7.0) / ApsaraDB for MongoDB (3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0) — replica set architecture
Self-managed MongoDB (3.0–7.0) / ApsaraDB for MongoDB (3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0) — replica set or sharded cluster architecture
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Self-managed MongoDB (3.0–7.0) / ApsaraDB for MongoDB (3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0) — sharded cluster architecture
Self-managed MongoDB (3.0–7.0) / ApsaraDB for MongoDB (3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0) — replica set or sharded cluster architecture
Schema synchronization, full data synchronization, incremental data synchronization
One-way
ApsaraDB for MongoDB sharded cluster (4.0, 4.2, 4.4, 5.0, 6.0, 7.0)
ApsaraDB for MongoDB sharded cluster (4.0, 4.2, 4.4, 5.0, 6.0, 7.0)
Schema synchronization, full data synchronization, incremental data synchronization
Two-way
Two-way synchronization between ApsaraDB for MongoDB sharded cluster instances
ApsaraDB for MongoDB replica set (4.0, 4.2, 4.4, 5.0, 6.0, 7.0)
ApsaraDB for MongoDB replica set (4.0, 4.2, 4.4, 5.0, 6.0, 7.0)
Schema synchronization, full data synchronization, incremental data synchronization
Two-way
Two-way synchronization between ApsaraDB for MongoDB replica set instances
Self-managed MongoDB (3.0–7.0) / ApsaraDB for MongoDB (3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0) — replica set or sharded cluster
Function Compute (FC) version 2.0
Incremental data synchronization
One-way
Synchronize data from an ApsaraDB for MongoDB replica set instance to Function Compute (FC) / Synchronize data from an ApsaraDB for MongoDB sharded cluster instance to Function Compute (FC)
Self-managed MongoDB (3.0–7.0) / ApsaraDB for MongoDB (3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0)
Lindorm
Full data synchronization, incremental data synchronization
One-way
Self-managed MongoDB (3.0–7.0) / ApsaraDB for MongoDB (3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0)
AnalyticDB for PostgreSQL (4.3, 6.0, 7.0)
Full data synchronization, incremental data synchronization
One-way
Synchronize data from ApsaraDB for MongoDB to AnalyticDB for PostgreSQL
Self-managed MongoDB (3.0–7.0) / ApsaraDB for MongoDB (3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0)
AnalyticDB for MySQL 3.0
Full data synchronization, incremental data synchronization
One-way
Synchronize data from ApsaraDB for MongoDB to AnalyticDB for MySQL 3.0
Self-managed MongoDB (3.0–7.0) / ApsaraDB for MongoDB (3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0)
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
Full data synchronization, incremental data synchronization
One-way
Self-managed MongoDB (3.0–7.0) / ApsaraDB for MongoDB (3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0)
PolarDB for MySQL (all versions)
Full data synchronization, incremental data synchronization
One-way
Synchronize data from ApsaraDB for MongoDB to PolarDB for MySQL
Self-managed MongoDB (3.0–7.0) / ApsaraDB for MongoDB (3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0)
Alibaba Cloud Message Queue for Kafka (0.10.1.0–2.x) / Self-managed Kafka (0.10.1.0–2.7.0)
Full data synchronization, incremental data synchronization
One-way
Synchronize data from ApsaraDB for MongoDB to Alibaba Cloud Message Queue for Kafka
Synchronization from a self-managed Redis database or a Tair (Redis-compatible) instance
ImportantRedis is a NoSQL database and does not require schema synchronization.
Only two-way synchronization between Tair (Enterprise Edition) instances is supported.
When the source is a self-managed Redis instance or an ApsaraDB for Tair (compatible with Redis) instance, full and incremental data synchronization are combined into a single step called Incremental Data Synchronization.
The highest supported RDB version is 11, which corresponds to Redis 7.2.
Source database
Destination database
Synchronization type
Topology
Configuration guide
Self-managed Redis standalone or cluster (2.8, 3.0, 3.2, 4.0, 5.0, 6.0, 7.0, 7.2) / ApsaraDB for Tair (compatible with Redis) cluster/standard/read-write splitting (4.0, 5.0, 6.0, 7.0)
Self-managed Redis standalone or cluster (2.8, 3.0, 3.2, 4.0, 5.0, 6.0, 7.0, 7.2) / ApsaraDB for Tair (compatible with Redis) cluster/standard/read-write splitting (4.0, 5.0, 6.0, 7.0)
Full data synchronization, incremental data synchronization
One-way
One-way synchronization between ApsaraDB for Tair (compatible with Redis) instances / Cross-account one-way synchronization / Synchronize data from a self-managed Redis instance on an ECS instance to an ApsaraDB for Tair (compatible with Redis) instance
Alibaba Cloud Message Queue for Kafka (0.10.1.0–2.x) / Self-managed Kafka (0.10.1.0–2.7.0)
Full data synchronization
Incremental data synchronization
One-way synchronization
ApsaraDB for Tair (compatible with Redis) Enterprise Edition/Tair cluster/standard/read-write splitting
ApsaraDB for Tair (compatible with Redis) Enterprise Edition/Tair cluster/standard/read-write splitting
Full data synchronization, incremental data synchronization
Two-way
Two-way synchronization between Tair (Enterprise Edition) instances / Use an OpenAPI to configure one-way or two-way data synchronization between Tair (Enterprise Edition) instances
Data synchronization from a TiDB database
Source database
Destination database
Synchronization type
Topology
Configuration guide
TiDB
AnalyticDB for MySQL (version 3.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from a self-managed TiDB database to AnalyticDB for MySQL 3.0
TiDB
PolarDB-X 2.0
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Document in preparation
Synchronize data from a Db2 for LUW database
ImportantDb2 for LUW is displayed as DB2 for LUW in the console.
The destination PolarDB-X 2.0 instance must be version 5.4.11 or later. For upgrade instructions, see View and upgrade the instance version.
Source database
Destination database
Synchronization type
Topology
Configuration guide
Db2 for LUW (9.5, 9.7, 10.1, 10.5, 11.1, 11.5)
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Db2 for LUW (9.5, 9.7, 10.1, 10.5, 11.1, 11.5)
PolarDB for MySQL (all versions)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Db2 for LUW (9.5, 9.7, 10.1, 10.5, 11.1, 11.5)
PolarDB-X 2.0
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Db2 for LUW (9.5, 9.7, 10.1, 10.5, 11.1, 11.5)
AnalyticDB for PostgreSQL (4.3, 6.0, 7.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from Db2 for LUW to AnalyticDB for PostgreSQL
Db2 for LUW (9.5, 9.7, 10.1, 10.5, 11.1, 11.5)
Alibaba Cloud Message Queue for Kafka (0.10.1.0–2.x) / Self-managed Kafka (0.10.1.0–2.7.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from Db2 for LUW to a self-managed Kafka cluster
Synchronize data from a Db2 for i (AS/400) database
ImportantDb2 for i is displayed as DB2 for iSeries (AS/400) in the console.
Source database
Destination database
Synchronization type
Topology
Configuration guide
Db2 for i (versions 7.3, 7.4)
Self-managed MySQL (5.1, 5.5, 5.6, 5.7, 8.0, 8.4) / RDS for MySQL (all versions)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Document in preparation
Db2 for i (versions 7.3, 7.4)
PolarDB for MySQL (all versions)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Document in preparation
Data synchronization from an AnalyticDB for MySQL 3.0 source
ImportantThe kernel version of the source AnalyticDB for MySQL 3.0 cluster must be 3.2.1.0 or later.
Source database
Destination database
Synchronization type
Topology
Configuration guide
AnalyticDB for MySQL (version 3.0)
AnalyticDB for MySQL (version 3.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronization with an AnalyticDB for PostgreSQL source
ImportantThe kernel version of the source AnalyticDB for PostgreSQL instance must be 7.2.1.4 or later.
Source database
Destination database
Synchronization type
Topology
Configuration guide
AnalyticDB for PostgreSQL (version 7.0)
AnalyticDB for PostgreSQL (version 7.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data between AnalyticDB for PostgreSQL instances
AnalyticDB for PostgreSQL (version 7.0)
Alibaba Cloud Message Queue for Kafka (0.10.1.0–2.x)
Full data synchronization, incremental data synchronization
One-way
Synchronize data from AnalyticDB for PostgreSQL to Alibaba Cloud Message Queue for Kafka
Synchronize data from a DMS logical database
ImportantThe DMS logical database must be created from multiple sharded PolarDB for MySQL instances.
Source database
Destination database
Synchronization type
Topology
Configuration guide
Data Management (DMS) logical database
AnalyticDB for MySQL (version 3.0)
Schema synchronization, full data synchronization, incremental data synchronization
One-way
Synchronize data from a Data Management (DMS) logical database to AnalyticDB for MySQL 3.0
Synchronize data from an AWS database
Source database
Destination database
Configuration guide
AWS platform database
Subject to what is available in the console
Use a VPN gateway to synchronize data between an Alibaba Cloud RDS instance and an AWS EC2 instance
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.
Migration solutions for a self-managed MySQL database or an RDS for MySQL instance
Important-
Databases in PolarDB-X 1.0 must use RDS for MySQL. DTS does not support PolarDB-X 1.0 databases that use PolarDB for MySQL.
-
Schema migration is not supported when the destination is PolarDB-X 1.0. It is supported when the destination is PolarDB-X 2.0.
-
Use PolarDB-X 2.0 instance version 5.4.11 or later. See View and upgrade the instance version.
-
Migration solutions that use AnalyticDB for MySQL 2.0 as the destination are not available in the new console. Configure these solutions in the Legacy Console.
Source database Destination database Migration types Configuration guide Self-managed MySQL (versions 5.1, 5.5, 5.6, 5.7, 8.0, 8.4) or RDS for MySQL (all versions) Self-managed MySQL (versions 5.1, 5.5, 5.6, 5.7, 8.0, 8.4) or RDS for MySQL (all versions) Schema migration, full data migration, and incremental data migration Migrate data from a self-managed MySQL database to an RDS for MySQL instance or Migrate data between RDS for MySQL instances PolarDB for MySQL (all versions) Schema migration, full data migration, and incremental data migration Migrate data from a self-managed MySQL database to a PolarDB for MySQL cluster or Migrate data from an RDS for MySQL instance to a PolarDB for MySQL cluster PolarDB-X 1.0 Full data migration and incremental data migration Migrate data from an RDS for MySQL instance to a PolarDB-X 1.0 instance PolarDB-X 2.0 Schema migration, full data migration, and incremental data migration Migrate data from an RDS for MySQL instance to a PolarDB-X 2.0 instance AnalyticDB for MySQL (versions 2.0 and 3.0) Schema migration, full data migration, and incremental data migration Migrate data from an RDS for MySQL instance to an AnalyticDB for MySQL 3.0 cluster AnalyticDB for PostgreSQL (versions 4.3, 6.0, and 7.0) Schema migration, full data migration, and incremental data migration Migrate data from an RDS for MySQL instance to an AnalyticDB for PostgreSQL instance Self-managed PostgreSQL (versions 9.4.8 and later, 9.5, 9.6, 10.x–17.x) or RDS for PostgreSQL (versions 9.4, 10–17) Schema migration, full data migration, and incremental data migration Migrate data from an RDS for MySQL instance to an RDS for PostgreSQL instance ApsaraMQ for Kafka (versions 0.10.1.0 to 2.x) or self-managed Kafka (versions 0.10.1.0 to 2.7.0) Schema migration, full data migration, and incremental data migration Migrate data from an RDS for MySQL instance to an ApsaraMQ for Kafka instance ApsaraDB for ClickHouse cluster (version 20.8 and later) Schema migration, full data migration, and incremental data migration Migrate data from an RDS for MySQL instance to an ApsaraDB for ClickHouse cluster DataHub (all versions) Schema migration, full data migration, and incremental data migration Migrate data from an RDS for MySQL instance to DataHub Elasticsearch (versions 5.5, 5.6, 6.x, 7.x, and 8.x) Schema migration, full data migration, and incremental data migration Migrate data from an RDS for MySQL instance to an Elasticsearch cluster MaxCompute Schema migration, full data migration, and incremental data migration Migrate data from an RDS for MySQL instance to MaxCompute Self-managed Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, and 19c) Schema migration, full data migration, and incremental data migration Migrate data from an RDS for MySQL instance to a self-managed Oracle database Tair instance (cluster, standard, or read/write splitting architecture, versions 4.0, 5.0, 6.0, and 7.0) Full data migration and incremental data migration Migrate data from an RDS for MySQL instance to a Tair or Redis instance Tablestore Schema migration, full data migration, and incremental data migration Migrate data from an RDS for MySQL instance to Tablestore ApsaraDB for SelectDB Schema migration, full data migration, and incremental data migration Migrate data from an RDS for MySQL instance to an ApsaraDB for SelectDB instance Lindorm Full data migration and incremental data migration Migrate data from an RDS for MySQL instance to Lindorm Doris (version 1.2 and later) Schema migration, full data migration, and incremental data migration Migrate data from an RDS for MySQL instance to a self-managed Doris database ApsaraMQ for RocketMQ (4.x and 5.x series) Full data migration and incremental data migration Migrate data from an RDS for MySQL instance to an ApsaraMQ for RocketMQ instance -
Migration solutions for a MariaDB database
Source database Destination database Migration types Configuration guide RDS for MariaDB (10.x) or self-managed MariaDB (10.x, 11.0 to 11.4) RDS for MariaDB or self-managed MariaDB Schema migration, full data migration, and incremental data migration Migrate data between RDS for MariaDB instances or Migrate data from a self-managed MariaDB database to an RDS for MariaDB instance RDS for MySQL Schema migration, full data migration, and incremental data migration Migrate data from an RDS for MariaDB instance to an RDS for MySQL instance RDS for PostgreSQL (versions 9.4, 10–17) Schema migration, full data migration, and incremental data migration Migrate data from an RDS for MariaDB instance to an RDS for PostgreSQL instance Migration solutions for an RDS for PPAS instance
Source database Destination database Migration types Configuration guide RDS PPAS (all versions) PolarDB for PostgreSQL (Compatible with Oracle) (all versions) Schema migration, full data migration, and incremental data migration Migrate data from an RDS PPAS instance to a PolarDB for PostgreSQL (Compatible with Oracle) cluster Migration solutions for a PolarDB for MySQL cluster
Important-
Databases in PolarDB-X 1.0 must use RDS for MySQL. DTS does not support PolarDB-X 1.0 databases that use PolarDB for MySQL.
-
Schema migration is not supported when the destination is PolarDB-X 1.0. It is supported when the destination is PolarDB-X 2.0.
-
Use PolarDB-X 2.0 instance version 5.4.11 or later. See View and upgrade the instance version.
Source database Destination database Migration types Configuration guide PolarDB for MySQL (all versions) PolarDB for MySQL (all versions) Schema migration, full data migration, and incremental data migration Migrate data between PolarDB for MySQL clusters Self-managed MySQL (versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4) or RDS for MySQL (all versions) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB for MySQL cluster to an RDS for MySQL instance PolarDB-X 1.0 Full data migration and incremental data migration Migrate data from a PolarDB for MySQL cluster to a PolarDB-X 1.0 instance PolarDB-X 2.0 Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB for MySQL cluster to a PolarDB-X 2.0 instance AnalyticDB for MySQL (version 3.0) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB for MySQL cluster to an AnalyticDB for MySQL 3.0 cluster AnalyticDB for PostgreSQL (versions 4.3, 6.0, and 7.0) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB for MySQL cluster to an AnalyticDB for PostgreSQL instance ApsaraMQ for Kafka (versions 0.10.1.0 to 2.x) or self-managed Kafka (versions 0.10.1.0 to 2.7.0) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB for MySQL cluster to Kafka DataHub (all versions) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB for MySQL cluster to DataHub ApsaraDB for ClickHouse cluster (version 20.8 and later) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB for MySQL cluster to an ApsaraDB for ClickHouse cluster Self-managed Oracle (RAC, PDB, or non-RAC, versions 9i, 10g, 11g, 12c, 18c, and 19c) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB for MySQL cluster to a self-managed Oracle database Elasticsearch (versions 5.5, 5.6, 6.x, 7.x, and 8.x) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB for MySQL cluster to an Elasticsearch cluster MaxCompute Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB for MySQL cluster to MaxCompute ApsaraDB for SelectDB Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB for MySQL cluster to an ApsaraDB for SelectDB instance Doris (version 1.2 and later) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB for MySQL cluster to a self-managed Doris database Lindorm Full data migration and incremental data migration Migrate data from a PolarDB for MySQL cluster to Lindorm -
Migration solutions for a PolarDB for PostgreSQL (Compatible with Oracle) cluster
Source database Destination database Migration types Configuration guide PolarDB for PostgreSQL (Compatible with Oracle) (all versions) PolarDB for PostgreSQL (Compatible with Oracle) (all versions) Schema migration, full data migration, and incremental data migration Migrate data between PolarDB for PostgreSQL (Compatible with Oracle) clusters Self-managed Oracle (RAC, PDB, or non-RAC, versions 9i, 10g, 11g, 12c, 18c, and 19c) Full data migration and incremental data migration Migrate data from a PolarDB for PostgreSQL (Compatible with Oracle) cluster to a self-managed Oracle database ApsaraMQ for Kafka (versions 0.10.1.0 to 2.x) or self-managed Kafka (versions 0.10.1.0 to 2.7.0) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB for PostgreSQL (Compatible with Oracle) cluster to an ApsaraMQ for Kafka instance AnalyticDB for MySQL (version 3.0) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB for PostgreSQL (Compatible with Oracle) cluster to an AnalyticDB for MySQL 3.0 cluster Migration solutions for a PolarDB-X instance
Important-
Configure these tasks only in the new console.
-
Databases in PolarDB-X 1.0 must use RDS for MySQL. DTS does not support PolarDB-X 1.0 databases that use PolarDB for MySQL.
-
Use PolarDB-X 2.0 instance version 5.4.11 or later. See View and upgrade the instance version.
Source database Destination database Migration types Configuration guide PolarDB-X 1.0 PolarDB-X 2.0 Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB-X 1.0 instance to a PolarDB-X 2.0 instance AnalyticDB for MySQL (version 3.0) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB-X 1.0 instance to an AnalyticDB for MySQL 3.0 cluster AnalyticDB for PostgreSQL (versions 4.3, 6.0, and 7.0) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB-X 1.0 instance to an AnalyticDB for PostgreSQL instance DataHub Schema migration and incremental data migration Migrate data from a PolarDB-X 1.0 instance to DataHub Elasticsearch (versions 5.5, 5.6, 6.x, 7.x, and 8.x) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB-X 1.0 instance to an Elasticsearch cluster ApsaraMQ for Kafka (versions 0.10.1.0 to 2.x) or self-managed Kafka (versions 0.10.1.0 to 2.7.0) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB-X 1.0 instance to ApsaraMQ for Kafka Self-managed MySQL (versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4) or RDS for MySQL (all versions) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB-X 1.0 instance to an RDS for MySQL instance PolarDB-X 2.0 PolarDB-X 2.0 Schema migration, full data migration, and incremental data migration Migrate data between PolarDB-X 2.0 instances Self-managed MySQL (versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4) or RDS for MySQL (all versions) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB-X 2.0 instance to an RDS for MySQL instance PolarDB for MySQL (all versions) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB-X 2.0 instance to a PolarDB for MySQL cluster AnalyticDB for MySQL (version 3.0) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB-X 2.0 instance to an AnalyticDB for MySQL 3.0 cluster AnalyticDB for PostgreSQL (versions 4.3, 6.0, and 7.0) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB-X 2.0 instance to an AnalyticDB for PostgreSQL instance MaxCompute Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB-X 2.0 instance to MaxCompute ApsaraMQ for Kafka (versions 0.10.1.0 to 2.x) or self-managed Kafka (versions 0.10.1.0 to 2.7.0) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB-X 2.0 instance to ApsaraMQ for Kafka DataHub (all versions) Schema migration and incremental data migration Migrate data from a PolarDB-X 2.0 instance to DataHub Elasticsearch (versions 5.5, 5.6, 6.x, 7.x, and 8.x) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB-X 2.0 instance to an Elasticsearch cluster Self-managed Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, and 19c) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB-X 2.0 instance to a self-managed Oracle database Tablestore Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB-X 2.0 instance to Tablestore PolarDB-X 1.0 Full data migration and incremental data migration Migrate data from a PolarDB-X 2.0 instance to a PolarDB-X 1.0 instance ApsaraDB for SelectDB Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB-X 2.0 instance to an ApsaraDB for SelectDB instance -
Migration solutions for a PolarDB for PostgreSQL cluster
Source database Destination database Migration types Configuration guide PolarDB for PostgreSQL (versions 11, 14, 15, 16, and 17) PolarDB for PostgreSQL (versions 11, 14, 15, 16, and 17) Schema migration, full data migration, and incremental data migration Migrate data between PolarDB for PostgreSQL clusters Self-managed PostgreSQL (versions 9.5.x, 9.6.x, 10.x–17.x) or RDS for PostgreSQL (versions 9.4, 10–17) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB for PostgreSQL cluster to an RDS for PostgreSQL instance Self-managed Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, and 19c) Full data migration and incremental data migration Migrate data from a PolarDB for PostgreSQL cluster to a self-managed Oracle database AnalyticDB for PostgreSQL (versions 4.3, 6.0, and 7.0) Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB for PostgreSQL cluster to an AnalyticDB for PostgreSQL instance ApsaraDB for SelectDB Schema migration, full data migration, and incremental data migration Migrate data from a PolarDB for PostgreSQL cluster to an ApsaraDB for SelectDB instance Migration solutions for a MaxCompute project
Source database Destination database Migration types Configuration guide MaxCompute (all versions) Self-managed MySQL (versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4) or RDS for MySQL (all versions) Schema migration and full data migration Migrate data from MaxCompute to an RDS for MySQL instance Migration solutions for an OceanBase (MySQL) instance
Source database Destination database Migration types Configuration guide ApsaraDB for OceanBase (cluster and tenant instances, MySQL mode) or OceanBase (MySQL) Community Edition Self-managed MySQL (versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4) or RDS for MySQL (all versions) Schema migration, full data migration, and incremental data migration Migrate data from an OceanBase database (MySQL mode) to an RDS for MySQL instance PolarDB for MySQL (all versions) Schema migration, full data migration, and incremental data migration Migrate data from an OceanBase database (MySQL mode) to a PolarDB for MySQL cluster Lindorm Full data migration and incremental data migration Migrate data from an OceanBase database (MySQL mode) to Lindorm HUAWEI CLOUD Document Database Service (DDS)
ApsaraDB for MongoDB
Full data migration
Incremental data migration
Use DTS to migrate data from HUAWEI CLOUD DDS to Alibaba Cloud
TencentDB for MySQL
RDS for MySQL
Schema migration
Full data migration
Incremental data migration
TencentDB for MongoDB
ApsaraDB for MongoDB
Incremental data migration
Full data migration
Migration solutions for an Oracle database
Important-
Databases in PolarDB-X 1.0 must use RDS for MySQL. DTS does not support PolarDB-X 1.0 databases that use PolarDB for MySQL.
-
Schema migration is not supported when the destination is PolarDB-X 1.0. It is supported when the destination is PolarDB-X 2.0.
-
Use PolarDB-X 2.0 instance version 5.4.11 or later. See View and upgrade the instance version.
Source database Destination database Migration types Configuration guide Self-managed Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, and 19c) PolarDB for PostgreSQL (Compatible with Oracle) (all versions) Schema migration, full data migration, and incremental data migration Migrate data from a self-managed Oracle database to a PolarDB for PostgreSQL (Compatible with Oracle) cluster or Migrate data from Amazon RDS for Oracle to a PolarDB for PostgreSQL (Compatible with Oracle) cluster Self-managed Oracle (RAC or non-RAC, versions 9i, 10g, 11g, 12c, 18c, and 19c) Schema migration, full data migration, and incremental data migration Migrate data between self-managed Oracle databases Self-managed MySQL (versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4) or RDS for MySQL (all versions) Schema migration, full data migration, and incremental data migration Migrate data from a self-managed Oracle database to an RDS for MySQL instance PolarDB for MySQL (all versions) Schema migration, full data migration, and incremental data migration Migrate data from a self-managed Oracle database to a PolarDB for MySQL cluster PolarDB for PostgreSQL (versions 11, 14, 15, 16, and 17) Schema migration, full data migration, and incremental data migration Migrate data from a self-managed Oracle database to a PolarDB for PostgreSQL cluster PolarDB-X 1.0 and 2.0 Full data migration and incremental data migration Migrate data from a self-managed Oracle database to a PolarDB-X 2.0 instance AnalyticDB for MySQL (version 3.0) Schema migration, full data migration, and incremental data migration Migrate data from a self-managed Oracle database to an AnalyticDB for MySQL 3.0 cluster AnalyticDB for PostgreSQL (versions 4.3, 6.0, and 7.0) Schema migration, full data migration, and incremental data migration Migrate data from a self-managed Oracle database to an AnalyticDB for PostgreSQL instance Self-managed PostgreSQL (versions 9.4.8 and later, 9.5, 9.6, 10.x–17.x) or RDS for PostgreSQL (versions 9.4, 10–17) Schema migration, full data migration, and incremental data migration Migrate data from a self-managed Oracle database to a self-managed PostgreSQL database or Migrate data from a self-managed Oracle database to an RDS for PostgreSQL instance ApsaraMQ for Kafka (versions 0.10.1.0 to 2.x) or self-managed Kafka (versions 0.10.1.0 to 2.7.0) Schema migration, full data migration, and incremental data migration Migrate data from a self-managed Oracle database to an ApsaraMQ for Kafka instance DataHub (all versions) Schema migration, full data migration, and incremental data migration Migrate data from a self-managed Oracle database to DataHub -
Migration solutions for a self-managed PostgreSQL database or an RDS for PostgreSQL instance
ImportantRDS for PostgreSQL serverless instances are not supported as a source database, but are supported as a destination database.
Source database Destination database Migration types Configuration guide Self-managed PostgreSQL (versions 9.4.8 and later, 9.5, 9.6, 10.x–17.x) or RDS for PostgreSQL (versions 9.4, 10–17) Self-managed PostgreSQL (versions 9.4.8 and later, 9.5, 9.6, 10.x–17.x) or RDS for PostgreSQL (versions 9.4, 10–17) Schema migration, full data migration, and incremental data migration Migrate data between RDS for PostgreSQL instances or Migrate data from a self-managed PostgreSQL database to an RDS for PostgreSQL instance PolarDB for PostgreSQL (versions 11, 14, 15, 16, and 17) Schema migration, full data migration, and incremental data migration Migrate data from a self-managed PostgreSQL database to a PolarDB for PostgreSQL cluster Self-managed MySQL (versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4) or RDS for MySQL (all versions) Schema migration, full data migration, and incremental data migration Migrate data from an RDS for PostgreSQL instance to an RDS for MySQL instance PolarDB for PostgreSQL (Compatible with Oracle) (all versions) Schema migration, full data migration, and incremental data migration Migrate data from a self-managed PostgreSQL database to a PolarDB for PostgreSQL (Compatible with Oracle) cluster AnalyticDB for PostgreSQL (versions 4.3, 6.0, and 7.0) Schema migration, full data migration, and incremental data migration Migrate data from a self-managed PostgreSQL database to an AnalyticDB for PostgreSQL instance ApsaraDB for SelectDB Schema migration, full data migration, and incremental data migration Migrate data from an RDS for PostgreSQL instance to an ApsaraDB for SelectDB instance Migration solutions for a self-managed SQL Server database or an RDS for SQL Server instance
Important-
The source self-managed SQL Server must be Enterprise, Developer, Enterprise Evaluation, Standard, or Web Edition. The same applies to the destination.
-
If the source self-managed SQL Server is version 2005, or the source RDS for SQL Server is version 2008 or 2008 R2, incremental data migration is not supported.
-
If Azure SQL Database is the source, set SQL Server Incremental Synchronization Mode to Polling and querying CDC instances for incremental synchronization.
-
SQL Server Cluster and SQL Server AlwaysOn availability groups are supported.
-
In hybrid log parsing mode (where SQL Server Incremental Synchronization Mode is set to Incremental Synchronization Through Log Parsing For Non-heap Tables And Through CDC For Heap Tables), supported editions are:
-
Enterprise or Enterprise Evaluation: 2012, 2014, 2016, 2019, or 2022.
-
Standard: 2016, 2019, or 2022.
-
If the source is Web Edition SQL Server, the SQL Server Incremental Synchronization Mode is limited to Incremental Synchronization Based on Logs of Source Database (Heap tables are not supported).
Source database Destination database Migration types Configuration guide Self-managed SQL Server (2005, 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019, or 2022) or RDS for SQL Server (2008, 2008 R2, 2012, 2014, 2016, 2017, 2019, or 2022) Self-managed SQL Server (2005, 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019, or 2022) or RDS for SQL Server (2008, 2008 R2, 2012, 2014, 2016, 2017, 2019, or 2022) Schema migration, full data migration, and incremental data migration Migrate data between RDS for SQL Server instances, Migrate data from a self-managed SQL Server database to an RDS for SQL Server instance, Migrate data from a self-managed SQL Server database to the cloud over a physical connection , Migrate data from SQL Server on Azure to an RDS for SQL Server instance, or Migrate data from SQL Server on AWS to an RDS for SQL Server instanceSelf-managed MySQL (versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4) or RDS for MySQL (all versions) Schema migration, full data migration, and incremental data migration Migrate data from an RDS for SQL Server instance to an RDS for MySQL instance PolarDB for MySQL (all versions) Schema migration, full data migration, and incremental data migration Migrate data from an RDS for SQL Server instance to a PolarDB for MySQL cluster AnalyticDB for MySQL (version 3.0) Schema migration, full data migration, and incremental data migration Migrate data from an RDS for SQL Server instance to an AnalyticDB for MySQL 3.0 cluster AnalyticDB for PostgreSQL (versions 4.3, 6.0, and 7.0) Schema migration, full data migration, and incremental data migration Migrate data from a self-managed SQL Server database to an AnalyticDB for PostgreSQL instance RDS for PostgreSQL (versions 9.4, 10–17) Schema migration, full data migration, and incremental data migration Migrate data from a self-managed SQL Server database to an RDS for PostgreSQL instance DataHub Schema migration and incremental data migration Migrate data from an RDS for SQL Server instance to DataHub -
Migration solutions for a self-managed MongoDB database or an ApsaraDB for MongoDB instance
Source database Destination database Migration types Configuration guide Single-node: self-managed MongoDB (versions 3.0 to 7.0) or ApsaraDB for MongoDB (versions 3.4 and 4.0) Single-node, replica set, or sharded cluster: self-managed MongoDB (versions 3.0 to 7.0) or ApsaraDB for MongoDB (versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, and 7.0) Schema migration and full data migration Perform full migration from an ApsaraDB for MongoDB single-node instance to an ApsaraDB for MongoDB instance of any architecture Replica set: self-managed MongoDB (versions 3.0 to 7.0) or ApsaraDB for MongoDB (versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, and 7.0) Replica set or sharded cluster: self-managed MongoDB (versions 3.0 to 7.0) or ApsaraDB for MongoDB (versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, and 7.0) Schema migration, full data migration, and incremental data migration Migrate data from an ApsaraDB for MongoDB replica set instance to an ApsaraDB for MongoDB replica set or sharded cluster instance Sharded cluster: self-managed MongoDB (versions 3.0 to 7.0) or ApsaraDB for MongoDB (versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, and 7.0) Replica set or sharded cluster: self-managed MongoDB (versions 3.0 to 7.0) or ApsaraDB for MongoDB (versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, and 7.0) Schema migration, full data migration, and incremental data migration Migrate data from a self-managed MongoDB sharded cluster instance to an ApsaraDB for MongoDB replica set or sharded cluster instance Replica set or sharded cluster: self-managed MongoDB (versions 3.0 to 7.0) or ApsaraDB for MongoDB (versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, and 7.0) Lindorm Full data migration and incremental data migration Migrate data from an ApsaraDB for MongoDB instance to Lindorm AnalyticDB for PostgreSQL (versions 4.3, 6.0, and 7.0) Full data migration and incremental data migration Migrate data from an ApsaraDB for MongoDB instance to an AnalyticDB for PostgreSQL instance AnalyticDB for MySQL 3.0 Full data migration and incremental data migration Migrate data from an ApsaraDB for MongoDB instance to an AnalyticDB for MySQL 3.0 cluster Self-managed MySQL (versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4) or RDS for MySQL (all versions) Full data migration and incremental data migration Migrate data from an ApsaraDB for MongoDB instance to an RDS for MySQL instance PolarDB for MySQL (all versions) Full data migration and incremental data migration Migrate data from an ApsaraDB for MongoDB instance to a PolarDB for MySQL cluster ApsaraMQ for Kafka (versions 0.10.1.0 to 2.x) or self-managed Kafka (versions 0.10.1.0 to 2.7.0) Full data migration and incremental data migration Synchronize data from an ApsaraDB for MongoDB instance to an ApsaraMQ for Kafka instance Migration solutions for a self-managed Redis database or an ApsaraDB for Tair (Redis-Compatible) instance
Important-
Redis is a NoSQL database. Schema migration is not required.
-
If the source is a self-managed Redis or Tair (Redis OSS-compatible) instance, both full and incremental data migration are supported and displayed together as Incremental Data Migration.
-
The highest supported RDB version is 11, which corresponds to Redis 7.2.
Source database Destination database Migration types Configuration guide Self-managed Redis (standalone or cluster, versions 2.8, 3.0, 3.2, 4.0, 5.0, 6.0, 7.0, and 7.2) or Tair instance (cluster, standard, or read/write splitting, versions 4.0, 5.0, 6.0, and 7.0) Self-managed Redis (standalone or cluster, versions 2.8, 3.0, 3.2, 4.0, 5.0, 6.0, 7.0, and 7.2) or Tair instance (cluster, standard, or read/write splitting, versions 4.0, 5.0, 6.0, and 7.0) Full data migration and incremental data migration Migrate data between Tair (compatible with Redis) instances, Cross-account migration, or Migrate data from a self-managed Redis database to a Tair (compatible with Redis) instance Full data migration
Incremental data migration
Migrate data from a Tair (compatible with Redis) instance to an ApsaraMQ for Kafka instance
-
Migration solutions for a TiDB database
Source database Destination database Migration types Configuration guide TiDB Self-managed MySQL (versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4) or RDS for MySQL (all versions) Schema migration, full data migration, and incremental data migration Migrate data from a self-managed TiDB database to an RDS for MySQL instance PolarDB for MySQL (all versions) Schema migration, full data migration, and incremental data migration Migrate data from a self-managed TiDB database to a PolarDB for MySQL cluster PolarDB-X 2.0 Schema migration, full data migration, and incremental data migration Documentation is being prepared. AnalyticDB for MySQL (version 3.0) Schema migration, full data migration, and incremental data migration Migrate data from a self-managed TiDB database to an AnalyticDB for MySQL 3.0 cluster Migration solutions for a Db2 for LUW database
Important-
Db2 for LUW appears as DB2 LUW in the console.
-
Use PolarDB-X 2.0 instance version 5.4.11 or later. See View and upgrade the instance version.
Source database Destination database Migration types Configuration guide Db2 for LUW (versions 9.5, 9.7, 10.1, 10.5, 11.1, and 11.5) Self-managed MySQL (versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4) or RDS for MySQL (all versions) Schema migration, full data migration, and incremental data migration Migrate data from a Db2 for LUW database to an RDS for MySQL instance PolarDB-X 2.0 Full data migration and incremental data migration Migrate data from a Db2 for LUW database to a PolarDB-X 2.0 instance AnalyticDB for PostgreSQL (versions 4.3, 6.0, and 7.0) Schema migration, full data migration, and incremental data migration Migrate data from a Db2 for LUW database to an AnalyticDB for PostgreSQL instance ApsaraMQ for Kafka (versions 0.10.1.0 to 2.x) or self-managed Kafka (versions 0.10.1.0 to 2.7.0) Schema migration, full data migration, and incremental data migration Migrate data from a Db2 for LUW database to an ApsaraMQ for Kafka instance PolarDB for MySQL (all versions) Schema migration, full data migration, and incremental data migration Migrate data from a Db2 for LUW database to a PolarDB for MySQL cluster -
Migration solutions for a Db2 for i database
ImportantDb2 for i appears as DB2 iSeries(AS/400) in the console.
Source database Destination database Migration types Configuration guide Db2 for i (versions 7.3 and 7.4) Self-managed MySQL (versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4) or RDS for MySQL (all versions) Schema migration, full data migration, and incremental data migration Documentation is being prepared. PolarDB for MySQL (all versions) Schema migration, full data migration, and incremental data migration Documentation is being prepared. Migration solutions for a Teradata database
ImportantConfigure these tasks only in the new console. The migration instances must be in the China (Shanghai), China (Qingdao), or China (Zhangjiakou) region.
Source database Destination database Migration types Configuration guide Teradata (version 17 and earlier) AnalyticDB for PostgreSQL (versions 4.3, 6.0, and 7.0) Schema migration and full data migration Migrate data from a Teradata database to an AnalyticDB for PostgreSQL instance Migration solutions for a self-managed HBase database
ImportantConfigure these tasks only in the new console.
Source database Destination database Migration types Configuration guide Self-managed HBase (1.x versions) AnalyticDB for MySQL (version 3.0) Schema migration and full data migration Migrate data from a self-managed HBase database to an AnalyticDB for MySQL 3.0 cluster Migration solutions for an AnalyticDB for MySQL 3.0 cluster
To migrate incremental data, the source AnalyticDB for MySQL 3.0 cluster must have a kernel version of 3.2.1.0 or later.
Source database Destination database Migration types Configuration guide AnalyticDB for MySQL (version 3.0) AnalyticDB for MySQL (version 3.0) Schema migration, full data migration, and incremental data migration Migrate data between AnalyticDB for MySQL 3.0 clusters Migration solutions for an AnalyticDB for PostgreSQL instance
To migrate incremental data, the source AnalyticDB for PostgreSQL instance must have a kernel version of 7.2.1.4 or later.
Source database Destination database Migration types Configuration guide AnalyticDB for PostgreSQL (version 7.0) AnalyticDB for PostgreSQL (version 7.0) Schema migration, full data migration, and incremental data migration Migrate data between AnalyticDB for PostgreSQL instances Migration solutions for a database hosted on a third-party cloud
DTS supports migrating data from third-party cloud platforms to Alibaba Cloud products.
Source database Destination database Migration types Configuration guide Databases on the Azure platform — — Connect an Azure VNet to an Alibaba Cloud VPC Amazon RDS for MySQL RDS for MySQL Schema migration, full data migration, and incremental data migration Migrate data from Amazon RDS for MySQL to ApsaraDB RDS for MySQL Amazon RDS for Oracle RDS for MySQL Schema migration, full data migration, and incremental data migration Migrate data from Amazon RDS for Oracle to ApsaraDB RDS for MySQL Amazon RDS for PostgreSQL RDS for PostgreSQL Schema migration, full data migration, and incremental data migration Incrementally migrate data from Amazon RDS for PostgreSQL to Alibaba Cloud Schema migration and full data migration Perform a full data migration from Amazon RDS for PostgreSQL to Alibaba Cloud Amazon RDS for SQL Server RDS for SQL Server Schema migration and full data migration Perform a full data migration from Amazon RDS for SQL Server to Alibaba Cloud Amazon Aurora MySQL RDS for MySQL Schema migration, full data migration, and incremental data migration Migrate data from Amazon Aurora MySQL to Alibaba Cloud PolarDB for MySQL Schema migration, full data migration, and incremental data migration Migrate data from Amazon Aurora MySQL to PolarDB for MySQL Amazon Aurora PostgreSQL RDS for PostgreSQL Schema migration and full data migration Migrate data from Amazon Aurora PostgreSQL to Alibaba Cloud MongoDB Atlas ApsaraDB for MongoDB Full data migration and incremental data migration Use DTS to migrate data from a MongoDB Atlas database to Alibaba Cloud
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 database | Supported versions | Supported change types | Configuration guide |
|---|---|---|---|
| ApsaraDB RDS for MySQL | All versions | Data updates, schema updates | Create a change tracking task for an ApsaraDB RDS for MySQL instance |
| PolarDB for MySQL | All versions | Data updates, schema updates | Create a change tracking task for a PolarDB for MySQL cluster |
| PolarDB-X 1.0 | — | Data updates, schema updates | Create a change tracking task for a PolarDB-X 1.0 instance |
| PolarDB-X 2.0 | — | Data updates, schema updates | Create a change tracking task for a PolarDB-X 2.0 instance |
| PolarDB for PostgreSQL (Compatible with Oracle) | All versions | Data updates only | Create a change tracking task for a PolarDB for PostgreSQL (Compatible with Oracle) cluster |
| ApsaraDB RDS for PostgreSQL | 9.4, 10, 11, 12, 13, 14, 15, 16, 17 | Data updates only | Create a change tracking task for an ApsaraDB RDS for PostgreSQL instance |
| PolarDB for PostgreSQL | 11, 14, 15, 16 | Data updates, schema updates | Create a change tracking task for a PolarDB for PostgreSQL cluster |
| Data Management (DMS) logical database | — | Data updates only | Create 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 database | Supported versions | Supported change types | Configuration guide |
|---|---|---|---|
| Self-managed MySQL | 5.1, 5.5, 5.6, 5.7, 8.0 | Data updates, schema updates | Create a change tracking task for an ApsaraDB RDS for MySQL instance |
| Self-managed Oracle (non-RAC) | 9i, 10g, 11g | Data updates, schema updates | Create a change tracking task for an Oracle database |
| Self-managed PostgreSQL | 9.4.8 and later, 9.5, 9.6, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x | Data updates only | Create a change tracking task for an ApsaraDB RDS for PostgreSQL instance |