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.

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 Reference
  • 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

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

Self-managed Oracle database (non-RAC architecture)

Version 9i, 10g, and 11g

  • Data update
  • Schema update
Track data changes from a user-created Oracle database

Change tracking (previous)

Source database Data change type Reference

ApsaraDB RDS for MySQL

Version 5.5, 5.6, or 5.7

Note ApsaraDB RDS for MySQL users can no longer use the previous change tracking feature after March 31, 2020. For more information, see [Notice] Data subscription mode discontinued as of March 31, 2020.
  • Data update
  • Schema update

Track data changes from an ApsaraDB RDS for MySQL instance

DRDS

MySQL version 5

Note The source database in the DRDS instance must be created based on ApsaraDB RDS for MySQL instances. DTS does not support DRDS databases that are created based on PolarDB for MySQL clusters.
Data update Track data changes from a DRDS instance