Migrate SQL Server on Azure to the cloud-Data Transmission Service(DTS)-阿里云帮助中心

Background

This document describes two methods for migrating a Microsoft Azure SQL Server database.

One-stop cloud migration using the RDS console

The RDS console provides a one-stop cloud migration feature to quickly and easily migrate data from a Microsoft Azure SQL Server database to ApsaraDB RDS for SQL Server.

Note
By default, this method includes schema migration, full data migration, and incremental data migration.
Cloud migration using DTS

Data Transmission Service (DTS) supports data migration. Unlike the one-stop cloud migration on the RDS console, DTS lets you select specific migration types, such as schema migration, full data migration, and incremental data migration, and configure more advanced parameters.

Scope of application

The source SQL Server database on Microsoft Azure is connected to Alibaba Cloud, allowing DTS to access the source database. For more information, see Connect a Microsoft Azure database to Alibaba Cloud.
A destination ApsaraDB RDS for SQL Server instance has been created and has more storage space than the total data in the source database. For more information, see Create an ApsaraDB RDS for SQL Server instance.

Precautions

Type	Description
Source database limits	For SQL Server on Azure Virtual Machines, Enterprise Edition must be 2008 or later, and Standard Edition must be 2016 SP1 or later. Version 2017 is not supported. Bandwidth requirement: The server that hosts the source database must have sufficient outbound bandwidth. Insufficient bandwidth reduces data migration speed. The tables to be migrated must have a primary key or unique constraint, and the columns in the key or constraint must be unique. Otherwise, duplicate data may exist in the target database. A single migration task can migrate a maximum of 10 databases. Exceeding this limit may cause stability and performance issues. Split the migration into multiple tasks if needed. If you configure a task to migrate specific objects instead of an entire database, you cannot migrate objects that have the same table name but different schema names to the same destination database within a single task. For an incremental data migration task, DTS requires that the transaction logs of the source database are retained for at least 24 hours. For a task that includes both full data migration and incremental data migration, retain logs for at least 7 days. You can change the retention period to at least 24 hours after full data migration is complete. Otherwise, the DTS task may fail due to unavailable transaction logs. In extreme cases, data inconsistency or loss may occur. Issues caused by insufficient log retention are not covered by the Service Level Agreement (SLA). Limits on operations in the source database: During the schema migration and full data migration phases, do not perform DDL operations that change the database or table structure. Otherwise, the data migration task fails. If you perform only full data migration, do not write new data to the source instance. Otherwise, data will become inconsistent between the source and target databases. To ensure real-time data consistency, select schema migration, full data migration, and incremental data migration. The source database cannot be a read-only instance. If the source database is an Azure SQL Database, a migration instance can migrate only one database. If you use the `sp_rename` command to rename objects such as stored procedures before the schema migration task runs, the task may not work as expected or may fail. Note Use the `ALTER` command to rename database objects. During full data migration, enable the `READ_COMMITTED_SNAPSHOT` parameter for the source database to prevent shared lock contention from affecting data writes. Otherwise, data inconsistency or task failure may occur. Issues caused by not enabling this parameter are not covered by the DTS SLA.
Other limits	DTS does not support migrating the following data types: CURSOR, ROWVERSION, SQL_VARIANT, HIERARCHYID, POLYGON, GEOMETRY, and GEOGRAPHY. To migrate triggers from the source database, the database account used for the migration task must have Owner permissions on the destination database. If data cannot be written to a column of the TIMESTAMP data type in the destination database, DTS does not support full or incremental data migration. This may lead to data inconsistency or task failure. The precheck module for a DTS incremental data migration task enables CDC in the source database. During this process, the SQL Server engine's internal limitations may cause temporary table locking in the source database. An incremental data migration task polls CDC instances to migrate incremental data. Therefore, the following limits apply: DTS obtains incremental data by polling the CDC instance of each table in the source database. Therefore, the number of tables to be synchronized from the source database cannot exceed 1,000. Otherwise, the task may experience high latency or instability. By default, the CDC component stores incremental data for three days. Adjust the retention period by running the `exec console.sys.sp_cdc_change_job @job_type = 'cleanup', @retention= <time>;` command. Note `<time>` specifies the retention period in minutes. If the average number of daily incremental SQL changes for a single table exceeds 10 million, set `<time>` to 1440. Consecutive column add or drop operations are not supported (more than two ADD COLUMN or DROP COLUMN DDL operations within one minute). Otherwise, the migration task may fail. Do not modify the CDC instances of the source database. Otherwise, the migration task may fail or data loss may occur. Migrating multiple databases and tables poses a risk to stability and performance. Incremental data migration has a latency of approximately 10 seconds. If you migrate data across different SQL Server versions, verify compatibility in advance. If a migration task includes incremental data migration, you cannot rebuild indexes. You must also disable all triggers and foreign keys in the target database. Otherwise, the task may fail or result in data loss. Note You cannot modify the primary key of a table for which CDC is enabled. If the number of CDC-enabled tables in a single migration task is greater than 1,000 (or greater than the value configured for The maximum number of tables for which CDC is enabled that DTS supports.), the precheck fails. If a task includes incremental migration and a single field in a CDC-enabled table to be written contains more than 64 KB of data, run the `exec sp_configure 'max text repl size', -1;` command to adjust the source database configuration in advance. Note By default, a CDC job can process a maximum data size of 64 KB for a single field. DTS automatically creates databases in ApsaraDB RDS for SQL Server. If the name of the database to be migrated does not conform to the naming conventions of ApsaraDB RDS for SQL Server, you must create the database in ApsaraDB RDS for SQL Server before you configure the migration task. For more information, see Create a database. To ensure accurate latency reporting for incremental data migration, DTS creates a `dts_cdc_sync_ddl` trigger, a `dts_sync_progress` heartbeat table, and a `dts_cdc_ddl_history` DDL storage table in the source database. For hybrid incremental synchronization, DTS creates the same objects and also enables database-level and table-level CDC. For tables where CDC is enabled, we recommend that the rate of data changes does not exceed 1,000 rows per second (RPS). Before you migrate data, evaluate the performance of the source and target databases and perform data migration during off-peak hours. During full data migration, DTS consumes read and write resources on both databases, increasing their load. During full data migration, concurrent INSERT operations can cause fragmentation in the target tables, so table storage space in the target database may be larger than in the source instance after migration. Verify that the migration precision that DTS uses for FLOAT and DOUBLE data types meets your business requirements. DTS uses the `ROUND(COLUMN,PRECISION)` function to read values from these columns. If a precision is not explicitly defined, DTS migrates FLOAT values with a precision of 38 digits and DOUBLE values with a precision of 308 digits. DTS attempts to resume a failed migration task for up to seven days. Before you switch your business workloads to the target instance, you must stop or release the task. Alternatively, revoke the write permissions of the DTS account on the target instance by using the `revoke` command to prevent a resumed task from overwriting target data. When multiple migration instances use the same source SQL Server database, their incremental data collection modules operate independently. If a task fails, DTS support staff will attempt to restore it within eight hours. During restoration, they may restart the task or adjust its parameters. Note Only DTS task parameters are modified—not database parameters. Parameters that may be adjusted include those listed in Modify instance parameters. SQL Server is a commercial, closed-source database whose log format can cause unavoidable issues during incremental CDC and parsing in DTS. Before enabling DTS for incremental synchronization from a SQL Server source in a production environment, perform comprehensive proof-of-concept (POC) testing that covers all business change scenarios, schema adjustments, and peak-load stress tests. Consistency between your production environment logic and the POC phase is essential for stable DTS operations. During incremental data migration, if a transaction is partially rolled back in the source database, DTS may not capture the rollback operation.

