Data Transmission Service (DTS) allows you to modify the number of DTS units (DUs) for a task that runs in a DTS dedicated cluster. If the performance of a task cannot meet your business requirements, you can allocate more DUs to the task to improve its performance.

Prerequisites

Usage notes

After you modify the number of DUs for a task, the task immediately restarts. We recommend that you modify the number of DUs for a task during off-peak hours. If the data in the source database changes during the restart of a task, take note of the following impacts:
  • Data synchronization task: The data may be inconsistent between the source and destination databases.
  • Data migration task: The data may be inconsistent between the source and destination databases.
  • Change tracking task: The task may fail to track incremental data.
After the task is restarted and the incremental data is processed, the data is consistent between the source and destination databases, and the incremental data that is generated during the restart can be tracked.

Procedure

  1. Go to the Dedicated Cluster page.
  2. Find the task for which you want to modify the number of DUs.
    1. In the top navigation bar, select the region in which the DTS dedicated cluster resides.
    2. On the Cluster Task page, click the name of the DTS dedicated cluster.
    3. In the left-side navigation pane, click Cluster Task List.
    4. Select the task type based on your requirements. Filter tasks
    5. In the filtered task list, find the task for which you want to modify the number of DUs.
  3. Click the More icon in the Actions column and select Change DU.
  4. In the New Instance Class section, modify the number of DUs.
    Note For more information about the relationship between the number of DUs allocated to a task and the performance of the task, see Performance specifications of tasks that run in a DTS dedicated cluster.
  5. Read and select the check box to agree to the Data Transmission Service (Pay-as-you-go) Service Terms.
  6. Click OK.
    The task immediately restarts. The modification takes effect when the task enters the running state.