Microsoft SQL Server end of life
Microsoft has informed us all a while back that SQL Server 2016 exits extended support on July 14th 2026, and SQL Server 2017 is due to follow next year Oct 12th 2027. If you haven’t already done so, you should be making plans about what to do if you are currently running these versions of SQL Server.
Of course, in an ideal world, the choice would be simple, you would just upgrade to the latest and greatest version (now with AI), SQL Server 2025. Unfortunately, the real world rarely tends to be so easy. So, what are the questions that you need to answer to decide what to do? You really have three choices.
- Stay where you are
- Purchase Extended Security Updates
- Upgrade SQL Server
If you’re unsure which path is right for you, download our free migration guide at the bottom of the page to help your team choose the best route.
Stay where you are
The simplest choice, though one that extends your technical debt and introduces the complexities of managing a system that is no longer receiving security patches. It is also the one most likely to be driven by existing technical debt; maybe an application that no longer has vendor support, maybe an existing in-house system that you haven’t managed to replace yet. You should still patch to the latest available patch, and keep an eye out for those occasional GDRs that Microsoft finds important enough to back port to older & unsupported versions of SQL Server. Beyond that you need to be planning what the future looks like for this system.
Purchase ESU
The second option is to purchase an Extended Security Update (ESU). The expensive choice, for those who are stuck as above but who require to be on a “Supported Version” of their software. Maybe you’ve got Cyber Essentials Plus, maybe you are in a regulated industry? Microsoft has got your back, well temporarily. You can buy an annual ESU on top of your existing licence purchase, but only for the next three years, and it will cost you.
Microsoft recently cleaned up their ESU purchase model. Now ESU will cost you an additional 100% of your current licence costs each year that you have it, and you either need Software Assurance or an active Enterprise Subscription Agreement as well. Previous versions had an escalating price model, now its flat, and Azure and on prem cost the same. People who are on the legacy option using Azure that granted free ESUs will still benefit from those, but that is no longer an option for new purchasers.
ESU purchase model
| Version | Start Date | End Date | Cost |
|---|---|---|---|
| 2016 ESU Year 1 | 15 July, 2026 | 13 July 2027 | 100% of current licence |
| 2016 ESU Year 2 | 14 July, 2027 | 18 July 2028 | 100% of current licence |
| 2016 ESU Year 3 | 19 July, 2028 | 17 July 2029 | 100% of current licence |
And remember, ESUs are security fixes only, and you can only purchase a maximum of an additional three years of coverage. 2017 ESUs will look similar but run from October to October when they kick in.
Upgrade version
The most common choice, though not without its own considerations. What version? Do you have Software Assurance or do you have to buy extra licences? In place or side-by-side upgrade? Do all your applications support the same version? Are you using Enterprise features that have changed since 2016/2017? And when do you upgrade? With the tendency to host multiple, different application databases on a single instance (saving on licence costs), you now have multiple constraints on your planned upgrade.
Plan your next database upgrade or migration
Upgrading or migrating a database starts with asking the right questions. To help you navigate the process, we created a comprehensive guide packed with the essential diagnostic questions every team must answer. Combined with our simplified decision matrix, this guide helps you track your choices, evaluate your options objectively, and move forward with total confidence.
Download our Free Migration Guide
Discover key questions to ask your team and access our decision matrix to help you plan your next steps.
"*" indicates required fields
