Parameter | Description |
Migration Types | 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 schema, DTS does not migrate data records that have the same primary keys 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.
|
Operation Types | Select the types of operations that you want to migrate based on your business requirements. By default, all operation types are selected. |
Processing Policy of Dirty Data | The processing policy for handling data write errors. Valid values: |
Data Write Mode | The mode in which data is written. Valid values: |
Batch Write Mode | The operation that is used to write multiple rows of data to the Tablestore instance at a time. Valid values: To achieve higher read and write efficiency and reduce your costs of using the Tablestore instance, we recommend that you select BulkImportRequest. |
More | You can configure the following parameters based on your business requirements: Queue Size: the length of the queue for writing data to the Tablestore instance. Thread Quantity: the number of callback threads for writing data to the Tablestore instance. Concurrency: the maximum number of concurrent threads for the Tablestore instance. Buckets: the number of concurrent buckets for writing incremental data in sequence. To improve the concurrent write capability, you can set this parameter to a large value. Note The value must be less than or equal to the maximum number of concurrent threads.
|
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 make sure 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. Click the  icon and add the objects to the Selected Objects section. Note You can select tables or databases as the objects to be migrated. If you select tables as the objects to be migrated, DTS does not migrate other objects such as views, triggers, and stored procedures to the destination database. If you select Tablestore as the destination database type, you can migrate tables only in a single database. You can select only one database or multiple tables in the same 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 Only table name mapping is supported. 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.
|
Elastic Compute Service (ECS)
Container Compute Service (ACS)
