This topic describes how to migrate full data from an Amazon RDS for SQL Server database to an ApsaraDB RDS for SQL Server database by using Data Transmission Service (DTS).

Prerequisites

  • The Public accessibility option of Amazon RDS for SQL Server is set to Yes. This ensures that DTS can access Amazon RDS for SQL Server over the Internet.
  • The database version of Amazon RDS for SQL Server is 2005, 2008, 2008 R2, 2012, 2014, or 2016.
  • An ApsaraDB RDS for SQL Server instance is created. For more information, see Create an RDS for SQL Server instance.
  • The available storage space of the destination ApsaraDB RDS for SQL Server database is larger than the total space of the data in the Amazon RDS for SQL Server database.

Notes

  • DTS uses read and write resources of the source and destination databases during full data migration. This may increase the database load. If the database performance is unfavorable, the specification is low, or the data volume is large, database services may become unavailable. For example, DTS occupies a large amount of read and write resources in the following cases: a large number of slow SQL queries are performed on the source database, the tables have no primary keys, or a deadlock occurs in the destination database. Before you migrate data, evaluate the performance of the source and destination databases. We recommend that you migrate data during off-peak hours. For example, you can migrate data when the CPU usage of the source and destination databases is less than 30%.
  • Amazon RDS for SQL Server does not support incremental data migration because the sysadmin server-level role is not available in Amazon RDS.
  • The source database must have PRIMARY KEY or UNIQUE constraints and all fields must be unique. Otherwise, duplicate data may exist in the destination database.
  • If the name of the source database is invalid, you must create a database in the ApsaraDB RDS for SQL Server instance before configuring a data migration task.
    Note For more information about how to create a database and the database naming conventions, see Create databases and accounts.
  • DTS automatically resumes a failed data migration task. Before switching your workloads to the destination instance, you must stop or release the data migration task. Otherwise, the data from the source database will overwrite the data in the destination instance after the task is resumed.

Migration types

  • Schema migration

    DTS migrates the schemas of the required objects to the destination instance. 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, and default.

  • Full data migration
    DTS migrates historical data of the required objects from the source Amazon RDS for SQL Server database to the destination ApsaraDB RDS for SQL Server database.
    Note Data of the sql_variant type cannot be migrated.

Billing

Migration type Instance configurations Internet traffic
Schema migration or full data migration Free of charge Migrating data from Alibaba Cloud over the Internet incurs fees. For more information, see Pricing.

Permissions required for database accounts

Database Schema migration Full data migration
Amazon RDS for SQL Server database The permission to perform SELECT operations The permission to perform SELECT operations
ApsaraDB RDS for SQL Server database The read/write permissions The read/write permissions

For more information about how to create and authorize a database account, see the following topics:

Full data migration

To avoid data migration failures caused by dependencies between objects, DTS migrates the schemas and data of the source SQL Server database in the following order:

  1. Migrate the schemas of tables, views, synonyms, user-defined types, rules, defaults, and plan guides.
  2. Perform full data migration.
  3. Migrate the schemas of SQL stored procedures, SQL functions, triggers, and foreign keys.

Preparations before data migration

  1. Log on to the Amazon RDS Management Console.
  2. Go to the Basic information page of the source Amazon RDS for SQL Server instance.
  3. In the Security group rules section, click the name of the security group corresponding to the existing inbound rule.
    Security group rules
  4. On the Security groups page, click the Inbound tab in the Security group section. On the Inbound tab, click Edit to add CIDR blocks of DTS servers in the corresponding region to the inbound rule. For more information, see Add the CIDR blocks of DTS servers to the security settings of on-premises databases.
    Edit inbound rules
    Note
    • You only need to add the CIDR blocks of DTS servers that are located in the same region as the destination database. For example, the source database is located in Singapore and the destination database is located in Hangzhou. You only need to add the CIDR blocks of DTS servers that are located in the China (Hangzhou) region.
    • You can add all the required CIDR blocks to the inbound rule at one time.