Billing

Migration type	Instance configuration fee	Internet traffic fee
Schema migration and full data migration	Free of charge.	When the Access Method parameter of the destination database is set to Public IP Address, you are charged for Internet traffic. For more information, see Billing overview.
Incremental data migration	Charged. For more information, see Billing overview.

Migration types

Schema migration

DTS migrates the schema definitions of the migration objects from the source database to the destination database.
- DTS supports schema migration for the following objects: tables, views, triggers, synonyms, SQL stored procedures, SQL functions, plan guides, user-defined types, rules, defaults, and sequences.
- DTS does not support schema migration for the following objects: assemblies, service brokers, full-text indexes, full-text catalogs, distributed schemas, distributed functions, Common Language Runtime (CLR) stored procedures, CLR scalar-valued functions, CLR table-valued functions, internal tables, systems, or aggregate functions.
Full migration

DTS migrates all historical data of the specified migration objects from the source database to the destination database.
Incremental migration

After a full migration is complete, DTS migrates incremental data updates from the source database to the destination database. Incremental migration lets you smoothly migrate data without interrupting your self-managed applications.

SQL operations for incremental data migration

Type	SQL statement
DML	`INSERT`, `UPDATE`, `DELETE` Note DTS does not support `UPDATE` statements that only update large fields.
DDL	`CREATE TABLE` `ALTER TABLE` Includes only `ADD COLUMN` and `DROP COLUMN`. `DROP TABLE` `CREATE INDEX`, `DROP INDEX` Note DTS does not support `transactional DDL`. For example, a single `SQL statement` that adds multiple columns or contains both `DDL` and `DML` operations can cause data loss. DTS does not support `DDL` operations that involve a `user-defined type`. DTS does not support `online DDL` operations. DTS does not support `DDL` operations that use a `reserved keyword` as an attribute name. DTS does not support `DDL` operations executed from a `system stored procedure`. DTS does not support `TRUNCATE TABLE` operations. DTS does not support `partition`s or `table definition`s that contain functions.

