Cloud

Database Cloud Migration

Moving a database to the cloud is a cutover project. The destination only helps if the application, the jobs and the recovery plan arrive with it.

Pick the service, then rehearse the move

For SQL Server the usual destinations are Azure SQL, Azure SQL Managed Instance, SQL Server on Azure or Amazon RDS, or SQL Server on EC2. For PostgreSQL, Aurora is one option and not the only one. Google Cloud SQL is in scope when that is the platform you have chosen. We do not treat one cloud as the default.

Service limits are on cloud and hybrid database services. Version upgrades that happen at the same time are on database migration services. A continuous copy during the move may use AWS DMS when the source and target support it.

Named before the project starts

  • Source engine and version
  • Target service, not only the cloud vendor
  • Downtime the business can accept
  • Jobs and integrations that must move
  • How you get back if the cutover fails

Where is the database going?

Azure, AWS or Google Cloud, and whether the engine stays SQL Server. If the target service is undecided, that is a fine place to start.