SQL Server 2016 End of Life:
support ended yesterday — here is every path forward

SQL Server 2016 reached the end of Microsoft extended support on July 14, 2026. Mainstream support had already ended five years earlier, on July 13, 2021 — extended support was the last five years of free security-only servicing, and now that has ended too. This applies across every edition: Developer, Enterprise, Enterprise Core, Express, Standard, and Web. If you have a SQL Server 2016 instance running anywhere in your environment, its support status changed yesterday, whether or not anything visibly broke.

What Stopped Yesterday

End of extended support under Microsoft's Fixed Lifecycle Policy is a hard cutoff, not a gradual wind-down. As of July 14, 2026:

• No more free security updates Microsoft ships no further security patches for SQL Server 2016 outside the paid ESU program. Any vulnerability disclosed from July 15 onward stays permanently unpatched on an unlicensed instance.
• No more non-security fixes Servicing Pack 3 (SP3) was the last service pack; no further cumulative updates, reliability fixes, or non-security patches will ship.
• No more Microsoft support tickets Microsoft will not take a SQL Server 2016 support case at all — even with an active support plan — unless you hold an ESU subscription or have migrated the workload to Azure.
• Compliance status changed overnight "End of vendor security support" is an automatic finding under PCI DSS, SOC 2, ISO 27001, and HIPAA assessments. Nothing about the running database changed technically — your audit posture did.

The Dates, Stated Plainly

Every date above comes from Microsoft's published lifecycle and ESU documentation. Note that being on SP3 was already a requirement to be in support at all this year — SP2 servicing ended back in October 2022 — and SP3 remains the mandatory baseline for ESU eligibility.

The ESU Decision Math

Extended Security Updates are the only way to keep receiving Microsoft security patches for SQL Server 2016, and the terms are narrower than people expect. Before budgeting for ESUs, run the actual math:

In practice, ESU is correctly priced as a scheduling tool, not a destination. It buys a fixed, non-renewable window to complete a migration that was already going to be necessary — it does not buy indefinite safety. Teams that treat the three years as "solved" rather than "a deadline moved once" tend to arrive at July 2029 with the same unmigrated database and no further options.

How ESUs Are Actually Purchased

There are exactly two purchase routes, and the fine print differs:

• Azure Arc, pay-as-you-go Connect eligible SQL Server 2016 instances to Azure Arc and subscribe to ESUs on a consumption basis. This works for instances running anywhere — on-premises, another cloud, or Azure — as long as they are Arc-enrolled.
• Volume licensing with Software Assurance Purchase ESUs annually through your existing volume licensing agreement, contingent on active Software Assurance coverage for the licenses in question.
• Billing starts regardless of when you subscribe The ESU clock started at midnight UTC on July 15, 2026. If you subscribe in September 2026, you are billed back to July 15 — there is no way to defer the cost by delaying enrollment, only a way to delay when the patches start arriving.
• Azure VMs are not a free pass With SQL Server 2014, Microsoft made ESUs free for workloads running on Azure VMs. That exemption does not carry over to SQL Server 2016 — Azure-hosted instances still require a paid ESU subscription.

The Editions That Get Nothing

This is the detail most likely to catch teams off guard: ESU eligibility is restricted to Enterprise and Standard editions only. If your SQL Server 2016 instances run on Express, Web, or Developer edition, there is no ESU purchase option at any price, through any channel. Those editions are simply done — the only paths are migration or unmanaged risk.

This matters more than the edition names suggest. SQL Server 2016 Express is free, has no licensing gate, and is bundled or silently installed by a long list of line-of-business applications, monitoring agents, and internal tools — which means it tends to be under-inventoried relative to Enterprise and Standard, which are usually tracked because they're paid. A shop that budgets ESU coverage for its "real" databases and never checks for Express instances can end up with permanently unpatched SQL Server sitting on internal networks, unaccounted for.

If SQL Server 2016 Sits Under SharePoint

