SQL Server 2016 reached end of extended support on July 14, 2026. Extended Security Updates can provide up to three additional years for eligible deployments, but the earlier escalating annual-price schedule was false. Microsoft describes annual ESU pricing at approximately 75% of the on-premises license cost.
Current as of 2026-08-15
Microsoft’s end-of-support overview lists the lifecycle and modernization paths. The ESU years run to July 13, 2027, July 18, 2028, and July 17, 2029.
Decision summary
- Use Microsoft’s approximately 75% annual ESU estimate and obtain an exact licensing quote.
- Use current assessment tooling rather than retired Data Migration Assistant or Azure Data Studio guidance.
- Choose ESU only as a governed bridge with a funded exit date.
- Test application, driver, compatibility, performance, backup, and rollback before migration.
Choose a supported destination
- Upgrade to a supported SQL Server release on premises or in a supported hosted environment.
- Move an appropriate workload to Azure SQL Managed Instance or Azure SQL Database.
- Run SQL Server in Azure virtual machines with the applicable management and ESU benefits.
- Remain temporarily on SQL Server 2016 with paid ESUs and a documented exit plan.
Use the current assessment path
Microsoft has retired Data Migration Assistant and Azure Data Studio. Use the current SQL Server Migration component in SQL Server Management Studio 21 and current Azure migration or Azure Arc assessment capabilities identified in Microsoft’s documentation.
Build a complete inventory
- Instances, editions, versions, and licensing.
- Databases, compatibility levels, size, growth, and criticality.
- Applications, drivers, linked servers, SSIS, SSRS, SQL Agent, and vendor support.
- Authentication, encryption, certificates, service accounts, and privileged access.
- Backup, recovery objectives, high availability, and maintenance windows.
Treat ESU as a bridge
Microsoft’s end-of-support overview gives the approximately 75% annual estimate, while its ESU FAQ explains eligibility. Obtain an exact licensing quote for the deployment. Assign an executive owner, target platform, budget, milestones, and stop condition before purchasing the bridge.
Validate and roll back
Restore production-like data into the target, run workload and failure tests, validate backups, rehearse cutover, and define rollback before the maintenance window. Preserve a supported recovery path until business owners sign off.
For related guidance from ITECS, see ITECS managed Azure cloud services.
Sources and update trigger
- Microsoft Learn — SQL Server end-of-support overview
- Microsoft Learn — SQL Server ESU FAQ
- Microsoft Learn — ESUs for SQL Server in Azure VMs
- Microsoft SQL Server Blog — Protect and modernize SQL Server 2016
Review trigger: Review at every ESU-year boundary, licensing renewal, or material application/platform change.
continue reading
More ITECS blog articles
About ITECS Team
The ITECS team consists of experienced IT professionals dedicated to delivering enterprise-grade technology solutions and insights to businesses in Dallas and beyond.
View full profile and articles