Database account permissions

Database	Schema migration	Full data migration	Incremental data migration	Creation and authorization
Microsoft Azure SQL Database	SELECT permission	SELECT permission	sysadmin role Note The server admin account in the Azure SQL Database console has the required permissions. For databases that use the vCore model, all service tiers support CDC. For databases that use the DTU model, only service objectives of S3 and higher support CDC.	For more information, contact Microsoft Azure support.
ApsaraDB RDS for SQL Server instance	Read and write permissions			Create a standard, privileged, or global read-only account and Modify the permissions of an account.

Procedure

One-stop migration to ApsaraDB RDS

Go to the Data Migration tab of the destination ApsaraDB RDS for SQL Server instance.
1. Go to the ApsaraDB RDS instances list.
2. In the top navigation bar, select the region where the destination ApsaraDB RDS for SQL Server instance resides.
3. Click the ID of the destination ApsaraDB RDS for SQL Server instance.
4. In the left-side navigation pane, click Data Migration and Synchronization.
5. Click the Data Migration tab.
Click End-to-End Cloud Migration.

Configure the source and destination databases.

Category	Parameter	Description
N/A	Task Name	DTS automatically generates a task name. We recommend specifying a descriptive name for easy identification. The name does not need to be unique.
Source Database	Database Type	The value is SQL Server by default. You do not need to change this setting.
	Type	Select Azure.
	Access Method	Select Public IP Address or Express Connect, VPN Gateway, or Smart Access Gateway depending on how the SQL Server database on Microsoft Azure connects to Alibaba Cloud. Important If the source database is an Azure SQL Managed Instance, select Public IP Address.
	Instance Region	If you set Access Method to Public IP Address, select the region of the SQL Server database on Microsoft Azure. Note If the region of the SQL Server database on Microsoft Azure is not available, you can select the region that is geographically closest to the database. If you set Access Method to Express Connect, VPN Gateway, or Smart Access Gateway, select the region of the VPC to which the SQL Server database on Microsoft Azure is connected.
	Connected VPC	Select the ID of the VPC to which the SQL Server database on Microsoft Azure is connected. Note This parameter is available only if you set Access Method to Express Connect, VPN Gateway, or Smart Access Gateway.
	Domain Name or IP	Enter the domain name or IP address of the SQL Server database on Microsoft Azure. Note We recommend that you enter the domain name.
	Port Number	Enter the service port of the SQL Server database on Azure.
	Database Account	Enter the database account for the SQL Server database on Azure. For information about the required permissions, see Permissions required for database accounts. Important The account for an Azure SQL Database uses the format `<admin_account>@<instance_server_name>`. For example, if the administrator account of the Azure SQL Database is `testuser` and the instance server name is `dtstest` (which you can query by running the `SELECT @@SERVERNAME AS ServerName` command), enter `testuser@dtstest` for Database Account.
	Database Password	Enter the password for the database account.
	Encryption	Select Non-encrypted or SSL-encrypted based on your business requirements. If SSL encryption is disabled for the source database, select Non-encrypted. If SSL encryption is enabled for the source database, select SSL-encrypted. By default, DTS trusts the server certificate.
