Parameter | Description |
Migration Types | Select the migration types based on your business requirements. The migration types must be supported by the database engine. To perform only full data migration, select Schema Migration and Full Data Migration. To ensure service continuity during data migration, select Schema Migration, Full Data Migration, and Incremental Data Migration.
Note If you do not select Incremental Data Migration, we recommend that you do not write data to the source database during data migration. This ensures data consistency between the source and destination databases. |
Processing Mode of Conflicting Tables | Precheck and Report Errors: checks whether the destination database contains tables that have the same names as tables in the source database. If the source and destination databases do not contain tables that have identical table names, the precheck is passed. Otherwise, an error is returned during the precheck and the data migration task cannot be started. Note You can use the object name mapping feature to rename the tables that are migrated to the destination database. You can use this feature if the source and destination databases contain tables that have identical table names and the tables in the destination database cannot be deleted or renamed. For more information, see Map object names. Ignore Errors and Proceed: skips the precheck for identical table names in the source and destination databases. Warning If you select Ignore Errors and Proceed, data inconsistency may occur and your business may be exposed to the following potential risks: If the source and destination databases have the same schemas, DTS does not migrate data records that have the same primary key values as data records in the destination database. If the source and destination databases have different schemas, only specific columns are migrated or the data migration task fails. Proceed with caution.
|
DDL and DML Operations to Be Synchronized | The DDL and DML operations that you want to migrate. For more information, see the SQL operations that can be incrementally migrated section of this topic. Note To select the SQL operations performed on a specific table, right-click an object in the Selected Objects section. In the dialog box that appears, select the SQL operations that you want to migrate during incremental data migration. |
Merge Tables | Yes: In online transaction processing (OLTP) scenarios, sharding is implemented to speed up the response to business tables. In online analytical processing (OLAP) scenarios, you can store a large volume of data in a single table. This makes your SQL queries more efficient. You can merge multiple source tables that have the same schema into a single destination table. This feature allows you to synchronize data from multiple tables in the source database to a single table in the destination database. For more information, see Enable the multi-table merging feature. Note After you select multiple tables from the source database, you must change the names of these tables to the name of the destination table. To do this, you can use the object name mapping feature. For more information, see Map object names. DTS adds a column named __dts_data_source to the destination table. This column is used to record the data source. The data type of this column is TEXT. DTS specifies the column values based on the following format: <DTS instance ID>:<Database name>:<Schema name>:<Table name>. Such column values allow DTS to identify each source table. For example, dts********:dtstestdata:testschema:customer1 indicates that the source table is customer1. If you set this parameter to Yes, all the selected source tables in the task are merged into a destination table. If you do not need to merge specific source tables, you can create a separate data synchronization task for these tables.
Warning We recommend that you do not perform DDL operations to change the schemas of source databases or tables. Otherwise, data inconsistency may occur or the data synchronization task fails. No: This value is selected by default.
|
Capitalization of Object Names in Destination Instance | The capitalization of database names, table names, and column names in the destination instance. By default, DTS default policy is selected. You can select other options to ensure that the capitalization of object names is consistent with that in the source or destination database. For more information, see Specify the capitalization of object names in the destination instance. |
Source Objects | Select one or more objects from the Source Objects section and click the  icon to add the objects to the Selected Objects section. Note You can select columns, tables, or schemas as the objects to be migrated. If you select tables or columns as the objects to be migrated, DTS does not migrate other objects, such as views, triggers, or stored procedures, to the destination database. |
Selected Objects | - To rename an object that you want to migrate to the destination instance, right-click the object in the Selected Objects section. For more information, see Map the name of a single object.
- To rename multiple objects at a time, click Batch Edit in the upper-right corner of the Selected Objects section. For more information, see Map multiple object names at a time.
Note If you use the object name mapping feature to rename an object, other objects that are dependent on the object may fail to be migrated. To specify WHERE conditions to filter data, right-click a table in the Selected Objects section. In the dialog box that appears, specify the conditions. For more information, see Use SQL conditions to filter data. To select the SQL operations performed on a specific database or table, right-click an object in the Selected Objects section. In the dialog box that appears, select the SQL operations that you want to migrate. For more information, see the SQL operations that can be incrementally migrated section of this topic.
|
Elastic Compute Service (ECS)
Container Compute Service (ACS)