SQL Server 2016 was a common database tier for on-premises SharePoint farms. If that describes your environment, worth knowing: SharePoint Server 2016 and SharePoint Server 2019 also reached end of support on the identical date, July 14, 2026 — but unlike SQL Server, Microsoft has not announced any ESU program for SharePoint itself. That means the database tier under your farm has a paid three-year bridge available, and the application tier on top of it does not.

If this is your situation, read the full breakdown of the double SharePoint cutoff, the missing SharePoint ESU option, and the combined options table in our companion piece: SharePoint 2016 & 2019 End of Life — the July 14 double cutoff.

Migration Paths

• Upgrade to SQL Server 2022 The direct on-premises path where application compatibility allows. Keeps full control of the instance and licensing model, and resets the support clock against a current lifecycle.
• Migrate to Azure SQL Database or Managed Instance Removes the version-lifecycle problem entirely — Azure SQL is a managed service with no discrete "end of support" date for the customer to track. Requires assessing compatibility and, for Managed Instance, near-drop-in migration for most workloads.
• ESU as a bridge while you plan the above For Enterprise/Standard instances that cannot move immediately — vendor certification gaps, large data volumes, complex dependency chains — ESU buys up to three years of Critical-only patching to execute the migration on a controlled timeline, not a rushed one.

Your Action Checklist

• Inventory every SQL Server 2016 instance, including hidden Express installsCheck for edition, service pack level, and what depends on each instance — application databases, reporting servers, SharePoint content databases, vendor-packaged tools.
• Sort instances by edition eligibilityEnterprise/Standard on SP3 can buy ESU. Express, Web, and Developer cannot — those need a migration decision now, not a purchasing decision.
• Decide per instance: upgrade, Azure SQL, or ESU bridgePrioritize by exposure — internet-adjacent or credential-rich databases first — not by convenience.
• If buying ESU, subscribe now via Azure Arc or Software AssuranceBilling already started July 15, 2026 for every eligible instance whether or not you have subscribed — waiting only adds bill-back, it does not reduce cost.
• Check whether SharePoint sits on top of any affected instanceSharePoint 2016 and 2019 have no ESU option at all — if your SQL Server 2016 database is a SharePoint content database, the application tier needs its own migration plan.
• Apply compensating controls to anything staying unmanagedNetwork segmentation, restricted access, and increased monitoring on instances not covered by ESU and not yet migrated. Document these as temporary controls, not a fix.
• Log the finding in your risk register before your auditor doesSQL Server 2016 is now "end of vendor support" under PCI DSS, SOC 2, ISO 27001, and HIPAA. A documented migration plan with dates converts this into a managed exception.

Frequently Asked Questions

When did SQL Server 2016 reach end of life?

Extended support ended July 14, 2026. Mainstream support ended earlier, on July 13, 2021. This applies to Developer, Enterprise, Enterprise Core, Express, Standard, and Web editions.

Can I still get security updates for SQL Server 2016?

Only through paid Extended Security Updates, and only for Enterprise and Standard editions running SP3. ESUs cover Critical-rated MSRC updates only, for up to three years, through July 17, 2029. Express, Web, and Developer editions cannot subscribe at any price.

How much runway do ESUs actually buy?

Three years maximum: Year 1 runs July 15, 2026 to July 13, 2027; Year 2 to July 18, 2028; Year 3 ends July 17, 2029. There is no coverage of any kind after that date.

How do I buy SQL Server 2016 ESUs?

Via Azure Arc pay-as-you-go, or through volume licensing with active Software Assurance. Billing started at midnight UTC on July 15, 2026 for every eligible instance regardless of subscription date; subscribing later means a bill-back to the start of the term.

Are ESUs free on Azure virtual machines?

No. Unlike SQL Server 2014, Microsoft is not offering free ESUs for SQL Server 2016 on Azure VMs or Azure Stack. Running in Azure makes ESUs purchasable, not complimentary.

What about SharePoint farms running on SQL Server 2016?

SharePoint Server 2016 and 2019 reached end of support on the same date, July 14, 2026, but have no ESU program of their own. If SQL Server 2016 is your SharePoint content database engine, the database tier has a paid bridge and the application tier does not — see our SharePoint 2016 & 2019 EOL deep-dive for the full picture.