Destination Database	Database Type	The value is SQL Server by default. You do not need to change this setting.
	Access Method	The value is Alibaba Cloud Instance by default. You do not need to change this setting.
	Instance Region	This parameter is fixed to the region of the current ApsaraDB RDS for SQL Server instance and cannot be changed.
	Instance ID	This parameter is fixed to the ID of the current ApsaraDB RDS for SQL Server instance and cannot be changed.
	Database Account	Enter the database account of the current ApsaraDB RDS for SQL Server instance. For information about the required permissions, see Permissions required for database accounts.
	Database Password	Enter the password for the database account.
	Encryption	Select Non-encrypted or SSL-encrypted based on your business requirements. If SSL encryption is disabled for the destination database, select Non-encrypted. If SSL encryption is enabled for the destination database, select SSL-encrypted. By default, DTS trusts the server certificate.

At the bottom of the page, click Test Connectivity and Proceed.

In the dialog box that appears, ensure that the CIDR blocks of DTS servers are in the whitelist of the SQL Server database on Microsoft Azure. Then, click Test Connectivity.

Important
Adding the public IP address CIDR blocks of DTS servers to a whitelist may pose security risks. By using this product, you acknowledge and accept these potential risks. You are responsible for implementing basic security measures, such as strengthening your account passwords, restricting open ports for each CIDR block, using authentication for internal API calls, and regularly reviewing and limiting unnecessary network segments. For more information, see Add the IP addresses of DTS servers to a whitelist.
Select a migration plan.

The system evaluates your source database type and provides the following cloud migration plans:
- Select the Full and Incremental Data Migration plan, click Configure Objects at the bottom of the page.
- If you select another migration plan, you do not need to perform the subsequent steps.
  
  Note
  You can click View Migration Documentation at the bottom of the page to view the procedures for other migration plans.

On the Configure Objects page, select the objects to migrate.

Parameter	Description
Method to Migrate Triggers in Source Database	During incremental data migration, if triggers are migrated to the destination database too early, data may become inconsistent between the source and destination databases. We recommend that you select Manual Migration. For more information, see Configure how to synchronize or migrate triggers. Note If the objects that you want to migrate do not involve triggers, you can keep the default setting for this parameter.
Source Objects	In the Source Objects box, click the objects to migrate, and then click to move them to the Selected Objects box. Note You can select databases, tables, or columns as migration objects. If you select only tables or columns, other objects such as views, triggers, and stored procedures are not migrated to the destination database.
Selected Objects	To change the name of a migration object in the destination instance, right-click the object in the Selected Objects box and modify its name. For more information, see Map object names. To remove a selected migration object, click the object in the Selected Objects box and click to move it to the Source Objects box. Note If you use the object name mapping feature, the migration of other objects that depend on the renamed object may fail. To filter data by using WHERE clauses, right-click a table in the Selected Objects box and specify the filter conditions in the dialog box that appears. For more information, see Configure filter conditions. To select the SQL operations to migrate at the database or table level, right-click an object in the Selected Objects box and select the desired operations in the dialog box that appears.

Optional: Configure advanced settings.

