SQL Server

SQL Server Migration

A migration fails in the details: a job that did not move, a login that no longer maps, or a downtime window that was shorter than the data copy.

Move the database without guessing the cutover

Companies migrate because the server is old, the version is out of support, or the application is moving to Azure or AWS. The database move is the part that has to be rehearsed. Application compatibility, linked servers, SQL Agent jobs and SSIS packages are part of the same plan.

Method and validation are described on database migration services. Version-specific notes are on SQL Server 2016 and SQL Server 2022.

What the plan has to name

  • Source and target version
  • Database size and the allowed downtime
  • Jobs, linked servers and integration packages
  • How success will be checked before users return
  • How to go back if the cutover is wrong

Need help with SQL Server?

Schedule a Consultation Request SQL Server Health Assessment

Planning a migration?

Send the current version, the target, and whether the application can stop for an hour or needs a shorter cutover.

Contact AVRIN or call 562.445.5872