You can use DTS to migrate data between homogeneous and heterogeneous data sources. Typical scenarios include data migration to Alibaba Cloud, data migration between instances within Alibaba Cloud, and database splitting and scale-out. This topic describes the database types, database versions, and migration types that are supported by data migration.
For more information about data migration in various scenarios, see Overview of data migration scenarios.
Migration types
| Migration type | Description |
|---|---|
| Schema migration |
DTS migrates the schemas of the required objects from the source database to the destination database. Tables, views, triggers, and stored procedures can be migrated. For schema migration between heterogeneous databases, DTS converts the schema syntax based on the syntax of the source and destination databases. For example, it converts the NUMBER data type in Oracle databases to the DECIMAL data type in MySQL databases. |
| Full data migration | DTS migrates historical data of the required objects from the source database to the
destination database. If you select only schema migration and full data migration,
incremental data that is generated in the source database will not be migrated to
the destination database.
Note To ensure data consistency, do not write data into the source database during full
data migration. To migrate data with minimal downtime, you must select schema migration, full data migration, and incremental data migration when configuring a data migration task.
|
| Incremental data migration | DTS retrieves static snapshots that are used for full data migration from the source
database and migrates the snapshot data to the destination database. Then, DTS synchronizes
incremental data that is generated in the source database to the destination database
in real time.
Note During incremental data migration, data between the source and destination databases
is synchronized in real time. The migration task does not automatically stop. You
must manually stop the migration task.
|
Database and migration types
A user-created source or destination database, such as a MySQL, SQL Server, or Oracle database, can be one of the following types:
- User-Created Database with Public IP Address
- Database without public IP:Port (Accessed through database gateway)
- Self built database accessed through Cloud Enterprise Network(CEN)
- User-Created Database in ECS Instance
- User-Created Database Connected Over Express Connect, VPN Gateway, or Smart Access Gateway
| Source database | Destination database | Migration type |
|---|---|---|
|
User-created MySQL database 5.1, 5.5, 5.6, 5.7, and 8.0 |
|
|
ApsaraDB RDS for MySQL All versions |
|
|
|
Apsara PolarDB for MySQL All versions |
|
|
|
DRDS MySQL 5.x Note The database in DRDS instance are created based on ApsaraDB RDS for MySQL instances
(MySQL 5.x) that you purchased. DTS does not support databases that are created based
on ApsaraDB RDS for MySQL instances (MySQL 8.0) or ApsaraDB PolarDB for MySQL clusters.
|
|
|
|
HybridDB for MySQL (Previous name: PetaData) All versions |
|
|
|
AnalyticDB for MySQL 2.0 and 3.0 |
|
|
|
User-created PostgreSQL database 9.4, 9.5, 9.6, 10.x, 11.x, and 12 |
|
|
|
User-created Oracle database (RAC and non-RAC architecture) 9i, 10g, 11g, 12c, 18c, and 19c |
|
|
|
ApsaraDB for MariaDB TX 10.3 |
ApsaraDB for MariaDB TX 10.3 |
|
|
ApsaraDB RDS for MySQL All versions |
|
|
|
User-created MySQL database 5.1, 5.5, 5.6, 5.7, and 8.0 |
|
|
|
Apsara PolarDB for MySQL All versions |
Apsara PolarDB for MySQL All versions |
|
|
User-created MySQL database 5.1, 5.5, 5.6, 5.7, and 8.0 |
|
|
|
ApsaraDB RDS for MySQL All versions |
|
|
|
AnalyticDB for MySQL 2.0 and 3.0 |
|
|
|
User-created SQL Server database 2005, 2008, 2008 R2, 2012, 2014, 2016, and 2017 Note SQL Server Cluster and SQL Server AlwaysOn High Availability Group are not supported.
|
|
|
ApsaraDB RDS for SQL Server 2008, 2008 R2, 2012, 2014, 2016, and 2017 |
|
|
|
User-created Oracle database (RAC and non-RAC architecture) 9i, 10g, 11g, 12c, 18c, and 19c |
User-created Oracle database (RAC and non-RAC architecture) 9i, 10g, 11g, 12c, 18c, and 19c |
|
|
PolarDB database compatible with Oracle All versions |
|
|
|
ApsaraDB RDS for PPAS 9.3 and 10 |
|
|
|
User-created MySQL database 5.1, 5.5, 5.6, 5.7, and 8.0 |
|
|
|
ApsaraDB RDS for MySQL All versions |
|
|
|
DRDS MySQL 5.x Note The database in DRDS instance are created based on ApsaraDB RDS for MySQL instances
(MySQL 5.x) that you purchased. DTS does not support databases that are created based
on ApsaraDB RDS for MySQL instances (MySQL 8.0) or ApsaraDB PolarDB for MySQL clusters.
|
|
|
|
AnalyticDB for MySQL 2.0 and 3.0 |
|
|
|
User-created PostgreSQL database 9.4, 9.5, 9.6, 10.x, 11.x, and 12 |
|
|
|
|
Note MongoDB is a NoSQL database that does not require schema migration.
|
|
User-created Redis database (single-host architecture) 2.8, 3.0, 3.2, 4.0, and 5.0 |
User-created Redis database (single-host and cluster architecture) 2.8, 3.0, 3.2, 4.0, and 5.0 |
Note Redis is a NoSQL database that does not require schema migration.
|
|
ApsaraDB for Redis instance (single-host and cluster architecture) Community versions 4.0 and 5.0 |
|
|
| User-created TiDB database |
User-created MySQL database 5.1, 5.5, 5.6, 5.7, and 8.0 |
|
|
ApsaraDB RDS for MySQL All versions |
|
|
|
Apsara PolarDB for MySQL All versions |
|
|
|
User-created Db2 database 9.7 and 10.5 |
User-created MySQL database 5.1, 5.5, 5.6, 5.7, and 8.0 |
|