Use the change tracking feature - Data Transmission Service

You can use Data Transmission Service (DTS) to retrieve incremental data from data sources in real time. This feature applies to multiple scenarios, such as cache update, business decoupling, asynchronous data processing, real-time synchronization of heterogeneous data, and real-time synchronization of complex extract, transform, and load (ETL) operations. This topic describes how to create, monitor, and manage a change tracking task.

Background information

Overview of change tracking scenarios
This topic describes the database types and data types that support the change tracking feature.
Functions and features
For more information, see Change tracking.

Manage a change tracking task

Step	Description
Preparation overview	Before you use DTS for change tracking, prepare the environment that is required for the source database.
Configure a change tracking task by using the new DTS console	Create a change tracking task by completing simple configurations in the DTS console.
Manage the change tracking task	A consumer group is created. For more information, see Create consumer groups. After you configure a change tracking task, create one or more consumer groups to consume data. You can create multiple consumer groups for a change tracking task. Consumers in different consumer groups can track data changes from the same data source. This helps you reduce the cost of tracking data changes and improve the efficiency of data consumption. Optional. Manage consumer groups. Manage the consumer groups of the change tracking task. For example, you can modify passwords for consumer groups or delete consumer groups. Optional. Modify the objects for change tracking. Change the objects whose changes are tracked when the change tracking task is running.
Consume tracked data	Select a consumption mode based on the type of the consumer client and the type of the database. Use the SDK demo to consume tracked data Use the SDK demo code to consume the tracked data from a PolarDB-X 1.0 instance Use flink-dts-connector to consume tracked data Use a Kafka client to consume tracked data
Stop the change tracking task	If you want to stop the change tracking task, release the corresponding instance. Pay-as-you-go: For more information about how to release a pay-as-you-go change tracking instance, see Release a pay-as-you-go instances. Subscription: A subscription change tracking instance cannot be manually released. It will be automatically released seven days after the expiration date. Note You can also reset a change tracking instance to stop the change tracking task. For more information, see Reset a DTS instance.