The data migration feature refers to data replication between different data sources. It is a short-term one-time task that migrates the entire database. After migration, cutover will be performed to continue the task in the new database. DTS supports non-stop data migration without locks to minimize the impact of database downtime on the business.
DTS supports migration of self-built, TencentDB, and third-party cloud source databases.
The following takes MySQL as an example to describe the data migration process:
It simply takes a few steps in DTS to set up data migration to Tencent Cloud without any complicated configuration. The migration process does not interrupt the service provided by your source database, thereby minimizing the impact of cloudification on your business.
DTS supports the following three migration types:
For more information on the source and target database types, versions, and migration types supported for data migration, see Databases Supported by Data Migration.
|Heterogeneous migration and migration from third-party cloud databases||Data migration between databases in different types is supported, such as migration from MySQL to TDSQL-C. Currently supported third-party cloud databases include Alibaba Cloud and AWS databases.||Databases Supported by Data Migration|
|Cross-account migration||Data migration between different Tencent Cloud accounts is supported.||Cross-Account TencentDB Instance Migration|
|Cross-version migration of most databases||The target database version should be equal to or later than the source database version; for example, data on v5.5.x can be migrated to v5.5.x, v5.6.x, or later. The last digit in the version number is the minor version number, which is not restricted.||Databases Supported by Data Migration|
|Migration of user information, views, and advanced objects||User information, views, stored procedures, functions, triggers, and events can be migrated.||-|
|Data consistency check||The data in the source and target databases can be checked for consistency.||Creating Data Consistency Check Task|
|Task progress visualization||Information such as migration steps and progress can be displayed.||Viewing Task|
|Metric monitoring and default alarm policy||Supported Events and Metrics|
|Migration without locks||Migration is implemented without locks, during which no global lock (the FTWRL lock) is added, and only tables without a primary key are locked.||-|
|Database/Table mapping||Databases/Tables migrated from the source database to the target database can be renamed.||Renaming Database/Table|
|Instance restart or upgrade||During incremental migration, the instances can be restarted or upgraded.||-|
|HA switch||HA switch from the source instance (with GTID enabled) to the target instance is supported.||-|
|No requirements for the super privileges||The operator does not need to have the super privileges of the source instance account (only for certain databases currently).||-|