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

Note For more information about terms such as the migration type, initial synchronization type, and subscribed data type, see Terms.

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. This section describes the database types, database versions, and migration types that are supported by data migration.

For more information about data migration in various scenarios, see Overview of data migration scenarios.

Note A user-created source or destination database can be one of the following types: User-Created Database with Public IP Address, User-Created Database in ECS Instance, and User-Created Database Connected Over Express Connect, VPN Gateway, or Smart Access Gateway.
Source database Destination database Migration type
  • User-created MySQL database

    5.1, 5.5, 5.6, 5.7, and 8.0

  • ApsaraDB RDS for MySQL

    All versions

User-created MySQL database

5.1, 5.5, 5.6, 5.7, and 8.0

  • Schema migration
  • Full data migration
  • Incremental data migration

ApsaraDB RDS for MySQL

All versions

  • Schema migration
  • Full data migration
  • Incremental data migration

Apsara PolarDB for MySQL

All versions

  • Schema migration
  • Full data migration
  • Incremental data migration

DRDS

All versions

Note The databases in DRDS instances are created based on ApsaraDB RDS for MySQL instances that you purchased. DTS does not support databases that are created based on private ApsaraDB RDS for MySQL instances or Apsara PolarDB for MySQL clusters.
  • Full data migration
  • Incremental data migration

HybridDB for MySQL (Previous name: PetaData)

All versions

  • Full data migration
  • Incremental data migration

AnalyticDB for MySQL

2.0 and 3.0

  • Schema migration
  • Full data migration
  • Incremental data migration

User-created PostgreSQL database

9.4, 9.5, 9.6, 10.x, 11.x, and 12

  • Full data migration
  • Incremental data migration

User-created Oracle database (RAC and non-RAC architecture)

9i, 10g, 11g, 12c, 18c, and 19c

  • Schema migration
  • Full data migration
  • Incremental data migration

ApsaraDB for MariaDB TX

10.3

ApsaraDB for MariaDB TX

10.3

  • Schema migration
  • Full data migration
  • Incremental data migration

ApsaraDB RDS for MySQL

All versions

  • Schema migration
  • Full data migration
  • Incremental data migration

User-created MySQL database

5.1, 5.5, 5.6, 5.7, and 8.0

  • Schema migration
  • Full data migration
  • Incremental data migration

Apsara PolarDB for MySQL

All versions

Apsara PolarDB for MySQL

All versions

  • Schema migration
  • Full data migration
  • Incremental data migration

User-created MySQL database

5.1, 5.5, 5.6, 5.7, and 8.0

  • Schema migration
  • Full data migration
  • Incremental data migration

ApsaraDB RDS for MySQL

All versions

  • Schema migration
  • Full data migration
  • Incremental data migration

AnalyticDB for MySQL

2.0 and 3.0

  • Schema migration
  • Full data migration
  • Incremental data migration
  • User-created SQL Server database

    2005, 2008, 2008 R2, 2012, 2014, 2016, and 2017

    Note
    • SQL Server Cluster and SQL Server AlwaysOn High Availability Group are not supported.
    • If the version of the source database is 2005, incremental data migration is not supported.
  • ApsaraDB RDS for SQL Server

    2008, 2008 R2, 2012, 2014, 2016, and 2017

    Note If the version of the source database is 2008 or 2008 R2, incremental data migration is not supported.

User-created SQL Server database

2005, 2008, 2008 R2, 2012, 2014, 2016, and 2017

Note SQL Server Cluster and SQL Server AlwaysOn High Availability Group are not supported.
  • Schema migration
  • Full data migration
  • Incremental data migration

ApsaraDB RDS for SQL Server

2008, 2008 R2, 2012, 2014, 2016, and 2017

  • Schema migration
  • Full data migration
  • Incremental data migration

User-created Oracle database (RAC and non-RAC architecture)

9i, 10g, 11g, 12c, 18c, and 19c

User-created Oracle database (RAC and non-RAC architecture)

9i, 10g, 11g, 12c, 18c, and 19c

  • Schema migration
  • Full data migration
  • Incremental data migration

PolarDB database compatible with Oracle

All versions

  • Schema migration
  • Full data migration
  • Incremental data migration

ApsaraDB RDS for PPAS

9.3 and 10

  • Schema migration
  • Full data migration
  • Incremental data migration

User-created MySQL database

5.1, 5.5, 5.6, 5.7, and 8.0

  • Schema migration
  • Full data migration
  • Incremental data migration

ApsaraDB RDS for MySQL

All versions

  • Schema migration
  • Full data migration
  • Incremental data migration

DRDS

All versions

Note The databases in DRDS instances are created based on ApsaraDB RDS for MySQL instances that you purchased. DTS does not support databases that are created based on private ApsaraDB RDS for MySQL instances or Apsara PolarDB for MySQL clusters.
  • Full data migration
  • Incremental data migration

AnalyticDB for MySQL

2.0 and 3.0

  • Schema migration
  • Full data migration
  • Incremental data migration

User-created PostgreSQL database

9.4, 9.5, 9.6, 10.x, 11.x, and 12

  • User-created PostgreSQL database

    9.4, 9.5, 9.6, 10.x, 11.x, and 12

  • ApsaraDB RDS for PostgreSQL

    9.4, 10, 11, and 12

  • Schema migration
  • Full data migration
  • Incremental data migration
  • User-created MongoDB database (single-node, replica set, and sharded cluster architecture)

    3.0, 3.2, 3.4, 3.6, and 4.0

  • ApsaraDB for MongoDB instance (single-node and replica set architecture)

    All versions

  • User-created MongoDB database (single-node, replica set, and sharded cluster architecture)

    3.0, 3.2, 3.4, 3.6, and 4.0

  • ApsaraDB for MongoDB instance (single-node, replica set, and sharded cluster architecture)

    All versions

  • Full data migration
  • Incremental data migration
