This topic describes how to migrate data from a self-managed SQL Server database to an ApsaraDB RDS for SQL Server instance by using Data Transmission Service (DTS).
Prerequisites
- The version of the self-managed SQL Server database is supported by DTS. For more information, see Overview of data migration scenarios.
- The destination ApsaraDB RDS for SQL Server instance is created. For more information, see Create an ApsaraDB RDS for SQL Server instance.
- The available storage space of the ApsaraDB RDS for SQL Server instance is larger than the total size of the data in the self-managed SQL Server database.
- If the source database meets one of the following conditions, we recommend that you migrate data by using the backup feature of ApsaraDB RDS for SQL Server. For more information, see Migrate data from a self-managed database to ApsaraDB RDS for SQL Server.
The source instance contains more than 10 databases.
A single database of the source instance backs up its logs at an interval of less than 1 hour.
A single database of the source instance executes more than 100 DDL statements each hour.
Logs are written at a rate of 20 MB/s for a single database of the source instance.
The change data capture (CDC) feature needs to be enabled for more than 1,000 tables in the source ApsaraDB RDS for SQL Server instance.
The logs of a database in the source ApsaraDB RDS for SQL Server instance involve heap tables, tables without primary keys, compressed tables, or tables with computed columns. You can execute the following SQL statements to check whether the source database contains these tables.
Execute the following SQL statement to check for heap tables:
SELECT s.name AS schema_name, t.name AS table_name FROM sys.schemas s INNER JOIN sys.tables t ON s.schema_id = t.schema_id AND t.type = 'U' AND s.name NOT IN ('cdc', 'sys') AND t.name NOT IN ('systranschemas') AND t.object_id IN (SELECT object_id FROM sys.indexes WHERE index_id = 0);
Execute the following SQL statement to check for tables without primary keys:
SELECT s.name AS schema_name, t.name AS table_name FROM sys.schemas s INNER JOIN sys.tables t ON s.schema_id = t.schema_id AND t.type = 'U' AND s.name NOT IN ('cdc', 'sys') AND t.name NOT IN ('systranschemas') AND t.object_id NOT IN (SELECT parent_object_id FROM sys.objects WHERE type = 'PK');
Execute the following SQL statement to check for primary key columns that are not contained in clustered index columns:
SELECT s.name AS schema_name, t.name AS table_name FROM sys.schemas s INNER JOIN sys.tables t ON s.schema_id= t.schema_id WHERE t.type= 'U' AND s.name NOT IN('cdc', 'sys') AND t.name NOT IN('systranschemas') AND t.object_id IN (SELECT pk_columns.object_id AS object_id FROM (select sic.object_id object_id, sic.column_id FROM sys.index_columns sic, sys.indexes sis WHERE sic.object_id= sis.object_id AND sic.index_id= sis.index_id AND sis.is_primary_key= 'true') pk_columns LEFT JOIN (SELECT sic.object_id object_id, sic.column_id FROM sys.index_columns sic, sys.indexes sis WHERE sic.object_id= sis.object_id AND sic.index_id= sis.index_id AND sis.index_id= 1) cluster_colums ON pk_columns.object_id= cluster_colums.object_id WHERE pk_columns.column_id != cluster_colums.column_id);
Execute the following SQL statement to check for compressed tables:
SELECT s.name AS schema_name, t.name AS table_name FROM sys.objects t, sys.schemas s, sys.partitions p WHERE s.schema_id = t.schema_id AND t.type = 'U' AND s.name NOT IN ('cdc', 'sys') AND t.name NOT IN ('systranschemas') AND t.object_id = p.object_id AND p.data_compression != 0;
Execute the following SQL statement to check for tables with computed columns:
SELECT s.name AS schema_name, t.name AS table_name FROM sys.schemas s INNER JOIN sys.tables t ON s.schema_id = t.schema_id AND t.type = 'U' AND s.name NOT IN ('cdc', 'sys') AND t.name NOT IN ('systranschemas') AND t.object_id IN (SELECT object_id FROM sys.columns WHERE is_computed = 1);
Limits
Category | Description |
Limits on the source database |
|
Other limits |
|
Special cases | If the destination instance is an ApsaraDB RDS for SQL Server instance, take note of the following limits: DTS automatically creates a destination database in the ApsaraDB RDS for SQL Server instance. However, if the name of the database to be migrated does not conform to the naming conventions of ApsaraDB RDS, you must manually create a database in the destination ApsaraDB RDS for SQL Server instance before you configure the data migration task. For more information, see Create a database. |
Billing
Migration type | Instance configuration fee | Internet traffic fee |
Schema migration and full data migration | Free of charge. | Charged only when data is migrated from Alibaba Cloud over the Internet. For more information, see Billing overview. |
Incremental data migration | Charged. For more information, see Billing overview. |
Migration types
- Schema migration
DTS migrates the schemas of objects from the source database to the destination database.
- DTS supports schema migration for the following types of objects: table, view, trigger, synonym, SQL stored procedure, SQL function, plan guide, user-defined type, rule, default, and sequence.
- DTS does not migrate the schemas of 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 data migration
DTS migrates the existing data of objects from the source database to the destination database.
Incremental data migration
After full data migration is complete, DTS migrates incremental data from the source database to the destination database. Incremental data migration allows data to be migrated smoothly without interrupting the services of self-managed applications during data migration.
SQL operations that can be incrementally migrated
Operation type | SQL statement |
DML | INSERT, UPDATE, and DELETE Note If an UPDATE operation updates only the large fields, DTS does not migrate the operation. |
DDL |
Note
|
Permissions required for database accounts
Database | Schema migration | Full data migration | Incremental data migration |
Self-managed SQL Server database | SELECT permission | SELECT permission | sysadmin |
ApsaraDB RDS for SQL Server instance | Read and write permissions |
For more information about how to create a database account and grant permissions to the database account, see the following topics:
- Self-managed SQL Server database: CREATE USER
- ApsaraDB RDS for SQL Server instance: Create an account and Modify the permissions of an account
Data migration process
To prevent data migration failures caused by dependencies among objects, DTS migrates the schemas and data from the source SQL Server database in the following order:- Migrate the schemas of tables, views, synonyms, user-defined types, rules, defaults, and plan guides.
- Perform full data migration.
- Migrate the schemas of SQL stored procedures, SQL functions, triggers, and foreign keys.
- Perform incremental data migration.
Preparations
- Execute the following statements on the self-managed SQL Server database to change the recovery model to full.
Parameter:use master; GO ALTER DATABASE <database_name> SET RECOVERY FULL WITH ROLLBACK IMMEDIATE; GO
<database_name>: the name of the source database.
Example:use master; GO ALTER DATABASE mytestdata SET RECOVERY FULL WITH ROLLBACK IMMEDIATE; GO
- Execute the following statement to create a logical backup for the source database. Skip this step if you have already created a logical backup.
Parameter:BACKUP DATABASE <database_name> TO DISK='<physical_backup_device_name>'; GO
- <database_name>: the name of the source database.
- <physical_backup_device_name>: the storage path and file name of the backup file.
BACKUP DATABASE mytestdata TO DISK='D:\backup\dbdata.bak'; GO
- Execute the following statement to back up the log entries of the source database:
Parameter:BACKUP LOG <database_name> to DISK='<physical_backup_device_name>' WITH init; GO
- <database_name>: the name of the source database.
- <physical_backup_device_name>: the storage path and file name of the backup file.
BACKUP LOG mytestdata TO DISK='D:\backup\dblog.bak' WITH init; GO
Procedure
- Go to the Data Migration Tasks page.
- Log on to the Data Management (DMS) console.
- In the top navigation bar, click DTS.
- In the left-side navigation pane, choose .
Note- Operations may vary based on the mode and layout of the DMS console. For more information, see Simple mode and Customize the layout and style of the DMS console.
- You can also go to the Data Migration Tasks page of the new DTS console.
- From the drop-down list next to Data Migration Tasks, select the region in which the data migration instance resides. Note If you use the new DTS console, you must select the region in which the data migration instance resides in the upper-left corner.
- Click Create Task. In the Create Task wizard, configure the source and destination databases.Warning
After you configure the source and destination databases, we recommend that you read the limits that are displayed in the upper part of the page. Otherwise, the task may fail or data inconsistency may occur.
Section Parameter Description N/A Task Name The name of the task. DTS automatically assigns a name to the task. We recommend that you specify a descriptive name that makes it easy to identify the task. You do not need to specify a unique task name.
Source Database Select an existing DMS database instance The database instance that you want to use. You can choose whether to select an existing instance based on your business requirements.
If you select an existing instance, DTS automatically populates the parameters for the database.
If you do not select an existing instance, you must manually configure parameters for the database.
Database Type The type of the source database. Select SQL Server. Access Method The access method of the source database. Select Public IP Address. Note If your source database is a self-managed database, you must deploy the network environment for the database. For more information, see Preparation overview.Instance Region The region in which the self-managed SQL Server database resides. Hostname or IP Address The endpoint that is used to connect to the self-managed SQL Server database. In this example, a public IP address is used. Port Number The service port number of the self-managed SQL Server database. The default port number is 1433. Database Account The database account that is used to log on to the self-managed SQL Server database. For more information about the permissions that are required for the account, see the Permissions required for database accounts section of this topic. Database Password The password of the database account.
Destination Database Select an existing DMS database instance The database instance that you want to use. You can choose whether to select an existing instance based on your business requirements.
If you select an existing instance, DTS automatically populates the parameters for the database.
If you do not select an existing instance, you must manually configure parameters for the database.
Database Type The type of the destination database. Select SQL Server. Access Method The access method of the destination database. Select Alibaba Cloud Instance. Instance Region The region in which the destination ApsaraDB RDS for SQL Server instance resides. Instance ID The ID of the destination ApsaraDB RDS for SQL Server instance. Database Account The database account of the destination ApsaraDB RDS for SQL Server instance. For more information about the permissions that are required for the account, see the Permissions required for database accounts section of this topic. Database Password The password of the database account.
If an IP address whitelist is configured for your self-managed database, add the CIDR blocks of DTS servers to the IP address whitelist. Then, click Test Connectivity and Proceed.
WarningIf the public CIDR blocks of DTS servers are automatically or manually added to the IP address whitelist of a database instance or to the security group rules of an ECS instance, security risks may arise. Therefore, before you use DTS to migrate data, you must understand and acknowledge the potential risks and take preventive measures, including but not limited to the following measures: enhancing the security of your account and password, limiting the ports that are exposed, authenticating API calls, regularly checking the IP address whitelist or ECS security group rules and forbidding unauthorized CIDR blocks, and connecting the database to DTS by using Express Connect, VPN Gateway, or Smart Access Gateway.
- Configure the objects to be migrated and advanced settings.
Parameter Description Migration Types To perform only full data migration, select Schema Migration and Full Data Migration.
To ensure service continuity during data migration, select Schema Migration, Full Data Migration, and Incremental Data Migration.
NoteIf you do not select Incremental Data Migration, we recommend that you do not write data to the source database during data migration. This ensures data consistency between the source and destination databases.
Processing Mode of Conflicting Tables Precheck and Report Errors: checks whether the destination database contains tables that have the same names as tables in the source database. If the source and destination databases do not contain tables that have identical table names, the precheck is passed. Otherwise, an error is returned during the precheck and the data migration task cannot be started.
NoteYou can use the object name mapping feature to rename the tables that are migrated to the destination database. You can use this feature if the source and destination databases contain tables that have identical table names and the tables in the destination database cannot be deleted or renamed. For more information, see Map object names.
Ignore Errors and Proceed: skips the precheck for identical table names in the source and destination databases.
WarningIf you select Ignore Errors and Proceed, data inconsistency may occur and your business may be exposed to the following potential risks:
If the source and destination databases have the same schemas, DTS does not migrate data records that have the same primary key values as data records in the destination database.
If the source and destination databases have different schemas, only specific columns are migrated or the data migration task fails. Proceed with caution.
SQL Server Incremental Synchronization Mode Log-based Parsing for Non-heap Tables and CDC-based Incremental Synchronization for Heap Tables:
Benefits:
Supports heap tables, tables without primary keys, compressed tables, and tables with computed columns.
Provides higher stability and a variety of complete DDL statements.
Limits:
DTS creates the trigger named dts_cdc_sync_ddl, the heartbeat table named dts_sync_progress, and the DDL storage table named dts_cdc_ddl_history in the source database, and enables change data capture (CDC) for the source database and specific tables.
You cannot execute the SELECT INTO statement on a table for which CDC is enabled in the source database. You cannot manually delete triggers that are created by DTS in the source database.
Incremental Synchronization Based on Logs of Source Database:
Benefits:
Does not modify the settings of the source database.
Limits:
Does not support heap tables, tables without primary keys, compressed tables, or tables with computed columns.
Source Objects Select one or more objects from the Source Objects section and click the
icon to add the objects to the Selected Objects section.
NoteYou can select columns, tables, or schemas as the objects to be migrated. If you select tables or columns as the objects to be migrated, DTS does not migrate other objects, such as views, triggers, or stored procedures, to the destination database.
Selected Objects - To rename an object that you want to migrate to the destination instance, right-click the object in the Selected Objects section. For more information, see Map the name of a single object.
- To rename multiple objects at a time, click Batch Edit in the upper-right corner of the Selected Objects section. For more information, see Map multiple object names at a time.
Note- If you use the object name mapping feature to rename an object, other objects that are dependent on the object may fail to be migrated.
- To specify WHERE conditions to filter data, right-click an object in the Selected Objects section. In the dialog box that appears, specify the conditions. For more information about how to specify the conditions, see Use SQL conditions to filter data.
- To select the SQL operations performed on a specific database or table, right-click an object in the Selected Objects section. In the dialog box that appears, select the SQL operations that you want to migrate. For more information, see the SQL operations that can be incrementally migrated section of this topic.
- Click Next: Advanced Settings to configure advanced settings.
Parameter Description Set Alerts Specifies whether to configure alerting for the data migration task. If the task fails or the migration latency exceeds the specified threshold, the alert contacts will receive notifications. Valid values:
No: does not configure alerting.
Yes: configures alerting. If you select Yes, you must also specify the alert threshold and alert contacts. For more information, see Configure monitoring and alerting.
Retry Time for Failed Connections The retry time range for failed connections. If the source or destination database fails to be connected after the data migration task is started, DTS immediately retries a connection within the time range. Valid values: 10 to 1440. Unit: minutes. Default value: 720. We recommend that you set the parameter to a value greater than 30. If DTS reconnects to the source and destination databases within the specified time range, DTS resumes the data migration task. Otherwise, the data migration task fails.Note- If you set different retry time ranges for multiple data migration tasks that have the same source or destination database, the shortest retry time range that is set takes precedence.
- When DTS retries a connection, you are charged for the DTS instance. We recommend that you specify the retry time range based on your business requirements. You can also release the DTS instance at your earliest opportunity after the source and destination instances are released.
The wait time before a retry when other issues occur in the source and destination databases. The retry time range for other issues. For example, if DDL or DML operations fail to be performed after the data migration task is started, DTS immediately retries the operations within the retry time range. Valid values: 1 to 1440. Unit: minutes. Default value: 10. We recommend that you set the parameter to a value greater than 10. If the failed operations are successfully performed within the specified retry time range, DTS resumes the data migration task. Otherwise, the data migration task fails.
ImportantThe value of the The wait time before a retry when other issues occur in the source and destination databases parameter must be smaller than the value of the Retry Time for Failed Connections parameter.
Configure ETL Specifies whether to configure the extract, transform, and load (ETL) feature. For more information, see What is ETL?. Valid values:- Yes: configures the ETL feature. You can enter data processing statements in the code editor. For more information, see Configure ETL in a data migration or data synchronization task.
- No: does not configure the ETL feature.
In the lower part of the page, click Next: Save Task Settings and Precheck.
You can move the pointer over Next: Save Task Settings and Precheck and click Preview OpenAPI parameters to view the parameters to be specified when you call the relevant API operation to configure the DTS task.
NoteBefore you can start the data migration task, DTS performs a precheck. You can start the data migration task only after the task passes the precheck.
If the task fails to pass the precheck, click View Details next to each failed item. After you troubleshoot the issues based on the error message, you can run a precheck again.
If an alert is triggered for an item during the precheck:
If the alert item cannot be ignored, click View Details next to the failed item and troubleshoot the issues. Then, run a precheck again.
If the alert item can be ignored, click Confirm Alert Details. In the View Details dialog box, click Ignore. In the message that appears, click OK. Then, click Precheck Again to run a precheck again. If you ignore the alert item, data inconsistency may occur and your business may be exposed to potential risks.
Wait until the success rate becomes 100%. Then, click Next: Purchase Instance.
On the Purchase Instance page, configure the Instance Class parameter for the data migration instance. The following table describes the parameters.
Section
Parameter
Description
New Instance Class
Resource Group
The resource group to which the data migration instance belongs. Default value: default resource group. For more information, see What is Resource Management?
Instance Class
DTS provides instance classes that vary in the migration speed. You can select an instance class based on your business scenario. For more information, see Specifications of data migration instances.
Read and agree to Data Transmission Service (Pay-as-you-go) Service Terms by selecting the check box.
Click Buy and Start to start the data migration task. You can view the progress of the task in the task list.