SQL Server 2016 Is Past End of Life: Read the ESU Meter
Support ended 14 July 2026 and Extended Security Updates run to 17 July 2029. The escalating 75/150/300 percent table everyone quotes is not what the Azure meter charges, and waiting to subscribe does not save you a dollar.
Extended support for SQL Server 2016 ended on 14 July 2026. Microsoft’s own ESU FAQ puts the paid bridge at three years past that, ending 17 July 2029, and the meter started running at midnight UTC on 15 July.
Nothing shut off. Your instances still start, still accept connections, still take backups. What changed is that Microsoft ships nothing for them now, and that you can no longer open a support ticket at all, even with a paid support plan.
Most of what is written about this decision quotes a table of escalating percentages: 75 percent of your license cost in year one, 150 in year two, 300 in year three. That table describes the Volume Licensing program. It is not what the Azure meter charges, and if you plan a budget from it you will be wrong in both directions.
What the meter actually says
Prices below came off the Azure retail price API on 23 August 2026, which is the same feed the pricing page renders from.
| Meter | Rate | Per core, per month (730 hours) |
|---|---|---|
Ent edition - ESU 2016 | $0.74 / hour | $540.20 |
Std edition - ESU 2016 | $0.19 / hour | $138.70 |
Two things follow from that. The first is the minimum: ESU usage is metered on every core visible to the operating system environment, with a floor of four cores per OSE. So the smallest possible Standard bill is about $555 a month and the smallest possible Enterprise bill is about $2,161, no matter how small the box is. Standard is capped at 24 cores; Enterprise is not capped.
The second is what the rate does over time. The SQL Server 2014 meters carry exactly the same numbers, $0.74 and $0.19. SQL Server 2014 went out of support on 9 July 2024, which puts it in its third and final ESU year right now. If the Azure subscription escalated year over year the way the Volume Licensing table does, the 2014 rate would be several times the 2016 rate today. It is identical. The subscription is a flat hourly meter, and the escalation story does not apply to it.
Waiting does not save money
This is the part worth acting on. Subscribe after the end-of-support date and your next bill includes a one-time bill-back charge to the first day of the ESU year, based on the timestamp when you enabled it. The FAQ is explicit about it.
So an eight-core Enterprise instance switched on today is already looking at roughly 39 days of retroactive charge, around $5,500, on top of the ongoing meter. Every week of deliberation costs the same as a week of coverage without any of the coverage. The only thing delay buys you is exposure.
The flip side is that cancellation is genuinely clean. Charges stop the same hour you unsubscribe, they stop automatically when you migrate to Azure SQL (and you keep receiving updates after that), and they stop automatically when you upgrade the engine. There is no term, no penalty. If you were treating ESU as a commitment to avoid, it is closer to a tap.
Eligibility gates that catch people
Only Enterprise and Standard editions can subscribe. Express, Web, and Developer cannot, at any price. If your 2016 footprint is a pile of Express instances holding up internal tools, there is no paid bridge for them and the only paths are upgrade or retire.
You also need active Software Assurance under an EA, EAS, SCE, or EES enrollment, or you can skip that by connecting the instance to Azure Arc and setting the license type to pay-as-you-go. A perpetual license with no SA and no Arc connection qualifies for nothing. Connecting to Arc is itself free.
One gate is easy to miss until the first patch fails: ESUs are only built against the latest Service Pack. If your 2016 instances are sitting on SP2, install SP3 and the current cumulative update now, while there is no urgency, rather than during the week a critical CVE lands.
Two things are free once you have a production subscription. Passive replicas in an availability group or failover cluster instance are detected and billed at zero, and Developer edition instances get the patches without generating a meter as long as some production subscription is active.
The Azure VM shortcut is closed for this version
You will still find advice saying that lifting the instance onto an Azure VM gets you ESUs for free. That was true for SQL Server 2014 and Microsoft changed it for 2016. A 2016 instance on an Azure VM can subscribe through the SQL IaaS Agent extension, at the same rate as everywhere else. The same holds for Azure Stack and for Azure VMware Solution: free for 2014, purchasable for 2016.
Azure SQL Managed Instance is the option that actually ends the cycle, because there is no version to age out. It is also a real migration project with its own compatibility surface, so it is a decision about the next three years rather than a way to handle this month.
If you are staying on premises
Two billing shapes exist and picking the wrong one is expensive. The default meters every virtual core on the machine. The alternative is a physical-core license resource covering a host and every VM on it, which is worth it when you have several out-of-support instances packed onto one host. That resource always bills on the Enterprise meter and has a 16-core minimum, so it starts around $8,640 a month and only makes sense above roughly six Enterprise VMs.
Watch the machine identity. Azure Arc keys the subscription to the VMID, and a rebuild, clone, or rename can generate a new one. When that happens the old resource keeps billing while the new one triggers a fresh bill-back, so you pay twice. Unsubscribe before any operation that might change it.
Where the upgrade actually hurts
The engine jump is calmer than its reputation. Databases keep their existing compatibility level when you move them, so a database at level 130 stays at 130 on a 2022 or 2025 engine and the optimizer behaves the way your application already expects. Raise the level later, deliberately, after you have watched for plan regressions. Changing the engine and the compatibility level in the same window is how a routine upgrade turns into a bad week.
The drivers are where it breaks. SQL Server Native Client (SQLNCLI, SQLNCLI11) and the legacy OLE DB provider (SQLOLEDB) are long deprecated, and everything should be on MSOLEDBSQL. Linked servers, SSIS connection managers, and application connection strings written years ago are the three places that still reach for the old ones. Grep for those strings before you plan anything else, because the count you find determines whether this is a two-week job or a quarter.
On the target: SQL Server 2022 carries extended support to 11 January 2033, and SQL Server 2025, released 18 November 2025, runs to 6 January 2036. Three extra years is worth something if the application clears both. For a plain “get off 2016” move with no interest in the vector and AI features, 2022 has three more years of production mileage behind it.
The number that decides it
Take your core count, multiply by $540.20 for Enterprise or $138.70 for Standard, and that is what a month of standing still costs. Compare it to a quote for the upgrade work. For a single eight-core Standard instance that is about $1,110 a month, and a year of it buys a real migration twice over. For a four-core Enterprise instance it is $2,161 a month and the arithmetic stops being close.
Then add the bill-back you have already accrued since 15 July, because that part is owed whether you subscribe this week or in November.