Overview
A typical engagement starts with a team that runs SQL Server 2016 and 2017 and knows the version question is open, but inherited instances that were set up by people who have since left. A decision paper written before anyone has checked whether the backups restore would rest on assumptions.
Challenge
SQL Server 2016 extended support ended on 14 July 2026 and SQL Server 2017 extended support ends on 12 October 2027, so the question is real. Which route makes sense depends on facts nobody has gathered: whether each instance restores from its backups, which databases have never had a successful DBCC CHECKDB, how the instances are configured, and which applications block an upgrade.
Environment
SQL Server 2016 and 2017 instances in Standard and Enterprise editions on virtual machines on premises and in a cloud subscription, one availability group, Agent jobs for backups and maintenance written by earlier administrators, and applications whose vendors have not stated support for newer versions.
Approach
AceMQ agrees the scope and how query text is handled, then the customer's DBA runs read-only diagnostics that read catalog views, dynamic management views and msdb history. An AceMQ engineer and a partner SQL Server specialist review the six areas, restore one agreed database to a scratch server and time it against the recovery target, and place each instance against Microsoft's lifecycle dates.
Solution
- Read-only capture of configuration, backup history, wait statistics, Query Store state, security settings and Agent job history from each in-scope instance
- One agreed database restored to a scratch server, checked with CHECKDB and timed against the recovery time the business has stated
- Last successful CHECKDB time per database, and the databases that have never had one
- Table of instance, version, build and cumulative update, and Microsoft lifecycle position
- Findings that must be fixed whichever route is chosen, separated from findings that depend on the route
- Engineering view of upgrade, Extended Security Updates and a move for each instance, with what blocks each
Outcome
The engagement delivers a written report ranked by production risk, the timed restore result, the version and lifecycle table, the list of findings that apply on every route, and a recommendation per instance for the customer's change board. The decision, and any Microsoft licensing choice, stays with the customer.