Note MongoDB is a NoSQL database that does not require schema migration.

User-created Redis database (single-host architecture)

2.8, 3.0, 3.2, 4.0, and 5.0

User-created Redis database (single-host and cluster architecture)

2.8, 3.0, 3.2, 4.0, and 5.0

  • Full data migration
  • Incremental data migration
Note Redis is a NoSQL database that does not require schema migration.

ApsaraDB for Redis instance (single-host and cluster architecture)

Community versions 4.0 and 5.0

  • Full data migration
  • Incremental data migration

User-created Db2 database

9.7 and 10.5

User-created MySQL database

5.1, 5.5, 5.6, 5.7, and 8.0

  • Schema migration
  • Full data migration
  • Incremental data migration

Data synchronization

You can use DTS to synchronize data between data sources in real time. This feature applies to the following scenarios: active geo-redundancy, geo-disaster recovery, zone-disaster recovery, cross-border data synchronization, query load balancing, cloud BI systems, and real-time data warehousing. The following table lists the database types, initial synchronization types, and synchronization topologies that are supported by data synchronization.

For more information about data synchronization in various scenarios, see Overview of data synchronization scenarios.

Note A user-created source or destination database can be one of the following types: User-Created Database in ECS Instance and User-Created Database Connected Over Express Connect, VPN Gateway, or Smart Access Gateway.
Source database Destination database Initial synchronization type Synchronization topology
  • User-created MySQL database

    5.1, 5.5, 5.6, 5.7, and 8.0

  • ApsaraDB RDS for MySQL

    All versions

User-created MySQL database

5.1, 5.5, 5.6, 5.7, and 8.0

Initial schema synchronization

Initial full data synchronization

One-way synchronization

Two-way synchronization

ApsaraDB RDS for MySQL

All versions

Initial schema synchronization

Initial full data synchronization

One-way synchronization

Two-way synchronization

Apsara PolarDB for MySQL

All versions

Initial schema synchronization

Initial full data synchronization

One-way synchronization

Elasticsearch

5.5, 6.3, and 6.7

Initial schema synchronization

Initial full data synchronization

One-way synchronization

MaxCompute

All versions

Initial schema synchronization

Initial full data synchronization

One-way synchronization

AnalyticDB for MySQL

2.0 and 3.0

Initial schema synchronization

Initial full data synchronization

One-way synchronization

AnalyticDB for PostgreSQL

(Previous name: HybridDB for PostgreSQL)

4.3 and 6.0

Initial schema synchronization

Initial full data synchronization

One-way synchronization

Apsara PolarDB for MySQL

All versions

Apsara PolarDB for MySQL

All versions

Initial schema synchronization

Initial full data synchronization

One-way synchronization

ApsaraDB RDS for MySQL

All versions

Initial schema synchronization

Initial full data synchronization

One-way synchronization

User-created MySQL database

5.1, 5.5, 5.6, 5.7, and 8.0

Initial schema synchronization

Initial full data synchronization

One-way synchronization

AnalyticDB for MySQL

2.0 and 3.0

Initial schema synchronization

Initial full data synchronization

One-way synchronization
  • User-created Redis database (single-host and cluster architecture)

    2.8, 3.0, 3.2, 4.0, and 5.0

  • ApsaraDB for Redis instance (single-host and cluster architecture)

    Community versions 4.0 and 5.0

  • User-created Redis database (single-host and cluster architecture)

    2.8, 3.0, 3.2, 4.0, and 5.0

  • ApsaraDB for Redis instance (single-host and cluster architecture)

    Community versions 4.0 and 5.0

Initial full data synchronization

Note Redis is a NoSQL database that does not require initial schema synchronization.
One-way synchronization

Change tracking (previous)

You can use DTS to retrieve incremental data from ApsaraDB RDS for MySQL in real time. This feature applies to the following scenarios: cache updates, business decoupling, asynchronous data processing, real-time synchronization of heterogeneous data, and real-time synchronization of extract, transform, and load (ETL) operations. This feature will soon be unavailable. For more information, see [Notice] ApsaraDB RDS for MySQL users will no longer be able to use the previous change tracking feature after March 31, 2020.

Source database Data type

ApsaraDB RDS for MySQL

5.5, 5.6, and 5.7

  • Data update
  • Schema update

Change tracking (new)

You can use DTS to retrieve incremental data from user-created MySQL and ApsaraDB RDS for MySQL databases in real time. This feature applies to the following scenarios: cache updates, business decoupling, asynchronous data processing, real-time synchronization of heterogeneous data, and real-time synchronization of ETL operations.

Note
  • The previous change tracking feature requires high costs. To improve user experience and reduce costs, Alibaba Cloud has upgraded the change tracking feature to achieve repeated consumption of data across multiple downstream instances. For more information, see Change tracking (new).
  • A user-created source database, such as MySQL, can be one of the following types: User-Created Database with Public IP Address, User-Created Database in ECS Instance, and User-Created Database Connected Over Express Connect, VPN Gateway, or Smart Access Gateway.
Source database Data type

User-created MySQL database

5.1, 5.5, 5.6, 5.7, or 8.0

  • Data update
  • Schema update

ApsaraDB RDS for MySQL

All versions