- Release Notes
- Product Introduction
- Purchase Guide
- Quick Start
- Preparations
- NewDTS
- Databases Supported by Data Migration
- Migration from MySQL to TencentDB for MySQL
- Migration from MariaDB or Percona to TencentDB for MySQL
- Migration from MySQL to TDSQL for MySQL
- Migration from MySQL to TencentDB for MariaDB (Percona)
- Migration from PostgreSQL to TencentDB for PostgreSQL
- Migration from MongoDB to TencentDB for MongoDB
- Migration from SQL Server to TencentDB for SQL Server
- Offline Migration of MySQL Data
- Task Management
- Creating Data Consistency Check Task
- Data Sync
- Data Subscription Kafka Edition
- Data Subscription (Legacy)
- Data Migration (Legacy)
- MySQL Data Migration
- Migrating from Public Network-based External MySQL to TencentDB for MySQL
- Migrating from External MySQL Based on Direct Connect/VPN Gateway to TencentDB for MySQL
- Migrating from CCN-based Self-created MySQL to TencentDB for MySQL
- Migrating from AWS RDS for MySQL to TencentDB for MySQL
- Migrating from AWS Aurora for MySQL to TencentDB for MySQL
- Migrating from Alibaba Cloud RDS for MySQL to TencentDB for MySQL
- Migrating from Alibaba Cloud PolarDB for MySQL to TencentDB for MySQL
- Migration between TencentDB for MySQL Instances
- Online Import of MySQL Data
- Offline Migration of MySQL Data
- Migrating from Alibaba Cloud ApsaraDB for RDS to TencentDB
- Redis Data Migration
- MongoDB Data Migration
- MariaDB Data Migration
- MySQL Data Migration
- Fix for Verification Failure
- Check Item Overview
- Database Connection Check
- Peripheral Check
- Version Check
- Source Database Permission Check
- Partial Database Parameter Check
- Target Database Content Conflict Check
- Target Database Space Check
- Binlog Parameter Check
- Foreign Key Dependency Check
- View Check
- Warning Item Check
- RDS Check
- DLL Ring Sync Check for Single Database/Table Object
- DLL Sync Conflict Check for Single Database/Table Object in the Same Target
- Parameter Configuration Conflict Check
- Incremental Migration Precondition Check
- Extension/Plugin Compatibility Check
- Account Conflict Check
- Oplog Check
- Source Database Balancer Check
- Source Database Node Role Check
- ShardKey Check
- Target Database Load Check
- Local Disk Space Check
- Source Database Existence Check
- Target Database Existence Check
- Migration Network Check
- Cutover Description
- Connection to Cloud Monitor
- Best Practices
- API Documentation
- SDK Documentation
- FAQs
- Release Notes
- Product Introduction
- Purchase Guide
- Quick Start
- Preparations
- NewDTS
- Databases Supported by Data Migration
- Migration from MySQL to TencentDB for MySQL
- Migration from MariaDB or Percona to TencentDB for MySQL
- Migration from MySQL to TDSQL for MySQL
- Migration from MySQL to TencentDB for MariaDB (Percona)
- Migration from PostgreSQL to TencentDB for PostgreSQL
- Migration from MongoDB to TencentDB for MongoDB
- Migration from SQL Server to TencentDB for SQL Server
- Offline Migration of MySQL Data
- Task Management
- Creating Data Consistency Check Task
- Data Sync
- Data Subscription Kafka Edition
- Data Subscription (Legacy)
- Data Migration (Legacy)
- MySQL Data Migration
- Migrating from Public Network-based External MySQL to TencentDB for MySQL
- Migrating from External MySQL Based on Direct Connect/VPN Gateway to TencentDB for MySQL
- Migrating from CCN-based Self-created MySQL to TencentDB for MySQL
- Migrating from AWS RDS for MySQL to TencentDB for MySQL
- Migrating from AWS Aurora for MySQL to TencentDB for MySQL
- Migrating from Alibaba Cloud RDS for MySQL to TencentDB for MySQL
- Migrating from Alibaba Cloud PolarDB for MySQL to TencentDB for MySQL
- Migration between TencentDB for MySQL Instances
- Online Import of MySQL Data
- Offline Migration of MySQL Data
- Migrating from Alibaba Cloud ApsaraDB for RDS to TencentDB
- Redis Data Migration
- MongoDB Data Migration
- MariaDB Data Migration
- MySQL Data Migration
- Fix for Verification Failure
- Check Item Overview
- Database Connection Check
- Peripheral Check
- Version Check
- Source Database Permission Check
- Partial Database Parameter Check
- Target Database Content Conflict Check
- Target Database Space Check
- Binlog Parameter Check
- Foreign Key Dependency Check
- View Check
- Warning Item Check
- RDS Check
- DLL Ring Sync Check for Single Database/Table Object
- DLL Sync Conflict Check for Single Database/Table Object in the Same Target
- Parameter Configuration Conflict Check
- Incremental Migration Precondition Check
- Extension/Plugin Compatibility Check
- Account Conflict Check
- Oplog Check
- Source Database Balancer Check
- Source Database Node Role Check
- ShardKey Check
- Target Database Load Check
- Local Disk Space Check
- Source Database Existence Check
- Target Database Existence Check
- Migration Network Check
- Cutover Description
- Connection to Cloud Monitor
- Best Practices
- API Documentation
- SDK Documentation
- FAQs
DTS supports migration of self-built, TencentDB, and third-party cloud databases. Below are the specific network connection methods:
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.
CCN: the source database can be interconnected with VPCs through CCN.
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.
Databases that support migration are as detailed below:
| Data Flow Direction | Migration Direction | Source Database Type and Version | Target Database Type and Version | Migration Type | Cross-version Migration |
|---|---|---|---|---|---|
| MySQL > MySQL | To Tencent Cloud | TencentDB for MySQL 5.5, 5.6, 5.7, and 8.0 | Supported | ||
| MariaDB > MySQL | To Tencent Cloud | TencentDB for MySQL 5.5, 5.6, 5.7, and 8.0 | Yes | ||
| MariaDB (Percona) > MySQL | To Tencent Cloud | TencentDB for MySQL 5.5, 5.6, 5.7, and 8.0 | Supported | ||
| MySQL > TDSQL-C | To Tencent Cloud | TDSQL-C 5.6 and 5.7 | - | ||
| MySQL > TDSQL for MySQL | To Tencent Cloud | TDSQL for MySQL 5.7 | - | ||
| MySQL > MariaDB (Percona) | To Tencent Cloud | TencentDB for MariaDB (Percona) 5.7 | - | ||
| MariaDB > MariaDB | To Tencent Cloud | TencentDB for MariaDB 10.1.9 | - | ||
| MariaDB (Percona) > MariaDB (Percona) | To Tencent Cloud | TencentDB for MariaDB (Percona) 5.7 | - | ||
| PostgreSQL > PostgreSQL | To Tencent Cloud | TencentDB for PostgreSQL 9.3, 9.5, 9.6, 10, 11, and 12 | Supported. Migration from v13 to v12 is also supported | ||
| PostgreSQL > PostgreSQL | To Tencent Cloud | PostgreSQL 10, 11, and 12 | TencentDB for PostgreSQL 10, 11, and 12 | Full + incremental migration | Not supported |
| MongoDB > MongoDB | To Tencent Cloud | TencentDB for MongoDB 3.0, 3.2, 3.4, 3.6, 4.0, and 4.2 | Supported | ||
| SQL Server > SQL Server | To Tencent Cloud | TencentDB for SQL Server 2008 R2, 2012, 2014, 2016, 2017, and 2019 | Supported |
Note：
- "To Tencent Cloud" refers to scenarios where the target database is a TencentDB database product.
- MySQL/TDSQL for MySQL/MariaDB: the target database version must be greater than or equal to the source database version. The versions are differentiated by the major version number; for example, v5.6.x can be migrated to v5.6.x, v5.7.x, and above.
- PostgreSQL: in full migration, the target database version must be greater than or equal to the source database version; in incremental migration, migration between versions above v10.x is supported.
- MongoDB: migration between different versions is supported.
- SQL Server: 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.
Yes
No
Was this page helpful?