July 14, 2026, is the end of extended support for SQL Server 2016. After that date, Microsoft stops issuing security patches, bug fixes, and technical support for every edition, at every license level. The database keeps running. The safety net disappears.
If you’re an IT leader with SQL Server 2016 in your environment, this post covers the three realistic paths forward, the compliance exposure you’re taking on by waiting, and how to think through the decision when not every instance has a clean migration path.
Before You Plan: Find Every Instance
Migrations stall on inventory, not budget. SQL Server hides. It gets installed under applications, handed off between admins during staff changes, bundled into third-party software as SQL Express, and left running because it never breaks. Until it does.
Before evaluating options, you need a clear picture of what’s actually in your environment: every SQL Server 2016 instance, what application depends on it, and whether that application can move independently. That last point matters more than most teams expect. Some instances are locked to a vendor-controlled upgrade timeline, and you can’t upgrade the database without upgrading the app. Those need a different plan than the ones you own outright.
Start with the inventory. The rest of the decisions follow from there.
The Compliance Case
Running unsupported software is a liability under ISO 27001, SOC 2, PCI DSS, and most other major frameworks, all of which require current security patches. After July 14, SQL Server 2016 starts generating audit findings.
Cyber insurers have also started treating unpatched databases as a named risk category, which is worth flagging to leadership before a policy renewal rather than after an audit.
The real reason to act is security and operational continuity. The compliance angle just makes it easier to get the conversation on the calendar.
Three Paths Forward
Most environments don’t have a single right answer. Some instances can move quickly; others are tied to applications that need more time. The realistic plan is usually a mix, applied at the instance level rather than across the board.
1) Upgrade to SQL Server 2022 or SQL Server 2025
If staying on-premises is the goal, this is the straightforward path. Same infrastructure, same operational model, no cloud migration required.
SQL Server 2025 reached general availability in late 2025 and is the current release. It adds AI-native capabilities and real-time analytics that SQL Server 2016 can’t support, making it worth considering if your organization has active AI work on the roadmap. SQL Server 2022 is the proven, stable choice for shops that don’t need those features yet.
Both are available through TrustedTech. Straightforward migrations typically take 2 to 3 months; ones with significant application dependencies run longer. If this is your path, starting now is the right call.
On licensing: if your SQL Server 2016 licenses carry active Software Assurance, that coverage doesn’t automatically transfer to the new version, but SA does provide upgrade rights that affect how you license the next version. TrustedTech’s advisors can confirm what your existing SA covers before you buy anything new. It's worth having that conversation before committing.
2) Migrate to Azure SQL
Azure SQL is a fully managed service; Microsoft handles patching, high availability, and backups. For this discussion, the more relevant point is that it ends the EOL cycle. You stay on a supported version without managing that lifecycle yourself.
If cloud migration is already on your roadmap, SQL Server 2016 EOL is a practical forcing function for that work. Workloads on Azure SQL shift from perpetual licensing to consumption-based costs, which changes the CapEx/OpEx profile and warrants running past finance as part of the planning conversation.
This path requires more upfront architecture assessment than an on-prem upgrade. For workloads that are reasonably portable, it often results in a lower total cost over 3 to 5 years. For workloads with deep application dependencies, it may not be the right first move.
3) Extended Security Updates (ESU)
ESU is Microsoft’s bridge for organizations that won’t finish migrating before July 14. It covers only critical security patches; no new features, no bug fixes, no support calls. Coverage runs up to three years post-EOL, through July 2029, at escalating cost each year.
For instances that are genuinely stuck, tied to applications that can’t be re-platformed quickly, or where a rushed cutover creates more risk than the support gap, ESU makes sense. It buys time for a real decision.
ESU is available for on-premises SQL Server 2016 through Microsoft volume licensing and doesn’t require Azure Arc enrollment, which is a common misconception. TrustedTech doesn’t sell ESU directly, but our licensing advisors can walk through eligibility and what procurement looks like, so you’re not figuring it out alone.
One thing worth keeping in mind: three years of runway tends to feel long until it’s short. The teams that use ESU as a reason to defer the migration decision tend to land in 2029 with the same problem and less time to solve it.
Framing This for Leadership
Most IT directors bring SQL Server 2016 EOL to leadership as a compliance task. That framing tends to get it noted, not funded.
July 14 is one of the few IT deadlines with a genuine business consequence. As an on-ramp, it becomes the push for several conversations that normally stall: cloud migration work already on the roadmap, AI readiness (SQL 2022 and 2025 have integrations that 2016 doesn’t support), infrastructure cost work (migration surfaces overprovisioned instances and workloads that haven’t had a reason to be reviewed), and security posture improvements that matter to auditors and insurers.
The deadline is identical either way. The budget you get to address it is not.
Frequently Asked Questions
When exactly does SQL Server 2016 support end?
July 14, 2026. After that, Microsoft stops issuing security patches, bug fixes, and technical support for all SQL Server 2016 editions. ESU is available post-EOL through Microsoft volume licensing for up to three additional years.
Do I have to move to the cloud, or can I stay on-premises?
On-premises is a fully valid path. SQL Server 2022 and 2025 are both current, supported versions available on your own infrastructure. Azure SQL is worth considering for portable workloads, but it’s not a requirement. The right answer depends on your workloads, application dependencies, and where you want to be in a few years.
What is ESU and how do I get it?
Extended Security Updates cover critical patches for SQL Server 2016 after the EOL date, for up to three years, through Microsoft volume licensing. On-prem instances don’t need Azure Arc enrollment to qualify. TrustedTech doesn’t sell ESU directly, but can walk through eligibility and procurement with you.
What happens to my existing SQL Server 2016 licenses after EOL?
The perpetual licenses stay valid and the software keeps running. What ends is Microsoft’s support obligations. If your licenses include active Software Assurance, you have upgrade rights to a newer version. TrustedTech’s advisors can confirm what that actually covers before you buy anything new.
How long does a SQL Server 2016 migration take?
Straightforward upgrades to SQL Server 2022 or 2025 typically run 2 to 3 months. Migrations with significant application dependencies, or moves to Azure SQL, usually take 4 to 6 months in complex environments. Starting the discovery phase early gives you more realistic options.
Start With Inventory
July 14 is fast approaching. The teams that come out of this in good shape aren’t the ones with the cleanest environments; they’re the ones that started the inventory work early enough to make real decisions instead of forced ones.
TrustedTech’s licensing advisors work through this kind of assessment regularly: mapping existing SQL Server licensing, identifying what Software Assurance coverage actually entitles you to, and building a plan that accounts for the instances you can’t move immediately. If you don’t know where to start, that conversation is the place to.
