> ## Content Index > Fetch the complete content index at: https://www.techielass.com/llms.txt > Use this file to discover other available public pages before exploring further. # SQL Server 2016 End of Support: ESU dates, pricing and what to do next - URL: https://www.techielass.com/sql-server-2016-end-of-support-esu-dates-pricing-and-what-to-do-next/ - Published: 2026-08-27T07:01:39.000Z - Updated: 2026-08-27T07:01:39.000Z - Description: SQL Server 2016 hit end of support in July 2026. Here's what ESU actually costs (75%β†’150%β†’300%), and how to find out what's in your estate first. - Author: Sarah Lean - Tags: Azure Arc, SQL Server July 14, 2026 has come and gone. If you're still running SQL Server 2016, the deadline isn't a warning on a lifecycle page anymore, it's your current reality. Nothing crashed on July 15th. Your instances are still taking connections, your jobs are still running, and that's exactly the problem: an unsupported database doesn't announce itself. The risk just quietly accumulates from here. Here's where things actually stand, and what it's going to cost you to buy more time. ## **What changed on July 14th** SQL Server 2016 has reached the end of its 10-year support lifecycle. As of that date: - No more security updates - No more bug fixes - No more Microsoft support cases for the product - Every new vulnerability found in the 2016 codebase from now on stays open, permanently, unless you're paying for Extended Security Updates (ESU) πŸ’‘ ****One date people keep merging that shouldn't be merged:** SQL Server 2016 and Windows Server 2016 do not share a deadline. SQL Server 2016 support ended July 14, 2026\. [Windows Server](https://www.techielass.com/tag/windows-server/) 2016 doesn't hit its final security update until January 12, 2027\. If you've got a box running both, you're managing two separate lifecycle clocks on the same hardware, about six months apart, plan for both, not one. ## **ESU: A bridge, NOT a destination** Microsoft's Extended Security Updates (ESU) program gives you up to three more years of *critical* security patches only, no bug fixes, no new features, no general support. Coverage runs through **July 17, 2029**, split into three annual terms you buy separately: | **ESU Year** | **Coverage Window** | | ------------ | --------------------------- | | **Year 1** | Jul 15, 2026 – Jul 13, 2027 | | **Year 2** | Jul 14, 2027 – Jul 18, 2028 | | **Year 3** | Jul 19, 2028 – Jul 17, 2029 | Only Enterprise and Standard editions on the latest service pack qualify. If you've got 2016 Express instances tucked inside vendor appliances or under someone's desk, and let’s face it we’ve all seen that, there's no ESU option for them at any price. That's an upgrade-or-retire decision, full stop. ## **The pricing is not flat** This is the part that catches people out, and it's worth being precise about because the numbers are steep: ESU pricing for SQL Server 2016 is **not** a flat annual rate. It escalates every year: | **ESU Year** | **Cost** | | ---------------------------- | --------------------------------------- | | Year 1 (Jul 2026 – Jul 2027) | 75% of the current license price | | Year 2 (Jul 2027 – Jul 2028) | 150% of the current license price | | Year 3 (Jul 2028 – Jul 2029) | 300% of the current license price | | **Three-year total** | **525% of your original license price** | Run that against real numbers and it hurts. A SQL Server Enterprise 2-core pack that costs roughly $12,850/year at list price means Year 3 alone could run north of $38,000 per 2-core pack, before you factor in however many cores you're actually licensing. By the time you're through all three years, you've spent more than **five** times the price of a brand-new license just to keep receiving critical-only patches on a decade-old engine, with zero new capability to show for it. ## **What's new with pricing** Historically, running an out-of-support SQL Server on an Azure virtual machine (VM) got you Extended Security Updates for free, that was the deal for SQL Server 2014, and it's still the deal for 2014 today. People reasonably assumed the same logic would carry over to 2016. It doesn't. Because [SQL Server](https://www.techielass.com/tag/sql-server/) 2016's ESU program started as a new cycle after Microsoft's April 1, 2026 pricing-consistency change took effect, it's subject to the new model: **the same list price applies whether you're running in Azure, on-premises, or on another cloud.** The free-ESU-in-Azure perk that applied to earlier products doesn't extend to 2016. ## **How to actually buy it** There are two practical routes: - **SQL Server enabled by Azure Arc** β€” connect the instance (Azure VM, on-prem, or another cloud), turn on the ESU subscription through the SQL Server Configuration pane, and it bills as pay-as-you-go. [Azure Arc](https://www.techielass.com/tag/azure-arc/) registration is required for this path regardless of where the workload runs. - **Volume Licensing** β€” an annual purchase for eligible licenses with active Software Assurance. Even if you buy through Volume Licensing, Azure Arc registration is still required to activate ESU access. If you subscribe before July 14, 2026 passed, billing started at the beginning of the ESU term. If you're only sorting this out now, expect a one-time bill-back charge to the start of the current ESU year on top of your first invoice, signing up late doesn't mean you skip the backdated cost. ## **The plan should be modernisation** ESU buys you time, not a future. By Year 2 or 3 you're paying more for patches-only coverage than it would have cost to actually upgrade, with no performance gains, no new features, and every security issue that isn't rated "Critical" going unaddressed indefinitely. Here's the bit most teams skip, and it's the bit that makes everything above actually actionable: you can't make a sensible ESU-vs-modernise call until you know exactly what's sitting in your estate. Not the spreadsheet someone updated eighteen months ago, the real picture. How many SQL Server 2016 instances do you have, where are they, what edition, what patch level, and which ones are quietly Express and therefore not even eligible for ESU? The fastest way to get that picture is to onboard your on-prem (and other-cloud) servers to Azure Arc, then deploy the free Power BI dashboard from Azure Jumpstart:[ https://jumpstart.azure.com/azure\_jumpstart\_drops?drop=Arc%20Insights%20PBI%20Dashboards%20Powered%20by%20Jumpstart&fs=true](https://jumpstart.azure.com/azure%5Fjumpstart%5Fdrops?drop=Arc%20Insights%20PBI%20Dashboards%20Powered%20by%20Jumpstart&fs=true&ref=techielass.com) ![Server Inventory PowerBI Repor](https://storage.ghost.io/c/08/96/08960c71-63a2-449b-91b1-8d4628166dd2/content/images/2026/08/image.png) Server Inventory PowerBI Repor The dashboard will gives you a single view of your inventory: OS and SQL Server versions across the estate, which machines are already out of support or heading that way, and a rough sense of what ESU is going to cost you versus what modernisation looks like for both your Arc enabled servers and Azure servers. Do this before you sign anything, not after. Knowing the actual scale of the problem is what turns "we should probably look at ESU" into an actual, defensible decision. ## **Takeaways** - **The deadline has passed** β€” this is operational reality now, not a planning exercise. - **ESU is critical-patches-only and escalates fast**: 75% β†’ 150% β†’ 300%, for 525% total across three years. - **Azure no longer gives SQL Server 2016 a free pass** β€” pricing is consistent everywhere, unlike the SQL Server 2014 ESU program. - **Windows Server 2016 has its own deadline** (January 12, 2027) β€” don't assume one plan covers both products on the same box. - **Express edition has no ESU path at all** β€” find those instances now if you haven't already. - Treat ESU as breathing room to execute a migration plan, not as a long-term operating model.