Database migration with SSMA: Handling typical conversion errors
ABCloudz tech experts possess outstanding experience in migrating databases. For this purpose, we frequently use SQL Server Migration Assistant (SSMA). SSMA utilization may cause various types of errors, so we have created a blog post series which focused on typical database conversion errors. Each post in this series is dedicated to a separate problem statement and presents our recommendations on how it should be approached and fixed.
Related posts
Here is the list of blog posts on the most common SSMA conversion errors. We will continue updating this list as we publish new materials on the conversion challenges. We strongly recommend you bookmark this post so that you will keep updated. These are some topics we have already covered:
- Foreign keys with distinctive types of columns and referenced columns
- Table expressions that are not supported
- Unparsed Microsoft SQL-Pivot operator
- Interval expressions
- Interval literals
- SQL clause that is not supported
- Float type for materialized view
- Database links
SSMA conversion errors
An SQL Server Migration Assistant (SSMA) helps you automate your database migration projects by converting the source code. However, there may be cases when SSMA fails to convert specific parts of the code. SSMA will notify you about such problems with warnings or error messages. They are automatically displayed on your screen or added as comments to the converted code.
Unfortunately, SSMA does not provide any instructions or suggestions on handling the errors or warnings. In such cases, you will need to convert the problematic parts of the code manually, while SSMA will merely estimate the approximate time required for such conversion.
Make sure to check our recent blog post on the AWS Schema Conversion Tool (SCT) to know more about automated database conversion. Don’t hesitate to contact us for more relevant information or for help with your database migration projects.
