Data Transmission Service (DTS) no longer provides the previous change tracking feature for DRDS instances after December 1, 2021. To minimize the impacts on your business, we recommend that you use the new change tracking feature to track data changes in a DRDS instance.

Description

Data Transmission Service (DTS) no longer provides the previous change tracking feature for DRDS instances after December 1, 2021.

Note Change tracking tasks of the previous version cannot be created or configured for DRDS instances after December 1, 2021. However, if your change tracking task starts running before December 1, 2021, the task is not affected. You can still manage the task in the DTS console.

Impacts and recommendations

Scenario Impact Recommendation
You create a task to track data changes from a DRDS instance and the task starts running before December 1, 2021. After December 1, 2021, you do not need to create or configure a task to track data changes in a DRDS instance by using the previous change tracking feature. None. Your task is not affected. You can still manage the task for your DRDS instance in the DTS console after December 1, 2021. N/A
Notice After February 28, 2022, change tracking tasks created by using the previous change tracking feature for DRDS instances cannot be managed in the DTS console. Therefore, we recommend that you start to use the new change tracking feature for DRDS instances at the earliest opportunity.
You create a task to track data changes from a DRDS instance and the task starts running before December 1, 2021. After December 1, 2021, you need to create and configure another task to track data changes in a DRDS instance by using the previous change tracking feature. After December 1, 2021, DTS does not provide the previous change tracking feature for DRDS instances. We recommend that you use the new change tracking feature to track data changes in your DRDS instance and use the new SDK to consume the tracked data. Procedure:
  1. Track data changes from a DRDS instance.
  2. For more information about the sample code used for distributed change tracking, visit GitHub.
Notice If you need to track data changes in a DRDS instance, we recommend that you use the new change tracking feature at the earliest opportunity.
You want to use or start using the new change tracking feature to track data changes in a DRDS instance. None. To create a task to track data changes in a DRDS instance and consume the tracked data, perform the following steps:
  1. Track data changes from a DRDS instance.
  2. For more information about the sample code used for distributed change tracking, visit GitHub.

FAQ

How to determine whether a change tracking task for a DRDS instance is created by using the new change tracking feature or the previous version?

If the ID/Name of your change tracking instance for a DRDS instance is followed by the  icon after the change tracking instance starts running, the change tracking task is created by using the new change tracking feature for the DRDS instance. Otherwise, the change tracking task is created by using the previous version.

Technical support

If you have questions about the feature upgrade or business adaptation, submit a ticket for technical support.