You can use Data Transmission Service (DTS) to track data changes from databases in real time. Then, you can consume the tracked data and write data to a destination database. You can use the change tracking feature in the following scenarios: cache updates, business decoupling, synchronization of heterogeneous data, and synchronization of extract, transform, and load (ETL) operations.

Note The DTS console is upgraded. We recommend that you use the new DTS console because the configuration process is optimized and multiple change tracking scenarios are supported.

Change tracking (new)

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).

Note

A self-managed database can be one of the following types:

  • Self-managed database with a public IP address
  • Self-managed database that has no public IP address or port number (connected over Database Gateway)
  • Self-managed database that is connected over Cloud Enterprise Network (CEN)
  • Self-managed database that is hosted on Elastic Compute Service (ECS)
  • Self-managed database that is connected over Express Connect, VPN Gateway, or Smart Access Gateway
Source database Data change type References
  • Self-managed MySQL database

    Version 5.1, 5.5, 5.6, 5.7, or 8.0

  • ApsaraDB RDS for MySQL

    All versions

  • Data update
  • Schema update

New version of the DTS console: Track data changes from an ApsaraDB RDS for MySQL instance

PolarDB for MySQL

All versions

  • Data update
  • Schema update
New version of the DTS console: Track data changes from a PolarDB for MySQL cluster
PolarDB-X V1.0
Note A database in a PolarDB-X instance must be created based on one or more ApsaraDB RDS for MySQL instances. DTS does not support PolarDB-X databases that are created based on PolarDB for MySQL clusters.
  • Data update
  • Schema update
Note You can configure a change tracking task for this scenario only in the DTS console of the new version.
Track data changes from a DRDS instance
PolarDB-X V2.0
Note A database in a PolarDB-X instance must be created based on one or more ApsaraDB RDS for MySQL instances. DTS does not support PolarDB-X databases that are created based on PolarDB for MySQL clusters.
  • Data update
  • Schema update
Note You can configure a change tracking task for this scenario only in the DTS console of the new version.
Available soon

PolarDB for Oracle

All versions

Data update
Note You can configure a change tracking task for this scenario only in the DTS console of the new version.
Track data changes from a PolarDB for Oracle cluster

Self-managed Oracle database (non-RAC architecture)

Version 9i, 10g, or 11g

  • Data update
  • Schema update
New version of the DTS console: Track data changes from a self-managed Oracle database
  • ApsaraDB RDS for PostgreSQL

    Version 9.4, 10, 11, 12, or 13

  • Self-managed PostgreSQL database

    Version 9.4.8 or later, 9.5, 9.6, 10.x, 11.x, 12, or 13

Data update
Note You can configure a change tracking task for this scenario only in the DTS console of the new version.
Track data changes from an ApsaraDB RDS for PostgreSQL instance
DMS logical database
Note A logical database in DMS must be created based on the database shards of multiple PolarDB for MySQL clusters.
Data update
Note You can configure a change tracking task for this scenario only in the DTS console of the new version.
Available soon