Now that you have installed the AWS Schema Conversion Tool, the next step is to create a Database Migration Project using the tool.
Within the Schema Conversion Tool, if the new project wizard doesn’t start please start it by going to File > New Project Wizard top left corner. Once in Project wizard mode, please enter the following values into the form note you’ll need to adjust for the source database you selected in the text below and then click Next.
| Parameter | Value |
|---|---|
| Project Name | AWS Schema Conversion Tool Source DB to Aurora MySQL (or Aurora PostgresSQL) |
| Location | C:\Users\Administrator\AWS Schema Conversion Tool |
| Type Radio Button | Click/Select SQL Database |
| Source Database Engine | Microsoft SQL Server, Oracle or Source you selected earlier in this session |
| “I want to” Radio Button | Click/Select I want to switch engines and optimize for the cloud |


Specify the source database configurations in the form, Please note the password is not provided below you need to goto Secrets Manager and open DMSDBSecret and reveal the SQLServer password value. It is also on first Cloudformation Stack’s output tab (SQLServerPassword) and click Test Connection. Once the connection is successfully tested, click Next.
Depending on your source database, choose one of the following routes to follow the steps.

Select the dms_sample database, then click Next. (Note: once you click on database gray/blue bar highlight should appear & Next button will be enabled)

SCT will examine in detail all of the objects in the schema of source database. It will convert as much as possible automatically and provides detailed information about items it could not convert. If you scroll down on the report you’ll see specific target databases like below for SQL Server to Aurora MySQL.
Generally, packages, procedures, and functions are more likely to have some issues to resolve because they contain the most custom or proprietary SQL code. AWS SCT specifies how much manual change is needed to convert each object type. It also provides hints about how to adapt these objects to the target schema successfully.
After you are done reviewing the database migration assessment report, click Next.

Specify the target database configurations in the form, Please note the password is not provided below you need to go to Secrets Manager and open DMSDBSecret and reveal the password. It is also on first Cloudformation Stack’s output tab see the SQLSever password (same as above) and then click Test Connection. Once the connection is successfully tested, click Finish.


After hitting Next and loading metadata, you may get a warning message saying: Metadata loading was intrupted because of data fetching issues. You can ignore this message as it doesn’t affect us in this workshop. Note it will take a few minutes for SCT to analyze the database objects