Databases migration playbooks
3 end-to-end playbooks with templates, checklists and the official sources they are based on.
Database moves are usually the riskiest part of a migration, because applications break if the schema, collation, logins or connection strings change. Each guide below covers the full path: assess compatibility first, pick an online or offline method, rehearse, then cut over with a rollback plan.
Which guide do I need?
- You run SQL Server and want a managed Azure service, or SQL Server on an Azure VMSQL Server to Azure SQL migration →
- You are moving MySQL, MariaDB, PostgreSQL, SQL Server or Oracle to Amazon RDSSQL Server and MySQL to Amazon RDS or Aurora →
- You want to leave Oracle licensing and convert the schema and code to PostgreSQLOracle to PostgreSQL migration →
- The database is part of a bigger move of servers to AzureAzure migration →
Pick the right method for each database (native backup and restore, physical backup to Aurora, or AWS DMS with change data capture), then test and cut over.
17 min readHow to migrate from Oracle to PostgreSQLAssess the Oracle schema, convert tables and PL/SQL to PostgreSQL, move the data with a bulk load or change data capture, prove the result row by row, then cut the application over with a tested way back.
26 min readHow to migrate SQL Server to Azure SQLChoose between Azure SQL Database, Azure SQL Managed Instance and SQL Server on Azure VMs, assess compatibility, pick the current migration tool and cut over.
17 min read