All Products
Search

This Product

    Data Transmission Service:Create a similar task

    Document Center

    Data Transmission Service:Create a similar task

    Last Updated:Jun 20, 2026

    Creating multiple data transfer tasks with similar settings is tedious and error-prone. The Create Similar Task feature in Data Transmission Service (DTS) lets you use an existing task as a template to copy most of its settings to a new task in a single click. This improves configuration efficiency and reduces the risk of manual errors.

    Important

    This feature is a shortcut, not a full clone. The following critical information is not copied and must be reconfigured. Misusing this feature can cause the new task to behave unexpectedly. Before using this feature in production, you must read the configuration copy details and risks described in this document.

    • Source and target:

      • You can modify the source and target, but doing so does not automatically update dependent settings like task objects. You must carefully review all copied parameters.

      • Database password: For security reasons, you must re-enter the password.

    • Task configuration: instance parameters in advanced settings are reset to their defaults .

    • DTS task instance: You must purchase a new instance for the new task.

    Availability

    The Create Similar Task feature appears in the Actions column of the task list only when all the following conditions are met.

    • Supported task types: Data migration, data synchronization, and data validation.

    • Supported task statuses: The task must be fully configured. This feature is not available for tasks in the Not Configured or Staging state.

    • Tasks for Global Active Database (GAD) of RDS are not supported.

    Procedure

    This section describes how to use the Create Similar Task feature to quickly create a new task based on an existing one.

    1. Go to the Data Transmission Service (DTS) console. In the left-side navigation pane, select Data Synchronization, Data Migration, or Data Verification, depending on your task type.

    2. On the task list page, find the task to use as a template. In the Actions column, click Duplicate Task.

    3. DTS redirects you to the task configuration page and pre-fills most settings. You must carefully review and reconfigure the following key information:

      • Configure Source and Target Databases: Re-enter the passwords for the source and target databases.

      • Configure Task Objects: Review the copied task objects and related settings. Note that some parameters, such as instance parameters in advanced settings, are reset to their defaults and must be reconfigured.

      • Purchase Instance: Purchase a new DTS task instance.

    4. After you complete all configurations, run a precheck and start the task.

    Configuration copy details

    When you use the Create Similar Task feature, DTS copies some configuration items and resets others. The following table describes the rules.

    Configuration category

    Copied items

    Reset items

    Task Name

    By default, the name is the same as the original task name. We recommend that you change it to a meaningful name for easy identification. The name does not need to be unique.

    -

    Configure Source and Destination Databases

    Settings for the source/target database, such as Database Type, Access Method, Instance Region, Replicate Data Across Alibaba Cloud Accounts, Domain Name or IP and Port Number, Database Name, and SSL-encrypted.

    Note

    • Although these settings are copied, the connection or authorization information may have expired. Verify these settings. Also, make sure that the Database Account has sufficient permissions.

    • When the source database is an RDS for SQL Server instance, the Database Account defaults to the built-in account created by DTS, rdsdt_dtsacct. You must change it to the database account of the source RDS for SQL Server instance.

    • Database Password for the source/target database: This is cleared for security reasons and must be re-entered.

    • Database Account: If the original task used an RDS system account, the username is cleared.

    Configure Objects

    • The list of selected database and table objects, including any configured data filtering conditions or database, table, and column name mapping.

      Note

      • DTS copies the list of object names but does not verify their existence.

      • If the target is Kafka or RocketMQ, DTS clears the topic renaming configuration.

    • Task type (full/incremental).

    • DDL/DML operation types.

    -

    Advanced Settings

    The dedicated cluster from the original task.

    Instance parameters, such as the Retry Time for Failed Connections and the Retry Time for Other Issues.

    Data Verification

    All data validation settings from the original task.

    Note

    DTS copies the list of object names but does not verify their existence.

    -

    DTS task instance

    The DU settings of the original Serverless instance.

    You must purchase a new instance for the new task.

    Best practices and risks in production

    Risks

    • Inconsistent behavior due to missing task object settings

      This feature only copies basic settings such as task type (full/incremental), database/table objects, DDL/DML operation types, and data validation settings. Critical configuration items that affect task performance and data correctness, such as instance parameters in advanced settings, are reset to their defaults. If you do not reconfigure these parameters, the performance and data scope of the new task may differ significantly from the original task, leading to unexpected results.

    • Precheck failure due to changed database objects

      This feature copies only the list of database and table names from the original task's configuration. It does not verify if these objects still exist in the source database. If some databases or tables were deleted or renamed after the original task was created, the precheck for the new task will fail.

    Best practices

    • Treat the copied configuration as a template: Always treat a task created with this feature as a pre-filled template, not as a final configuration ready for execution.

    • Perform a comprehensive configuration review: Before you start the task, thoroughly review every configuration step, especially the database object selection and task object configuration. Ensure all settings meet the business requirements of the new task.

    • Monitor performance and load: Creating multiple similar tasks increases the load on the source and target databases and the demand on network bandwidth. Make sure your database resources are sufficient to prevent performance bottlenecks that could affect your business.

    FAQ

    Can I create a similar task from a released task instance?

    No. After a task instance is released, it is deleted from the task list and can no longer be used.

    Can I create a similar task by using an API?

    No.

    Can I create an identical instance with a single click?

    No.

    Why does the precheck report that database objects do not exist after I use Create Similar Task?

    This happens because the Create Similar Task feature only copies the list of database and table names from the original task and does not check if those objects currently exist. If objects were deleted or renamed after the original task was created, the precheck for the new task fails.

    Solution: In the object configuration step, manually verify and remove objects that do not exist, or reselect the correct objects.

    Why are the performance and behavior of the new task significantly different from the original one?

    This may be because task configuration items were reset to their default state. This feature only copies basic settings such as task type (full/incremental), the list of database/table objects, DDL/DML operation types, and data validation settings. However, critical settings that affect performance and data correctness, such as instance parameters in advanced settings, are reset to their defaults.

    Solution: In the task configuration step, carefully review and reconfigure all necessary advanced settings to match your business requirements.

    For a new synchronization requirement, should I use this feature to create a new task or modify an existing one?

    This depends on your requirements. A DTS task typically manages the data flow between one source and one target.

    • If the new requirement is to add new databases or tables between the existing source and target, you should edit the original task and add the new objects in the Configure Task Objects step.

    • If the new requirement involves a new source or target, and the task logic is similar to an existing task, you need to create a new DTS task. The Create Similar Task feature is ideal for this scenario, as it helps you quickly complete the basic configuration of the new task.

    Does creating a similar task affect the original task?

    No. This feature creates a new task that is separate from the original. It does not affect the operation or configuration of the original task.