You can expand the Advanced Settings section to configure advanced parameters.

Parameter	Description
Enable Throttling for Full Data Migration	During full migration, DTS consumes read and write resources on the source and destination databases, which may increase the database load. If required, you can enable throttling for the full migration task. You can set Queries per second (QPS) to the source database, RPS of Full Data Migration, and Data migration speed for full migration (MB/s) to reduce the load on the destination database.
Enable Throttling for Incremental Data Migration	If required, you can also choose to set speed limits for the incremental migration task. You can set RPS of Incremental Data Migration and Data migration speed for incremental migration (MB/s) to reduce the load on the destination database.
Data Verification Mode	Full data verification consumes read resources on the database. If you select Full Data Verification, you must also set Maximum number of rows of data read per second by full verification (RPS) and Maximum amount of data read per second by full verification (MBps) to limit the verification task and reduce the load on the database. Note A value of 0 indicates no limit. If both Maximum number of rows of data read per second by full verification (RPS) and Maximum amount of data read per second by full verification (MBps) are set to 0, the rate is not limited.

Save the task and run a precheck.
- To view the parameters for configuring this instance when you call the API operation, move the pointer over the Next: Save Task Settings and Precheck button and click Preview OpenAPI parameters in the bubble that appears.
- If you do not need to view or have finished viewing the API parameters, click Next: Save Task Settings and Precheck at the bottom of the page.
Note
- Before the migration task starts, DTS performs a precheck. The task starts only after it passes the precheck.
- If the precheck fails, click View Details next to the failed check item, fix the issue based on the prompt, and then run the precheck again.
- If a warning is reported during the precheck:
  
  For check items that cannot be ignored, click View Details next to the failed item, fix the issue based on the prompt, and then run the precheck again.
  
  For check items that can be ignored, you can click Confirm Alert Details, Ignore, OK, and Precheck Again to skip the alert item and run the precheck again. If you choose to ignore a warning, it may cause issues such as data inconsistency and pose risks to your business.
When the Success Rate is 100%, click Next: Purchase Instance.

Purchase a data migration instance.

On the Purchase page, select the link specification for the data migration instance. For more information, see the following table.

Category	Parameter	Description
New Instance Class	Resource Group Settings	Select the resource group to which the instance belongs. The default value is default resource group. For more information, see What is Resource Management?
New Instance Class	Instance Class	DTS provides migration specifications with different performance levels. The link specification affects the migration speed. You can select a specification based on your business scenario. For more information, see Data migration link specifications.

After the configuration is complete, read and select Data Transmission Service (Pay-as-you-go) Service Terms.
Click Buy and Start. In the OK dialog box that appears, click OK.

You can view the progress of the migration task on the Data Migration Tasks list page.
Note
- If the migration task does not include incremental migration, it stops automatically after the full migration is complete. After the task stops, its Status changes to Completed.
- If the migration task includes incremental migration, it does not stop automatically. The incremental migration task continues to run. While the incremental migration task is running, the Status of the task is Running.

Migrate data by using DTS

Go to the Data Migration Tasks page for the target region.
1. Log in to the DTS console.
2. In the left-side navigation pane, click Data Migration.
3. In the top navigation bar, select the region where the destination instance is located.
Click Create Task to navigate to the task configuration page.

Configure the source and destination databases.

