The legacy version of DTS implements incremental data sync through cloud native replication, which has a strong dependency on the kernel form of the source database and has many restrictions on the features; for example, it does not support advanced features such as table name mapping and many-to-one database sync.
The new version of DTS uses a new proprietary kernel and comprehensively improves the product features to provide more stable, available, flexible, and secure data transfer capabilities for better ease of use. Its capabilities are polished for data transfer, with advanced feature such as heterogeneous database migration and cross-account data migration.
The key features of the new and legacy versions of DTS are compared as follows:
Item | Legacy Version | New Version |
---|---|---|
Database type | ||
Cross-account migration | Not supported. | Supported. |
Supported data types | ||
Supported versions | It does not support cross-version migration. | It supports cross-version migration for most databases. For more information on the supported versions, see Databases Supported by Data Migration. |
Task progress visualization | Not supported. | Supported. |
Monitoring and alarming | ||
Enhanced operation experience | - | |
High availability (HA) | It has strict restrictions for HA switch. | |
Data verification | The operator must have the super privileges of the source instance account. | The operator does not need to have the super privileges of the source instance account (only for certain databases currently). |
The key features of the new and legacy versions of DTS are compared as follows:
Item | Legacy Version | New Version |
---|---|---|
Sync type | It supports one-way and one-to-one sync modes. | It supports two-way, ring, and many-to-one sync modes. |
Cross-account sync | It does not support cross-account sync. | It supports cross-account sync. |
Supported versions | It does not support cross-version sync. | It supports cross-version sync. For more information on the supported versions, see Databases Supported for Data Sync. |
Content conflict | It does not support content conflict check. | It provides table conflict check policies and supports renaming tables. |
Primary key conflict | It does not support primary key conflict policies. | It provides primary key conflict processing policies: |
Task progress visualization | Not supported. | Supported. |
Monitoring and alarming | ||
Enhanced operation experience | - | |
High availability (HA) | It has strict restrictions for HA switch. |
The key features of the new and legacy versions of DTS are compared as follows:
Item | Legacy Version | New Version |
---|---|---|
Database type | TencentDB for MySQL only. | TencentDB for MySQL, TencentDB for MariaDB, and TDSQL for MySQL. |
Subscribed data storage method | The data is stored on physical machines in master/slave mode. | The data is stored in the Kafka middleware, and partitioned storage of data in a single topic is supported (with partitioning strategy available), improving the consumption efficiency. |
Supported protocol | Proprietary protocol with SDK for Java only. | Kafka protocol with Kafka client SDKs for multiple programming languages. |
Monitoring and alarming | ||
Data channel | It allows creating only one data channel for a single instance. | It allows creating multiple data channels for a single instance, which can be consumed concurrently through a consumer group. |
Consumption method | It supports only serial processing. | It supports partitioned storage of data in a single topic for concurrent consumption of data in multiple partitions, improving the consumption efficiency. |
Was this page helpful?