SQL Server 2016 End of Life: Extended Support Ended 14 July 2026

SQL Server 2016 reached the end of extended support on 14 July 2026. Microsoft no longer ships free security updates for it, and the only way to keep receiving them is a paid Extended Security Updates (ESU) subscription, which Microsoft lists for up to three years, to July 2029. The alternative is to upgrade to SQL Server 2022 or 2025, or to move to Azure SQL Managed Instance. The dates below come from Microsoft Learn, checked on 31 October 2026. AceMQ plans and tests the route through its SQL Server support and SQL Server DBA services; Microsoft supplies the updates.

SQL Server end of life dates by version

Microsoft stamps each end date at 06:59:59 on the following day (SQL Server 2016 shows 7/15/2026), so the dates above are the last calendar day of support. Service Pack 3, the last service pack for SQL Server 2016, left support on the same day.

What the end of extended support means

Mainstream support includes security and non-security updates. Extended support is security updates only. When it ends, Microsoft stops publishing free fixes, so a new vulnerability in SQL Server 2016 stays open on your server. An ESU subscription does not restore full support: Microsoft states that ESU licences do not include support for the underlying SQL Server version, only help with deploying, installing and activating the updates. Scanners and auditors commonly flag an unsupported database version, which is usually what starts the conversation.

Your options for SQL Server 2016

• Upgrade to SQL Server 2022 or 2025. The durable answer. Test the application first and keep a rollback path until the new version has run a full business cycle. How to run it, in place or side by side, is in SQL Server upgrade: in-place or side-by-side.
• Buy Extended Security Updates through Azure Arc. Connect the instance to Azure Arc, then subscribe with Software Assurance under an Enterprise Agreement, Enterprise Agreement Subscription, Server and Cloud Enrollment or Enrollment for Education Solutions, or with pay-as-you-go billing without Software Assurance. Azure bills hourly, you can cancel at any time, and the subscription ends when you upgrade.
• Subscribe on SQL Server on Azure VMs. Register with the SQL IaaS Agent extension. Unlike SQL Server 2014, moving SQL Server 2016 to an Azure VM does not give free ESUs.
• Move to Azure SQL Managed Instance. Microsoft runs the platform and patching, with a different feature surface; Microsoft runs the operating system and patching. The managed SQL Server page sets out when it is the better choice.
• Do nothing. The instance keeps running and stays exposed to every vulnerability disclosed from now on.

ESUs are released only when Microsoft rates a vulnerability Critical, so there is no regular schedule, and they contain no new features or customer-requested fixes. Microsoft lists three annual periods: 15 July 2026 to 13 July 2027, to 18 July 2028, and to 17 July 2029. If you only applied General Distribution Release updates during normal support, Microsoft advises installing and validating the latest cumulative update when you subscribe, not when the first ESU ships.

How to choose between them

Upgrade when the application vendor supports a newer version and you can test it this year. Use ESUs as a bridge for instances you cannot move yet, such as a vendor application pinned to SQL Server 2016, and put an end date on the subscription. Consider Managed Instance for databases that fit its feature set and where nobody wants to run the platform. Mixed estates are normal: one answer rarely fits every instance. AceMQ does not sell ESUs and cannot patch SQL Server; what we do is plan the route, rehearse it on a restored copy and support the instance around it.

A checklist for this week

1. List every SQL Server instance with its version, edition and cumulative update level, including the ones nobody owns.
2. Mark which databases run on SQL Server 2016 and which applications depend on them.
3. Install and validate the latest SQL Server 2016 cumulative update on a test copy.
4. Choose upgrade, ESU or Managed Instance per instance, and record why for your auditor.
5. Enable Query Store on the databases you will upgrade, so a plan that regresses at the new compatibility level can be forced back.
6. Write the rollback plan before the cutover window, not during it.

If the list above is longer than your team can take on, a SQL Server health check gives you the inventory and a ranked plan, and database support across engines covers the rest of the estate under one contract.

• Microsoft Lifecycle: SQL Server 2016
• Microsoft Lifecycle: SQL Server 2017
• Microsoft Lifecycle: SQL Server 2019
• Microsoft Lifecycle: SQL Server 2022
• Microsoft Lifecycle: SQL Server 2025
• Microsoft Learn: What are Extended Security Updates?
• Microsoft Learn: What is Azure SQL Managed Instance?