The data migration feature refers to data replication between different data sources. DTS supports non-stop data migration to minimize the impact of database downtime on the business. It is applicable to diverse business scenarios, including data migration to Tencent Cloud, cross-TencentDB instance data migration, and data migration from third-party cloud databases to TencentDB.
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 for 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 for Data Migration|
|Cross-version migration of most databases||The target database version should be equal to or above the source database version; for example, data on v5.5.x can be migrated to v5.5.x, v5.6.x, or above. The last digit in the version number is the minor version number, which is not restricted.||Databases Supported for Data Migration|
|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||Tables with a primary key or non-null unique key can be migrated without being locked.||-|
|Table mapping||Tables migrated from the source database to the target database can be renamed.||Table Mapping|
|Instance restart or upgrade||During incremental data migration, the instances can be restarted or upgraded.||-|
|HA switch||HA switch from the source database (with GTID enabled) to the target database is supported.||-|
|No requirements for the super privileges||The operator does not need to have the super privileges of the source database account (only for certain databases currently).||-|