将 SQL 服务器迁移到新的 AWS Aurora 数据库
Migrating SQL Server to New AWS Aurora DB
我们正在将现有的 Premise SQL 服务器数据库迁移到 cloud.We 中的 AWS Aurora 数据库，刚刚在 RDS 实例中构建了目标 Aurora 数据库。它没有表，完全 empty.In 我连接的模式转换工具源 SQL 服务器数据库和目标 AWS Aurora DB。此时，如果我从 SQL 服务器迁移到空的 Aurora 数据库。 SCT 和 DMS 应该将我的整个 SQL 服务器数据库迁移到 AWS Aurora，对吧？或者我是否必须在 Target AWS 数据库中创建表 运行 SCT 和 DMS。
DMS 将为您创建表格，但不会复制一些详细信息。来自 the docs:
AWS DMS supports basic schema migration, including the creation of
tables and primary keys. However, AWS DMS doesn't automatically create
secondary indexes, foreign keys, user accounts, and so on in the
target database.
如果您使用 SCT，则可以迁移这些。
AWS DMS doesn't migrate your secondary indexes, sequences, default
values, stored procedures, triggers, synonyms, views, and other schema
objects that aren't specifically related to data migration. To migrate
these objects to your Aurora MySQL target, use AWS SCT.
migrating from SQL Server to Amazon Aurora 的分步指南可能会有所帮助。使用 SCT，您可以选择是否要通过设置准备模式来创建表。
Do nothing - AWS DMS does nothing to prepare your tables. Your table structure remains the same, and any existing data remains in the
table. You can use this method to consolidate data from multiple
systems.
Drop tables on target - AWS DMS creates your target tables for you. AWS DMS drops and re-creates the tables to migrate before
migration. AWS DMS creates the table and a primary key only for
heterogeneous migrations.
Truncate - AWS DMS truncates a target table before loading it. If the target table doesn’t exist, then AWS DMS creates it.
我们正在将现有的 Premise SQL 服务器数据库迁移到 cloud.We 中的 AWS Aurora 数据库，刚刚在 RDS 实例中构建了目标 Aurora 数据库。它没有表，完全 empty.In 我连接的模式转换工具源 SQL 服务器数据库和目标 AWS Aurora DB。此时，如果我从 SQL 服务器迁移到空的 Aurora 数据库。 SCT 和 DMS 应该将我的整个 SQL 服务器数据库迁移到 AWS Aurora，对吧？或者我是否必须在 Target AWS 数据库中创建表 运行 SCT 和 DMS。
DMS 将为您创建表格，但不会复制一些详细信息。来自 the docs:
AWS DMS supports basic schema migration, including the creation of tables and primary keys. However, AWS DMS doesn't automatically create secondary indexes, foreign keys, user accounts, and so on in the target database.
如果您使用 SCT，则可以迁移这些。
AWS DMS doesn't migrate your secondary indexes, sequences, default values, stored procedures, triggers, synonyms, views, and other schema objects that aren't specifically related to data migration. To migrate these objects to your Aurora MySQL target, use AWS SCT.
migrating from SQL Server to Amazon Aurora 的分步指南可能会有所帮助。使用 SCT，您可以选择是否要通过设置准备模式来创建表。
Do nothing - AWS DMS does nothing to prepare your tables. Your table structure remains the same, and any existing data remains in the table. You can use this method to consolidate data from multiple systems.
Drop tables on target - AWS DMS creates your target tables for you. AWS DMS drops and re-creates the tables to migrate before migration. AWS DMS creates the table and a primary key only for heterogeneous migrations.
Truncate - AWS DMS truncates a target table before loading it. If the target table doesn’t exist, then AWS DMS creates it.