This continues our video blog series on AWS Schema Conversion Tool. In our previous blog post Selecting target database type for migration using Assessment Report in AWS Schema Conversion Tool we talked about multi-platform Database Migration Assessment Report, which helps users to select the target database type depending on the complexity of migration and thus simplify the database migration process. And now we’ll concentrate on using the Assessment Report inside the AWS Schema Conversion Tool application.
Once you have determined the target database type, the goal of the assessment report is to examine all issues that the Schema Conversion Tool identified for the database migration process. It also provides advice on how to convert different types of objects if they are not supported in the target database or could not be automatically converted by the application. This is not the weakness of AWS Schema Conversion Tool. In fact, the AWS Schema Conversion Tool can be useful at this point, because it provides some valuable comments for each database object that could not be automatically converted. This helps you to manage and overcome all errors and warnings as part of the migration effort.
There is a specific Action Items View of the Assessment Report which allows users to concentrate on items occurring during database migration process. In this format, you can easily explore the source code of database objects which caused the current issue.
In the following video we’ll show you how to use all features of Database Migration Assessment Report, including Action Items, for an already created project in the AWS Schema Conversion Tool.
We used the AWS Schema Conversion Tool in several real database migration projects. We found the Assessment Report for the chosen pair of source and target database really helpful and useful in our practice. Here are some of the key findings:
- The Assessment Report shows the exact number of issues occurring during current database migration process. It provides the detailed information on every issue, so you can estimate the time needed to solve these issues.
- Just in one mouse click you can review the source code of functions and procedures causing the current issue. All database objects are shown in metadata trees. SCT always keeps them synchronized between each other inside the loaded migration project. So, you can easily access all the data and code objects of converted database for making the needed changes.
- We really liked the pop-up notifications and code highlights of migration issues. These features simplify navigation inside the project.
- Migrating an Oracle to MySQL Database using the AWS Schema Conversion Tool
- AWS Schema Conversion Tool: Offline mode
- AWS Schema Conversion Tool: Connecting to Oracle Source Database
- Selecting target database type for migration using Assessment Report in AWS Schema Conversion Tool
- Converting Objects during Database Migration using AWS Schema Conversion Tool
- AWS Schema Conversion Tool: Applying Converted Code to Target Database
- General Approach to Migration of Data Warehouses to Amazon Redshift
- Specific Features of Migrating Data Warehouses to Redshift
- First look at AWS Schema Conversion Tool with tighter DMS integration
- Using AWS Schema Conversion Tool for Application Conversion
- Optimizing your Redshift Storage with AWS Schema Conversion Tool
- Extracting Data from Warehouses with Data Migration Agents in AWS Schema Conversion Tool
- Using AWS Schema Conversion Tool Extension Pack for OLTP databases
- Using AWS Schema Conversion Tool Extension Pack for Data Warehouses
Stay tuned to our blog for more tips and insights into migrating databases and applications to AWS. To learn how the experts at DB Best can help you jump-start your effort, contact us to get started.