Migration software
AWS Schema Conversion Tool
Suggested in one of our migration playbooks, mainly for Databases. Here is what it handles, how it treats key settings, and other tools for the same jobs.
What does AWS Schema Conversion Tool handle?
The limits of the built-in tools that AWS Schema Conversion Tool gets around, as covered in our playbooks.
Oracle to PostgreSQL migration
- Size the code conversion before you promise a dateFor Oracle to PostgreSQL, converts SQL embedded in C#, C++, Java and Pro*C applications and SQL*Plus scripts to PSQL. Works on a local copy and lists items you must convert by hand in an assessment report.
- Finding Oracle-only SQL in the application by hand is slow and easy to get wrong.Converts SQL embedded in C#, C++, Java and Pro*C applications and SQL*Plus scripts, and lists what you must convert by hand.
How does AWS Schema Conversion Tool handle key settings?
From the settings checklists in our playbooks: what AWS Schema Conversion Tool carries across.
| Setting | How it handles it | Playbook |
|---|---|---|
| SQL inside the application | Converts SQL embedded in C#, C++, Java and Pro*C applications and SQL*Plus scripts, and lists what you must convert by hand. | Oracle to PostgreSQL migration |
Which tools do the same jobs as AWS Schema Conversion Tool?
Other tools our playbooks suggest for the same migrations.
We write these notes from the vendor documentation cited in each playbook. Tools cannot pay to be included or to change them. Check the vendor's current documentation and terms before you buy.