AWS dms documentation change
Summary
Updated references from AWS Schema Conversion Tool (AWS SCT) to DMS Schema Conversion, including changing documentation links.
Security assessment
The change only updates tool references and documentation links without addressing security vulnerabilities, weaknesses, or security features. No security-related content was added or modified.
Diff
diff --git a/dms/latest/userguide/CHAP_Tasks.Creating.md b/dms/latest/userguide/CHAP_Tasks.Creating.md index 7df0fd35e..8e093f1f8 100644 --- a//dms/latest/userguide/CHAP_Tasks.Creating.md +++ b//dms/latest/userguide/CHAP_Tasks.Creating.md @@ -65 +65 @@ For this option | Do this -**Target table preparation mode** | This setting is only visible if you choose **Migrate existing data** or **Migrate existing data and replicate ongoing changes** for **Migration type** in the preceding section. **Do nothing** – In **Do nothing** mode, AWS DMS assumes that the target tables have been pre-created on the target. If the tables aren't empty, conflicts might occur during data migration and can result in a DMS task error. If the target table doesn't exist, DMS creates the table for you. Your table structure remains as is and any existing data is left in the table. **Do nothing** mode is appropriate for CDC-only tasks when the target tables have been backfilled from the source and ongoing replication is applied to keep the source and target in sync. To pre-create tables, you can use the AWS Schema Conversion Tool (AWS SCT). For more information, see [Installing AWS SCT](https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_SchemaConversionTool.Installing.html). **Drop tables on target** – In **Drop tables on target** mode, AWS DMS drops the target tables and recreates them before starting the migration. This approach ensures that the target tables are empty when the migration starts. AWS DMS creates only the objects required to efficiently migrate the data: tables, primary keys, and in some cases, unique indexes. AWS DMS doesn't create secondary indexes, nonprimary key constraints, or column data defaults. If you are performing a full load plus CDC or CDC-only task, we recommend that you pause the migration at this point. Then, create secondary indexes that support filtering for update and delete statements. You might need to perform some configuration on the target database when you use **Drop tables on target** mode. For example, for an Oracle target, AWS DMS can't create a schema (database user) for security reasons. In this case, you precreate the schema user so AWS DMS can create the tables when the migration starts. For most other target types, AWS DMS creates the schema and all associated tables with the proper configuration parameters. **Truncate** – In **Truncate** mode, AWS DMS truncates all target tables before the migration starts. If the target table doesn't exist, DMS creates the table for you. Your table structure remains as is but tables are truncated at the target. **Truncate** mode is appropriate for full load or full load plus CDC migrations where the target schema has been precreated before the migration starts. To precreate tables, you can use AWS SCT. For more information, see [Installing AWS SCT](https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_SchemaConversionTool.Installing.html). +**Target table preparation mode** | This setting is only visible if you choose **Migrate existing data** or **Migrate existing data and replicate ongoing changes** for **Migration type** in the preceding section. **Do nothing** – In **Do nothing** mode, AWS DMS assumes that the target tables have been pre-created on the target. If the tables aren't empty, conflicts might occur during data migration and can result in a DMS task error. If the target table doesn't exist, DMS creates the table for you. Your table structure remains as is and any existing data is left in the table. **Do nothing** mode is appropriate for CDC-only tasks when the target tables have been backfilled from the source and ongoing replication is applied to keep the source and target in sync. To pre-create tables, you can use DMS Schema Conversion. For more information, see [Converting database schemas using DMS Schema Conversion](./CHAP_SchemaConversion.html). **Drop tables on target** – In **Drop tables on target** mode, AWS DMS drops the target tables and recreates them before starting the migration. This approach ensures that the target tables are empty when the migration starts. AWS DMS creates only the objects required to efficiently migrate the data: tables, primary keys, and in some cases, unique indexes. AWS DMS doesn't create secondary indexes, nonprimary key constraints, or column data defaults. If you are performing a full load plus CDC or CDC-only task, we recommend that you pause the migration at this point. Then, create secondary indexes that support filtering for update and delete statements. You might need to perform some configuration on the target database when you use **Drop tables on target** mode. For example, for an Oracle target, AWS DMS can't create a schema (database user) for security reasons. In this case, you pre-create the schema user so AWS DMS can create the tables when the migration starts. For most other target types, AWS DMS creates the schema and all associated tables with the proper configuration parameters. **Truncate** – In **Truncate** mode, AWS DMS truncates all target tables before the migration starts. If the target table doesn't exist, DMS creates the table for you. Your table structure remains as is but tables are truncated at the target. **Truncate** mode is appropriate for full load or full load plus CDC migrations where the target schema has been pre-created before the migration starts. To pre-create tables, you can use DMS Schema Conversion. For more information, see [Converting database schemas using DMS Schema Conversion](./CHAP_SchemaConversion.html).