Category	Parameter	Description
N/A	Task Name	DTS automatically generates a task name. We recommend that you specify a descriptive name for easy identification. The name does not need to be unique.
Source Database	Select Existing Connection	If you select an existing connection, DTS automatically populates the database information. If you do not select an existing connection, you must manually enter the database information. Note You can add a database connection on the Database Connections page or on the new configuration page. For more information, see Manage database connections.
	Database Type	Select SQL Server.
	Access Method	Select Public IP Address or Express Connect, VPN Gateway, or Smart Access Gateway depending on how the SQL Server database on Microsoft Azure connects to Alibaba Cloud. Important If the source database is an Azure SQL Managed Instance, select Public IP Address.
	Instance Region	If you set Access Method to Public IP Address, select the region of the SQL Server database on Microsoft Azure. Note If the region of the SQL Server database on Microsoft Azure is not available, you can select the region that is geographically closest to the database. If you set Access Method to Express Connect, VPN Gateway, or Smart Access Gateway, select the region of the VPC to which the SQL Server database on Microsoft Azure is connected.
	Replicate Data Across Alibaba Cloud Accounts	In this example, a database instance under the current Alibaba Cloud account is used. Select No. Note This parameter is available only if you set Access Method to Express Connect, VPN Gateway, or Smart Access Gateway.
	Connected VPC	Select the ID of the VPC to which the SQL Server database on Microsoft Azure is connected. Note This parameter is available only if you set Access Method to Express Connect, VPN Gateway, or Smart Access Gateway.
	Domain Name or IP	Enter the domain name or IP address of the SQL Server database on Microsoft Azure. Note We recommend that you enter the domain name.
	Port Number	Enter the service port of the SQL Server database on Microsoft Azure.
	Database Account	Enter the account of the SQL Server database on Microsoft Azure. For information about the required permissions, see Permissions required for database accounts. Important The account for an Azure SQL Database uses the format `<admin_account>@<instance_server_name>`. For example, if the administrator account of the Azure SQL Database is `testuser` and the instance server name is `dtstest` (which you can query by running the `SELECT @@SERVERNAME AS ServerName` command), enter `testuser@dtstest` for Database Account.
	Database Password	Enter the password for the database account.
	Encryption	Select Non-encrypted or SSL-encrypted based on your business requirements. If SSL encryption is disabled for the source database, select Non-encrypted. If SSL encryption is enabled for the source database, select SSL-encrypted. By default, DTS trusts the server certificate.
Destination Database	Select Existing Connection	If you select an existing connection, DTS automatically populates the database information. If you do not select an existing connection, you must manually enter the database information. Note You can add a database connection on the Database Connections page or on the new configuration page. For more information, see Manage database connections.
	Database Type	Select SQL Server.
	Access Method	Select Alibaba Cloud Instance.
	Instance Region	Select the region where the destination ApsaraDB RDS for SQL Server instance resides.
	Instance ID	Select the ID of the destination ApsaraDB RDS for SQL Server instance.
	Database Account	Enter the database account of the destination ApsaraDB RDS for SQL Server instance. For information about the required permissions, see Permissions required for database accounts.
	Database Password	Enter the password for the database account.
	Encryption	Select Non-encrypted or SSL-encrypted based on your business requirements. If SSL encryption is disabled for the destination database, select Non-encrypted. If SSL encryption is enabled for the destination database, select SSL-encrypted. By default, DTS trusts the server certificate.

At the bottom of the page, click Test Connectivity and Proceed.

In the dialog box that appears, ensure that the CIDR blocks of DTS servers are in the whitelist of the SQL Server database on Microsoft Azure. Then, click Test Connectivity.

Important
Adding the public IP address CIDR blocks of DTS servers to a whitelist may pose security risks. By using this product, you acknowledge and accept these potential risks. You are responsible for implementing basic security measures, such as strengthening your account passwords, restricting open ports for each CIDR block, using authentication for internal API calls, and regularly reviewing and limiting unnecessary network segments. For more information, see Add the IP addresses of DTS servers to a whitelist.

Configure the task objects.

On the Configure Objects page, configure the objects that you want to migrate.