Procedure

  1. Log on to the DTS console.
  2. In the left-side navigation pane, click Data Migration.
  3. At the top of the Migration Tasks page, select the region where the destination cluster resides.
    Select a region
  4. In the upper-right corner of the page, click Create Migration Task.
  5. Configure the information about the source and destination databases for the data migration task.
    Configure source and destination databases
    Section Parameter Description
    N/A Task Name DTS automatically generates a task name. We recommend that you use an informative name for easy identification. You do not need to use a unique task name.
    Source Database Instance Type Select User-Created Database with Public IP Address.
    Instance Region If the instance type is set to User-Created Database with Public IP Address, you do not need to specify the instance region.
    Database Type Select SQL Server.
    Hostname or IP Address Enter the endpoint that is used to connect to the Amazon RDS for SQL Server database.
    Note You can obtain the endpoint on the Basic information page of the source Amazon RDS for SQL Server instance.
    Endpoint
    Port Number Enter the service port number of the Amazon RDS for SQL Server database. The default port number is 1433.
    Database Account Enter the account for the Amazon RDS for SQL Server database. For more information about permissions required for the account, see Permissions required for database accounts.
    Database Password Enter the password for the database account.
    Note After you specify the source database parameters, click Test Connectivity next to Database Password to verify whether the specified parameters are valid. If the specified parameters are valid, the Passed message appears. If the Failed message appears, click Check next to Failed. Modify the source database parameters based on the check results.
    Destination Database Instance Type Select RDS Instance.
    Instance Region Select the region where the ApsaraDB RDS for SQL Server instance resides.
    RDS Instance ID Select the ID of the ApsaraDB RDS for SQL Server instance.
    Database Account Enter the database account of the ApsaraDB RDS for SQL Server instance. For more information about permissions required for the account, see Permissions required for database accounts.
    Database Password Enter the password for the database account.
    Note After you specify the destination database parameters, click Test Connectivity next to Database Password to verify whether the parameters are valid. If the specified parameters are valid, the Passed message appears. If the Failed message appears, click Check next to Failed. Modify the destination database parameters based on the check results.
  6. In the lower-right corner of the page, click Set Whitelist and Next.
    Note The CIDR blocks of DTS servers are automatically added to the whitelist of the ApsaraDB for RDS instance. This ensures that DTS servers can connect to the ApsaraDB for RDS instance.
  7. Select the migration types and objects to be migrated.
    Select the migration types and objects to be migrated
    Parameter Description
    Migration types Select Schema Migration and Full Data Migration.
    Note
    • Amazon RDS for SQL Server does not support incremental data migration because the sysadmin server-level role is not available in Amazon RDS.
    • To ensure data consistency, do not write new data into Amazon RDS for SQL Server during full data migration.
    Objects to be migrated

    In the Available section, select the objects to be migrated and click the Right arrow icon to add the objects to the Selected section.

    Note
    • You can select databases, tables, or columns as the objects to be migrated.
    • After an object is migrated to the destination instance, the name of the object remains unchanged. If you want an object to have a different name after the object is migrated to the ApsaraDB RDS for SQL Server instance, you can use the object name mapping feature provided by DTS. For more information about how to use this feature, see Object name mapping.
    • If you use the object name mapping feature on an object, other objects that are dependent on the object may fail to be migrated.
  8. In the lower-right corner of the page, click Precheck.
    Notice
    • Before you can start the data migration task, a precheck is performed. A data migration task can be started only if it passes the precheck.
    • If the task fails to pass the precheck, click the Info icon icon next to each failed item to view details. Troubleshoot the issues based on the causes and perform a precheck again.
  9. After the task passes the precheck, click Next.
  10. In the Confirm Settings dialog box, specify the Channel Specification parameter and select Data Transmission Service (Pay-As-You-Go) Service Terms.
  11. Click Buy and Start to start the data migration task.
    Note Do not manually stop a migration task. Otherwise, data migrated to the destination database will be incomplete. Wait until the data migration task stops when it is complete.
    Full data migration
  12. Switch your workloads to the ApsaraDB RDS for SQL Server instance.