This document describes how to use the data migration feature of DTS to migrate data from SQL Server to TencentDB for SQL Server.
- During full data migration, DTS consumes certain source database resources, which may increase the load and pressure of the source database. If your database configuration is low, we recommend you migrate the data during off-peak hours.
- Full migration is implemented with tables locked, causing write operations to be blocked for a few seconds.
- You have created a TencentDB for SQL Server instance.
- The source and target databases must meet the requirements for the migration feature and version as instructed in Databases Supported by Data Migration.
- You have completed all preparations.
- If the source database is not a TencentDB for SQL Server or TencentDB for SQL Server Basic Edition instance (such as a public network/CVM-based self-built instance or instance on another cloud), an account with the
sysadmin permission needs to be used for migration, and the
xp_cmdshell stored procedure must be able to run. If the source data is a TencentDB for SQL Server High-Availability Edition or Cluster Edition instance, there is no permission restriction.
- The migration account must be
- The service where the source database is located must open the file sharing port 445.
- The source database must be set to "full recovery mode", and we recommend you make a full backup before migration.
- The local disk space of the source database must be large enough, so that the remaining free space can fit the size of the database to be migrated.
- Only one migration task can be initiated at any time for the same source instance.
- Currently, cross-region migration is supported between the Chinese mainland and Hong Kong (China) but not between other regions.
- Only database-level migration is supported (i.e., all objects in the database must be migrated together), while single-table migration is not supported.
- Logins, job agents, triggers, and database links (link server) at the instance level cannot be migrated.
- Do not modify or delete user information (including username, password, and permissions) in the source and target databases and port numbers during migration; otherwise, the migration task will fail.
- Do not perform transaction log backup during incremental sync; otherwise, the transaction log will be truncated and become discontinuous.
- If you only perform full data migration, do not write new data into the source database during migration; otherwise, the data in the source and target databases will be inconsistent. In scenarios with data writes, to ensure the data consistency in real time, we recommend you select full + incremental data migration.
- For full + incremental data migration, after you click Complete and the task status becomes Completed, do not write new data to the source database. We recommend you stop writing for two minutes; otherwise, the data in the source and target databases may be inconsistent.
Supported SQL Operations
||Supported SQL Operations
||INSERT, UPDATE, DELETE, and REPLACE
||TABLE: CREATE TABLE, ALTER TABLE, DROP TABLE, TRUNCATE TABLE, and RENAME TABLE
VIEW: CREATE VIEW, ALTER VIEW, and DROP VIEW
INDEX: CREATE INDEX and DROP INDEX
DATABASE: CREATE DATABASE, ALTER DATABASE, and DROP DATABASE
The system will automatically check the following environment requirements before starting a migration task and report an error if a requirement is not met. If you can identify the failed check item, fix it as instructed in Requirements for Check Items; otherwise, wait for the system verification to complete and fix the problem according to the error message.
|Source database requirements
||The service where the source database resides must open the file sharing port 445.
The source and target databases can be connected.
The server where the source database resides must have enough outbound bandwidth; otherwise, the migration speed will be affected.
|Target database requirements
||Only migration from Basic Edition to High Availability Edition (including Dual-Server High Availability Edition and Cluster Edition) is supported, and the version number of the target database must be above that of the source database.
The target database cannot have the same name as the source database.
The disk space of the target database must be at least 1.5 times the size of the source database.
The target database cannot have access requests or active businesses; otherwise, migration will fail.
- Log in to the DTS console, select Data Migration on the left sidebar, and click Create Migration Task to enter the Create Migration Task page.
- On the Create Migration Task page, select the region of the target database and click Free Trial. Currently, the DTS data migration feature is free of charge.
- On the Set source and target databases page, configure the task, source database, and target database settings. After the source and target databases pass the connectivity test, click Create.
If the connectivity test fails, troubleshoot and fix the problem as prompted and as instructed in Troubleshooting Guide and try again.
|Setting Type||Configuration Item||Description|
||Set a meaningful name for easy task identification.|
- Immediate execution: the task will be started immediately after the task verification is passed.
- Scheduled execution: you need to configure a task execution time and the task will be started automatically then.
||Tags are used to manage resources by category in different dimensions. If the existing tags do not meet your requirements, go to the console to create more.|
|Source Database Settings
||Source Database Type||Select your source database type. In this document, select **SQL Server**.|
|Access Type||Select a type based on your scenario.
For a third-party cloud database, you can select **Public Network** generally or select **VPC Access**, **Direct Connect**, or **CCN** based on your actual network conditions. For the preparations for different access types, see Overview.
- Public Network: the source database can be accessed through a public IP.
- Self-Build on CVM: the source database is deployed in a CVM instance.
- Direct Connect: the source database can be interconnected with VPCs through Direct Connect.
- VPN Access: the source database can be interconnected with VPCs through VPN Connection.
- Database: the source database is a TencentDB database.
|Region||The region where the source database resides is the outbound region of the DTS service. Select a region nearest to your self-built database.|
|Host Address||IP address or domain name for accessing the source SQL Server database.|
|Port||Port for accessing the source SQL Server database.|
|Account||Account of the source SQL Server database, which must have the required permissions.|
|Password||Password of the source SQL Server database.|
|Target Database Settings
||Target Database Type||Select **SQL Server**.|
|Access Type||Select a type based on your scenario. In this document, select **Database**.|
|Region||Select the same region as in the source database settings.|
|Database Instance||Select the instance ID of the target database.|
|Account.||Account of the target database, which must have the required permissions.|
|Password||Password of the target database.|
- On the Set migration options and select migration objects page, configure the migration type and objects and click Save.
||Select a type based on your scenario.|
- Full migration:the entire database will be migrated.
- Full + incremental migration: the entire database and subsequent incremental data will be migrated. If there are data writes during migration, and you want to smoothly migrate the data in a non-stop manner, select this option.
||Only database-level migration is supported; that is, all objects in the specified database must be migrated together. Select the database to be migrated in **Source Database Object** and move it to the **Selected Object** box.|
- On the task verification page, verify the task. After the verification is passed, click Start Task.
If the verification failed, fix the problem as instructed in Fix for Verification Failure and initiate the verification task again.
- Failed: it indicates that a check item failed and the task is blocked. You need to fix the problem and run the verification task again.
- Alarm: it indicates that a check item doesn't completely meet the requirements, and the task can be continued, but the business will be affected. You need to assess whether to ignore the alarm or fix the problem and continue the task based on the alarm message.
- Return to the data migration task list, and you can see that the task has entered the Preparing status. After 1–2 minutes, the data migration task will be started.
- Select Full migration: once completed, the task will be stopped automatically.
- Select Full + Incremental migration: after full migration is completed, the migration task will automatically enter the incremental data sync stage, which will not stop automatically. You need to click Complete to manually stop the incremental data sync.
- Select an appropriate time to manually complete the incremental data sync and perform business switch.
- You can see that the migration task is in the incremental sync stage, and there is no latency. Stop writing the source database for several minutes.
- When the source-target database data gap is 0 MB, and the source-target database time lag is 0s, manually complete the incremental sync.
- (Optional) If you want to view, delete, or perform other operations on a task, click the task and select the target operation in the Operation column. For more information, see Task Management.
- After the migration task status becomes Task successful, you can formally cut over the business. For more information, see Cutover Description.