All Products
Search
Document Center

Data Management:Overview of change tracking scenarios

Last Updated:Oct 18, 2024

Data Transmission Service (DTS) provides the change tracking feature to track data changes from databases in real time. This feature allows you to consume the tracked data and write data to a destination database. You can use the change tracking feature 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 scenarios

Note

Whether cross-account change tracking is supported depends on the access method and type of the source database. To create a change tracking task across Alibaba Cloud accounts, you must set the Replicate Data Across Alibaba Cloud Accounts parameter to Yes for the source database. For more information about the databases that support cross-account change tracking, see the Supported databases section of the "Configure a DTS task across Alibaba Cloud accounts" topic.

Source database

Data change type

Reference

  • Self-managed MySQL database

    Supported versions: 5.1, 5.5, 5.6, 5.7, and 8.0

  • ApsaraDB RDS for MySQL

    All versions

  • Data update

  • Schema update

Track data changes from an ApsaraDB RDS for MySQL instance

PolarDB for MySQL

All versions

  • Data update

  • Schema update

Track data changes from a PolarDB for MySQL cluster

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.

  • Data update

  • Schema update

Track data changes from a PolarDB-X 1.0 instance

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.

  • Data update

  • Schema update

Track data changes from a PolarDB-X instance

PolarDB for PostgreSQL (Compatible with Oracle)

All versions

Data update

Track data changes from a PolarDB for Oracle cluster

Self-managed Oracle database (non-RAC architecture)

Supported versions: 9i, 10g, and 11g

  • Data update

  • Schema update

Track data changes from a self-managed Oracle database

  • ApsaraDB RDS for PostgreSQL

    Supported versions: 9.4, 10, 11, 12, 13, 14, 15, and 16

  • Self-managed PostgreSQL database

    Supported versions 9.4.8 and later, 9.5, 9.6, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, and 16.x

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

Track data changes from a DMS logical database

PolarDB for PostgreSQL

Supported versions: 11 and 14

  • Data update

  • Schema update

Track data changes from a PolarDB for PostgreSQL cluster