DTS provides features such as data migration, data synchronization, and change tracking. Before you use these features, you must prepare the environments that are required for your source or destination database.

Note For more information about the preparations that are required for DTS features, see the following topics:

You can use a user-created database as the source or destination database. The following table lists the preparations in different scenarios.

Table 1. Preparation overview
Scenario Preparation
  • The type of the source or destination database for data migration is User-Created Database with Public IP Address.
  • The type of the source database for change tracking is User-Created Database with Public IP Address.
Note The type of the source or destination database for data synchronization cannot be User-Created Database with Public IP Address.
  • The type of the source or destination database for data migration or synchronization is Database without public IP:Port (Accessed through database gateway).
  • The type of the source database for change tracking is Database without public IP:Port (Accessed through database gateway).
The type of the source or destination database for data migration or synchronization is Self built database accessed through Cloud Enterprise Network(CEN).
  • The type of the source or destination database for data migration or synchronization is User-Created Database in ECS Instance.
  • The type of the source database for change tracking is User-Created Database in ECS Instance.
Create an account for a user-created MySQL database and configure binary logging
  • The type of the source or destination database for data migration or synchronization is User-Created Database Connected over Express Connect, VPN Gateway, or Smart Access Gateway.
  • The type of the source database for change tracking is User-Created Database Connected over Express Connect, VPN Gateway, or Smart Access Gateway.
The destination ApsaraDB RDS for MySQL instance has low specifications (with less than two CPU cores) and you need to migrate a large volume of data. Disable slow query log to improve migration performance