Parameter	Description
Migration Types	If you only need to perform a full migration, select both Schema Migration and Full Data Migration. To perform a migration with no downtime, select Schema Migration, Full Data Migration, and Incremental Data Migration. Note If you do not select Schema Migration, you must ensure that a database and tables to receive the data exist in the destination database. You can also use the object name mapping feature in the Selected Objects box as needed. If you do not select Incremental Data Migration, do not write new data to the source instance during data migration to ensure data consistency.
Method to Migrate Triggers in Source Database	During incremental data migration, if triggers are migrated to the destination database too early, data may become inconsistent between the source and destination databases. We recommend that you select Manual Migration. For more information, see Configure how to synchronize or migrate triggers. Note You can configure this parameter only if you select both Schema Migration and Incremental Data Migration for Migration Types. If the objects to be migrated do not involve triggers, you do not need to configure this parameter. You can use the default value.
SQL Server Incremental Synchronization Mode	Select Polling and querying CDC instances for incremental synchronization. Note This parameter is available only if Incremental Data Migration is selected for Migration Types.
The maximum number of tables for which CDC is enabled that DTS supports.	In this example, no modification is needed. Keep the default value.
Processing Mode of Conflicting Tables	Precheck and Report Errors: Checks whether tables with the same names exist in the destination database. If no tables with the same names exist, the precheck is passed. If tables with the same names exist, an error is reported during the precheck, and the data migration task does not start. Note If a table in the destination database has the same name but cannot be easily deleted or renamed, you can change the name of the table in the destination database. For more information, see Object name mapping. Ignore Errors and Proceed: Skips the check for tables with the same names. Warning Selecting Ignore Errors and Proceed may cause data inconsistency and business risks. For example: If the table schemas are consistent and a record in the destination database has the same primary key value as a record in the source database: During full migration, DTS keeps the record in the destination database. The record from the source database is not migrated. During incremental migration, DTS does not keep the record in the destination database. The record from the source database overwrites the record in the destination database. If the table schemas are inconsistent, only some columns of data may be migrated, or the migration may fail. Proceed with caution.
Capitalization of Object Names in Destination Instance	You can configure the case sensitivity policy for the names of migrated objects, such as databases, tables, and columns, in the destination instance. By default, DTS default policy is selected. You can also choose to keep the case sensitivity consistent with the default policy of the source or destination database. For more information, see Case sensitivity of object names in the destination database.
Source Objects	In the Source Objects box, click the objects to migrate, and then click to move them to the Selected Objects box. Note You can select databases, tables, or columns as migration objects. If you select only tables or columns, other objects such as views, triggers, and stored procedures are not migrated to the destination database.
Selected Objects	To change the name of a migration object in the destination instance, right-click the object in the Selected Objects box and modify its name. For more information, see Map object names. To remove a selected migration object, click the object in the Selected Objects box and click to move it to the Source Objects box. Note If you use the object name mapping feature, the migration of other objects that depend on the renamed object may fail. To filter data by using WHERE clauses, right-click a table in the Selected Objects box and specify the filter conditions in the dialog box that appears. For more information, see Configure filter conditions. To select the SQL operations to migrate at the database or table level, right-click an object in the Selected Objects box and select the desired operations in the dialog box that appears.

Click Next: Advanced Settings to configure advanced parameters.

