SQL Server

SQL Server 2022 Migration

SQL Server 2022 is a support decision as much as a feature decision. The upgrade is worth it when the application has been checked, not because the version number is newer.

Who this upgrade is for

Teams on SQL Server 2016, 2017 or 2019 move to 2022 to stay on a supported engine and to use capabilities such as Query Store hints and contained availability groups where the edition allows them. Some applications cannot move until a vendor certifies the version. We find that out before the weekend.

The general method, including rehearsal and rollback, is on database migration services. If 2016 is the source, start with SQL Server 2016 migration, because that version is already out of extended support.

Checked before cutover

  • Application and vendor support for SQL Server 2022
  • Compatibility level and a test pass of the real workload
  • Agent jobs, logins and linked servers
  • Whether an availability group has to move with the instance
  • A rollback that does not depend on hope

Tell us the version you are leaving

2016, 2017 or 2019, the size of the databases, and any vendor who has to approve SQL Server 2022.