If your accounting package, ERP system or a piece of internal line-of-business software still runs on SQL Server 2016 in the background, a date on Microsoft's own lifecycle calendar now matters to your business whether or not anyone on your team has looked at it: 14 July 2026. That is when SQL Server 2016 reaches the end of its support lifecycle, and the practical consequences are more immediate than most SMEs assume.
This guide covers what "end of support" actually means for SQL Server 2016, the real options Microsoft itself lists for what comes next, what Extended Security Updates cost and do not cover, and what to check before you decide.
What "end of support" actually means
Every version of SQL Server ships with a fixed support window: five years of mainstream support, covering functional updates, performance improvements and security fixes, followed by five years of extended support, covering security fixes only. Once that ten-year window closes, Microsoft stops servicing the product entirely — no more patches, no more security updates.
For SQL Server 2016, that window closes on 14 July 2026. The part that catches most IT teams off guard is not the loss of patches, it is the loss of support itself: once a version is out of support, you cannot open a support ticket for it, even if your organisation has an active support plan. If something breaks in production after that date, Microsoft's own documentation is explicit that there is no ticket to log — your options are to have already moved, or to be paying separately for Extended Security Updates, which is a different, narrower kind of coverage described below.
This is not a hypothetical for the Dutch market. SQL Server 2016 has been a common backend for on-premises line-of-business software for a decade, and unlike an office productivity upgrade, swapping out a database platform underneath a working application is not something most SMEs can do on short notice.
Your four real options
Microsoft's own end-of-support guidance lays out four paths once a version reaches this point, and they trade off cost, effort and how long the fix actually lasts:
| Option | What it involves | Best fit |
|---|---|---|
| Upgrade on-premises | Move your existing databases to a current, supported version of SQL Server on your own hardware | You want to keep full control of the environment and are willing to invest in new licensing and infrastructure |
| Move to a managed cloud database | Migrate to a fully managed platform-as-a-service database that Microsoft describes as never reaching end of support on its own | You want to stop tracking database lifecycle dates altogether and can accept some compatibility differences from on-premises SQL Server |
| Lift-and-shift to a cloud virtual machine | Move the existing SQL Server instance, as-is or upgraded, onto a virtual machine in the cloud | You need OS-level access or have dependencies that a fully managed database service does not support |
| Subscribe to Extended Security Updates | Stay on SQL Server 2016 exactly as it is, and pay for continued critical security patches | You need more time to test an upgrade path and cannot move by July 2026 |
The first three all get you back onto a version that keeps receiving full support. The fourth does not — it buys time, nothing more, and it comes with real limits worth understanding before you treat it as your plan.
Extended Security Updates: a bridge, not a destination
Extended Security Updates (ESUs) let you keep running SQL Server 2016 exactly as it is today while still receiving certain security patches. Several details determine whether this is actually a workable bridge for your business:
What ESUs cover, and what they don't. ESUs only include security fixes that Microsoft's Security Response Center rates as Critical. They explicitly exclude new features, functional improvements and customer-requested fixes — an ESU subscription freezes your SQL Server 2016 installation in place and patches only the most severe vulnerabilities in it. A non-critical bug you hit in production will not get fixed under this program.
Who is eligible. Only the Enterprise and Standard editions of SQL Server 2016 qualify for ESUs. If you are running Express, Web or Developer edition in production, this bridge is not available to you at all — Microsoft's guidance points those environments straight to an upgrade.
What it costs. Microsoft prices standalone on-premises ESUs at approximately 75% of your existing on-premises licence cost, per year. That is a recurring bill for a product that gains no new capability while you pay it — it is priced as a delay, not a service.
What it requires. To buy ESUs on-premises, you need active Software Assurance under an Enterprise Agreement, an Enterprise Subscription Agreement, a Server & Cloud Enrollment or an Enrollment for Education Solutions. Without Software Assurance, the alternative route is connecting your SQL Server instance to Azure Arc and paying for ESUs on a pay-as-you-go basis instead.
How long it lasts, and when billing starts. ESUs for SQL Server 2016 run for a maximum of three years, through 17 July 2029, after which there is no further extension — Microsoft's own documentation is clear this option does not apply to versions any older than SQL Server 2014. If you subscribe before the deadline, billing on Azure starts automatically at midnight UTC on 15 July 2026, the day after support ends.
The catch specific to SQL Server 2016. If you are used to how this worked for the previous end-of-support version, SQL Server 2014, be aware the terms changed. Migrating a SQL Server 2014 instance to a cloud virtual machine as-is used to come with free ESUs. That is no longer true for SQL Server 2016: moving a SQL Server 2016 instance to a cloud VM as-is still requires a paid ESU subscription. Lifting and shifting to the cloud does not, by itself, solve the support question for this version — you either upgrade the SQL Server version during that move, or you keep paying for ESUs regardless of where the server physically runs.
What to check before you decide
- Which applications actually depend on this instance. Map every application, reporting tool, scheduled job and integration that talks to the SQL Server 2016 database before you touch anything — a database that "just runs the accounting system" often turns out to also feed three other tools nobody thought to check first.
- Whether your applications will tolerate an upgraded database compatibility level. Moving to a newer SQL Server version, on-premises or in the cloud, generally keeps existing applications working as long as the database compatibility level stays the same; an application typically only needs full recertification if you deliberately raise that setting to use newer database features.
- Whether your Windows Server underneath has its own clock running. Database platform lifecycle and operating system lifecycle are two separate clocks that often get replaced together — check the Windows Server version your SQL Server 2016 instance runs on independently, rather than assuming it is covered by whatever you decide for the database.
- How much runway you realistically have. Testing an upgrade path, validating that reports and integrations still work, and running a staged rollout all take real time. Treat July 2026 as the date by which migration needs to be *finished*, not the date by which you start planning.
Common mistakes
- Assuming a support contract still gets you a ticket after the deadline. It does not. Being out of support means exactly that, regardless of what support plan you are paying for elsewhere.
- Treating ESUs as a long-term fix. Three years, critical-only patches, no new features: ESUs are priced and scoped as a bridge to buy migration time, not as an alternative to migrating.
- Assuming a cloud lift-and-shift automatically restores support. For SQL Server 2016 specifically, moving to a cloud VM as-is still needs a paid ESU subscription — only upgrading the SQL Server version, or moving to a managed database service, gets you back to full support without one.
- Discovering dependent applications after the migration starts. A rushed inventory is how a "simple database upgrade" turns into unplanned downtime for systems nobody realised were connected.
FAQ
When does support for SQL Server 2016 actually end? 14 July 2026. After that date, Microsoft no longer issues security patches for the base product, and you cannot open a support ticket for it even with an active support plan.
Can I still get help from Microsoft after the deadline if something breaks? Only if you have subscribed to Extended Security Updates, and even then support is limited to issues related to the ESU patches themselves, not general troubleshooting of the underlying SQL Server 2016 installation.
What do Extended Security Updates actually cost? Microsoft prices standalone on-premises ESUs at roughly 75% of your existing on-premises licence cost per year, available for a maximum of three years, through 17 July 2029, and limited to Critical-rated security fixes only.
Does moving to the cloud automatically solve this for SQL Server 2016? Not by itself. Unlike the previous end-of-support version, migrating a SQL Server 2016 instance to a cloud virtual machine as-is no longer comes with free Extended Security Updates — you still pay for the ESU subscription unless you upgrade the SQL Server version as part of the move, or migrate to a managed database service instead.
Is SQL Server 2016 the only version SMEs need to worry about? No. SQL Server 2014 reached its own end of support earlier, on 9 July 2024, with ESUs for that version available through 8 July 2027. If your environment has a mix of older SQL Server versions, each one is on its own separate lifecycle clock.
Get your database inventory sorted before July 2026
Not sure which of your applications actually depend on that SQL Server 2016 instance, or which of the four options fits your setup? Our Data & Databases team can map the dependencies and scope a realistic migration path. If the better answer for your business is moving the workload into the cloud entirely, our Cloud & Infrastructure team can walk through what that migration actually involves.