This topic describes how to configure a data integration task between ApsaraDB RDS for MySQL instances.
Prerequisites
The source and destination ApsaraDB RDS for MySQL instances are created. For more information, see Create an ApsaraDB RDS for MySQL instance.
Background information
Data Transmission Service (DTS) provides the data integration feature. You can configure a scheduling policy when you migrate schemas and historical data from the source database to the destination database on a regular basis. The data integration feature allows you to flexibly build data warehouses. For more information, see Scheduling policies of data integration.
Precautions
The source database must have PRIMARY KEY or UNIQUE constraints and all fields must be unique. Otherwise, the destination database may contain duplicate data records.
Limits
- DTS supports schema migration for the following types of objects: table, view, trigger,
stored procedure, and function.
Note During schema migration, DTS changes the value of the SECURITY attribute from
DEFINER
toINVOKER
for views, stored procedures, and functions. - DTS does not migrate user information from the source database. Before a user can call views, stored procedures, and functions of the destination database, you must grant the read/write permissions to the user.
Billing
Migration type | Instance configuration fee | Internet traffic fee |
---|---|---|
Schema migration and full data migration | Free of charge | Charged only when data is migrated from Alibaba Cloud over the Internet. For more information, see Pricing. |
Procedure
The procedure in this topic uses ApsaraDB RDS for MySQL instances that reside in the China (Qingdao) region as an example.
Result
If a task is completed before the end of the current scheduled time, the task status changes to Completed. DTS waits for the next scheduled time and performs full data migration again.
