You can follow the general procedure in this topic to create and manage a task in change tracking mode.
- Use cases
The change tracking mode allows you to build a distributed application with decoupled data systems, so you can implement your asynchronous replications between these data systems.
- Supported databases and data changes
For more information about databases and update types that are supported by the change tracking mode, see Supported sources and targets.
- Advanced features
For information about the features of a change tracking task, see Change tracking mode.
Change tracking procedure
You can complete the following higher level steps to create and manage a change tracking task.
|1. Set up the networking environment||
Before you use DTS for change tracking, prepare the environments that are required for the source and target databases.
For more information, see Set up a network environment for replication.
|2. Create a change tracking instance||Create a change tracking instance in the DTS console. The instance can be either pay-as-you-go or subscription.|
|3. Create a change tracking task||Create a change tracking task for the instance that you created. When creating a task, you will set up the connection to the data source and select the objects that are to be tracked.|
|4. Configure consumer settings||
|4. Consume tracked data||Use a Kafka client to consume tracked data. For more information, see Use a Kafka client to consume tracked data.|
|5. Stop the change tracking task||If you want to stop the change tracking task, delete the instance.
Note You can also reset a change tracking instance to stop the associated task. For more information, see Reset a change tracking task.