Migration software
MySQL Shell
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 it handles
The limits of the built-in tools that MySQL Shell gets around, as covered in our playbooks.
SQL Server and MySQL to Amazon RDS or Aurora
- Users, routines and time zones need recreating on AuroraUsers and routines are included by default. Use excludeUsers to leave out accounts the target will not accept; user-defined functions are not included. Oracle does not document Aurora as a target, so test the load.
- Aurora MySQL physical restore (from XtraBackup files) does not restore user accounts, functions, stored procedures or time zone information.Dumps users, grants and routines in one go. User-defined functions are not included, and Aurora is not a documented target, so test the load.
How it handles key settings
From the settings checklists in our playbooks: what MySQL Shell carries across.
| Setting | How it handles it | Playbook |
|---|---|---|
| Logins, users and grants | Dumps user accounts, roles and grants with the instance. Aurora is not a documented target, so test the load. | SQL Server and MySQL to Amazon RDS or Aurora |
| Stored procedures, functions, triggers and jobs | Includes routines, events and triggers. User-defined functions are not included. | SQL Server and MySQL to Amazon RDS or Aurora |
Tools for the same jobs
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.