Converting database schemas using DMS Schema Conversion
DMS Schema Conversion in AWS Database Migration Service (AWS DMS) makes database migrations between different types of databases more predictable. Use DMS Schema Conversion to assess the complexity of your migration for your source data provider, and to convert database schemas and code objects. You can then apply the converted code to your target database.
DMS Schema Conversion automatically converts your source database schemas and most of the database code objects to a format compatible with the target database. This conversion includes tables, views, stored procedures, functions, data types, synonyms, and so on. Any objects that DMS Schema Conversion can't convert automatically are clearly marked. To complete the migration, you can convert these objects manually.
At a high level, DMS Schema Conversion
For the list of supported source databases, see Sources for DMS Schema Conversion.
For the list of supported target databases, see Targets for DMS Schema Conversion.
The following diagram illustrates the DMS Schema Conversion process.
Use the following topics to better understand how to use DMS Schema Conversion.
Topics
- Supported AWS Regions
- Schema conversion features
- Schema conversion limitations
- Getting started with DMS Schema Conversion
- Setting up a network for DMS Schema Conversion
- Creating source data providers in DMS Schema Conversion
- Creating target data providers in DMS Schema Conversion
- Managing migration projects in DMS Schema Conversion
- Creating database migration assessment reports with DMS Schema Conversion
- Using DMS Schema Conversion
- Using extension packs in DMS Schema Conversion
Supported AWS Regions
You can create a DMS Schema Conversion migration project in the following AWS Regions. In other Regions, you can use the AWS Schema Conversion Tool. For more information about AWS SCT, see the AWS Schema Conversion Tool User Guide.
| Region Name | Region |
|---|---|
| US East (N. Virginia) | us-east-1 |
| US East (Ohio) | us-east-2 |
| US West (Oregon) | us-west-2 |
| Asia Pacific (Tokyo) | ap-northeast-1 |
| Asia Pacific (Singapore) | ap-southeast-1 |
| Asia Pacific (Sydney) | ap-southeast-2 |
| Europe (Frankfurt) | eu-central-1 |
| Europe (Stockholm) | eu-north-1 |
| Europe (Ireland) | eu-west-1 |
Schema conversion features
DMS Schema Conversion provides the following features:
-
DMS Schema Conversion automatically manages the AWS Cloud resources that are required for your database migration project. These resources include instance profiles, data providers, and AWS Secrets Manager secrets. They also include AWS Identity and Access Management (IAM) roles, Amazon S3 buckets, and migration projects.
-
You can use DMS Schema Conversion to connect to your source database, read the metadata, and create database migration assessment reports. You can then save the report to an Amazon S3 bucket. With these reports, you get a summary of your schema conversion tasks and the details for items that DMS Schema Conversion can't automatically convert to your target database. Database migration assessment reports help evaluate how much of your migration project DMS Schema Conversion can automate. Also, these reports help estimate the amount of manual effort that is required to complete the conversion. For more information, see Creating database migration assessment reports with DMS Schema Conversion.
-
After you connect to your source and target data providers, DMS Schema Conversion can convert your existing source database schemas to the target database engine. You can choose any schema item from your source database to convert. After you convert your database code in DMS Schema Conversion, you can review your source code and the converted code. Also, you can save the converted SQL code to an Amazon S3 bucket.
-
Before you convert your source database schemas, you can set up transformation rules. You can use transformation rules to change the data type of columns, move objects from one schema to another, and change the names of objects. You can apply transformation rules to databases, schemas, tables, and columns. For more information, see Setting up transformation rules.
-
You can change conversion settings to improve the performance of the converted code. These settings are specific for each conversion pair and depend on the features of the source database that you use in your code. For more information, see Specifying schema conversion settings.
-
In some cases, DMS Schema Conversion can't convert source database features to equivalent Amazon RDS features. For these cases, DMS Schema Conversion creates an extension pack in your target database to emulate the features that weren't converted. For more information, see Using extension packs.
-
You can apply the converted code and the extension pack schema to your target database. For more information, see Applying your converted code.
-
DMS Schema Conversion supports all of the features in the latest AWS SCT release. For more information, see The latest release notes for AWS SCT .
-
You can edit converted SQL code before DMS migrates it to the target database. For more information, see Editing and saving your converted SQL code .
Schema conversion limitations
DMS Schema Conversion is a web-version of the AWS Schema Conversion Tool (AWS SCT). DMS Schema Conversion supports less database platforms and provides more limited functionality compared to the AWS SCT desktop application. To convert data warehouse schemas, big data frameworks, application SQL code, and ETL processes, use AWS SCT. For more information about AWS SCT, see the AWS Schema Conversion Tool User Guide.
The following limitations apply when you use DMS Schema Conversion for database schema conversion:
-
You can't save a migration project and use it in an offline mode.
-
You can't edit SQL code for the source in a migration project for DMS Schema Conversion. To edit the SQL code of your source database, use your regular SQL editor. Choose Refresh from database to add the updated code in your migration project.
-
Migration rules in DMS Schema Conversion don't support changing column collation. Also, you can't use migration rules to move objects to a new schema.
-
You can't apply filters to your source and target database trees to display only those database objects that meet the filter clause.
-
DMS Schema Conversion extension pack doesn't include AWS Lambda functions that emulate email sending, job scheduling, and other features in your converted code.
-
DMS Schema Conversion doesn't use customer-managed KMS keys for access to any customer AWS resources. For example, DMS Schema Conversion doesn't support using a customer-managed KMS key to access customer data in Amazon S3.
