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
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 clients. For more information, see Change tracking (new).
The following types of databases are supported:
- Self-managed database with a public IP address
- Self-managed database without a public IP address or port number (connected over Database Gateway)
- Self-managed database connected over Cloud Enterprise Network (CEN)
- Self-managed database hosted on Elastic Compute Service (ECS)
- Self-managed database connected over Express Connect, VPN Gateway, or Smart Access Gateway
Source database | Data change type | References |
---|---|---|
|
| Track data changes from an ApsaraDB RDS for MySQL instance |
PolarDB MySQL All versions |
| 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. |
| 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. |
| Track data changes from a PolarDB-X instance |
PolarDB for 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 |
| Track data changes from a self-managed Oracle database |
| 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 PostgreSQL Supported version: 11 |
| Track data changes from a PolarDB for PostgreSQL cluster |