Parameter	Description
Dedicated Cluster for Task Scheduling	By default, DTS schedules tasks on a shared cluster. You do not need to select one. If you want more stable tasks, you can purchase a dedicated cluster to run DTS migration tasks.
Retry Time for Failed Connections	After the migration task starts, if the connection to the source or destination database fails, DTS reports an error and immediately begins to retry the connection. The default retry duration is 720 minutes. You can customize the retry time to a value from 10 to 1440 minutes. We recommend that you set the duration to more than 30 minutes. If DTS reconnects to the source and destination databases within the specified duration, the migration task automatically resumes. Otherwise, the task fails. Note For multiple DTS instances that share the same source or destination, the network retry time is determined by the setting of the last created task. Because you are charged for the task during the connection retry period, we recommend that you customize the retry time based on your business needs, or release the DTS instance as soon as possible after the source and destination database instances are released.
Retry Time for Other Issues	After the migration task starts, if a non-connectivity issue, such as a DDL or DML execution exception, occurs in the source or destination database, DTS reports an error and immediately begins to retry the operation. The default retry duration is 10 minutes. You can customize the retry time to a value from 1 to 1440 minutes. We recommend that you set the duration to more than 10 minutes. If the related operations succeed within the specified retry duration, the migration task automatically resumes. Otherwise, the task fails. Important The value of Retry Time for Other Issues must be less than the value of Retry Time for Failed Connections.
Enable Throttling for Full Data Migration	During full migration, DTS consumes read and write resources on the source and destination databases, which may increase the database load. If required, you can enable throttling for the full migration task. You can set Queries per second (QPS) to the source database, RPS of Full Data Migration, and Data migration speed for full migration (MB/s) to reduce the load on the destination database. Note This configuration item is available only if you select Full Data Migration for Migration Types. You can also adjust the full migration speed after the migration instance is running.
Enable Throttling for Incremental Data Migration	If required, you can also choose to set speed limits for the incremental migration task. You can set RPS of Incremental Data Migration and Data migration speed for incremental migration (MB/s) to reduce the load on the destination database. Note This configuration item is available only if you select Incremental Data Migration for Migration Types. You can also adjust the incremental migration speed after the migration instance is running.
Environment Tag	You can select an environment tag to identify the instance based on your business requirements. In this example, you do not need to select a tag.
Configure ETL	Choose whether to enable the extract, transform, and load (ETL) feature. For more information, see What is ETL? Valid values: Yes: Enables the ETL feature. Enter data processing statements in the code editor. For more information, see Configure ETL in a data migration or data synchronization task. No: Disables the ETL feature.
Monitoring and Alerting	Select whether to set alerts and receive alert notifications based on your business needs. No: Does not set an alert. Yes: Configure alerts by setting an alert threshold and an alert contact. If a migration fails or the latency exceeds the threshold, the system sends an alert notification.

Click Next: Data Verification to configure a data verification task.

If you need to use the data verification feature, see Configure data verification for instructions.

Save the task and run a precheck.
- To view the parameters for configuring this instance when you call the API operation, move the pointer over the Next: Save Task Settings and Precheck button and click Preview OpenAPI parameters in the bubble that appears.
- If you do not need to view or have finished viewing the API parameters, click Next: Save Task Settings and Precheck at the bottom of the page.
Note
- Before the migration task starts, DTS performs a precheck. The task starts only after it passes the precheck.
- If the precheck fails, click View Details next to the failed check item, fix the issue based on the prompt, and then run the precheck again.
- If a warning is reported during the precheck:
  
  For check items that cannot be ignored, click View Details next to the failed item, fix the issue based on the prompt, and then run the precheck again.
  
  For check items that can be ignored, you can click Confirm Alert Details, Ignore, OK, and Precheck Again to skip the alert item and run the precheck again. If you choose to ignore a warning, it may cause issues such as data inconsistency and pose risks to your business.

Purchase an instance.

When the Success Rate is 100%, click Next: Purchase Instance.

On the Purchase page, select the link specification for the data migration instance. For more information, see the following table.

Category	Parameter	Description
New Instance Class	Resource Group Settings	Select the resource group to which the instance belongs. The default value is default resource group. For more information, see What is Resource Management?
New Instance Class	Instance Class	DTS provides migration specifications with different performance levels. The link specification affects the migration speed. You can select a specification based on your business scenario. For more information, see Data migration link specifications.

After the configuration is complete, read and select Data Transmission Service (Pay-as-you-go) Service Terms.
Click Buy and Start. In the OK dialog box that appears, click OK.

You can view the progress of the migration task on the Data Migration Tasks list page.
Note
- If the migration task does not include incremental migration, it stops automatically after the full migration is complete. After the task stops, its Status changes to Completed.
- If the migration task includes incremental migration, it does not stop automatically. The incremental migration task continues to run. While the incremental migration task is running, the Status of the task is Running.

FAQ

Can I select verification objects for ApsaraDB RDS One-Stop Cloud Migration?

No. By default, the verification objects are the same as the migration objects.
How is full data verification performed for ApsaraDB RDS One-Stop Cloud Migration?

The process uses HASH verification at a 100% sampling ratio.
What is the benchmark for full data verification in ApsaraDB RDS One-Stop Cloud Migration?

It uses the union of data from the source and destination databases as the benchmark to verify data consistency.