Create a new project<\/a>
Connect to origin and destination servers<\/a>
Select the database you would like to analyse<\/a>
Drill down to make changes<\/a><\/strong><\/p><\/blockquote>\n\n\n\n
\n\n\n\nOpen the AWS SCT and create a new project<\/h3>\n\n\n\n
Prerequisites: <\/strong>Your new Amazon RDS or Aurora<\/a> instance is deployed and the necessary drivers have been installed. This takes a few clicks from the AWS console.<\/p>\n\n\n\n
Once you’ve got everything up and running pick your source and target database types. The tool currently supports a number of database sources and Aurora and Redshift<\/a> as a destination.<\/p>\n\n\n\n
Image from AWS Documentation<\/figcaption><\/figure><\/div>\n\n\n\n Limitations<\/h5>\n\n\n\n
- You cannot use Redshift as a source if you are moving data into an Aurora database.<\/li><\/ul>\n\n\n\n
\n\n\n\nConnect to both the origin and destination servers<\/h3>\n\n\n\n
The origin will appear on the left and the destination will appear on the right with action items in the middle.<\/p>\n\n\n\n
Image from AWS Documentation<\/figcaption><\/figure><\/div>\n\n\n\n
\n\n\n\nSelect the database<\/h3>\n\n\n\n
Go to: Actions > Create Report<\/strong><\/p>\n\n\n\n
The drivers will then examine in detail all of the objects in that schema, including the schema itself, tables, views, procedures, functions, and packages.<\/p>\n\n\n\n
It will convert as much as possible automatically and provide detailed information about items it couldn\u2019t convert. The report can be saved as a .csv file or a .pdf file for review.<\/p>\n\n\n\n
Image from AWS Documentation<\/figcaption><\/figure><\/div>\n\n\n\n
- Green can be resolved right away.<\/li><\/ul>\n\n\n\n
- Yellow need minor tweaks.<\/li><\/ul>\n\n\n\n
- Red needs significant work to update.<\/li><\/ul>\n\n\n\n
Limitations<\/h5>\n\n\n\n
We ran into trouble when converting tables with indexes. SQL Server supports INCLUDE<\/a> but as PostgreSQL does not it meant manually doing changes to make sure these columns were captured in the new index.<\/p>\n\n\n\n
\n\n\n\nDrill down into each object to check where changes need to be made<\/h3>\n\n\n\n
Image from AWS Documentation<\/figcaption><\/figure><\/div>\n\n\n\n When ready to commit, right click and select ‘apply to database’.<\/p>\n\n\n\n
You can now go to your new Amazon RDS and refresh the database to pull over your work.<\/p>\n\n\n\n
Migration of the data can also happen at this point if the necessary drivers have been installed or you can then use the AWS Database Migration Service.<\/a><\/p>\n\n\n\n
\n\n\n\nAnd that’s it. The Schema Conversion Tool is incredibly easy to use and a massive time saver when it comes to migration, so we can spend more time upskilling users and less time tinkering with scripts and schemas.<\/p>\n\n\n\n
Read more about the tool in the AWS documentation<\/a>.<\/p>\n\n\n\n
\n\n\n\nPhoto by Designecologist<\/a><\/strong> from Pexels<\/a><\/strong> <\/p>\n","protected":false},"excerpt":{"rendered":"