SQL Server 2016 support has ended. What now?
Extended support for Microsoft SQL Server 2016 ended in July 2026. This older database platform will, of course, continue to function, but the end of support changes the conditions under which companies should plan its continued operation and security and consider a potential upgrade.
The end of extended support for Microsoft SQL Server 2016 during the summer effectively means that this database platform no longer receives standard security updates or regular product support from Microsoft. At the same time, there is no reason to panic. Rather, this is a point at which companies should decide what to do next.
There is no need to act hastily or automatically migrate to the latest available version. A more sensible first step is to map the current environment, application dependencies and the company’s plans for the coming years. The resulting decision may be to keep SQL Server 2016 in operation for a limited period, prepare a migration to the newer SQL Server 2019 or SQL Server 2022, or move to the latest 2025 version.
End of support does not mean the end of operation
The term end of support does not mean that the product stops functioning. Databases, applications and their integrations may continue to work after the end-of-support date in July 2026 in the same way as before. What changes is the level of support and the security conditions under which the organisation operates the software.
Microsoft has ended extended support for SQL Server 2016, which means that unless a company uses the Extended Security Updates (ESU) programme, this version will no longer receive new security updates as standard. The ESU programme provides critical security updates for a further three years, specifically until 17 July 2029.
It is important to understand, however, that ESU does not provide any new features or standard non-security fixes, nor does it replace regular product support. For some organisations, it may nevertheless be a suitable transitional solution, particularly where key applications do not yet support a newer SQL Server version or where migration is part of a larger project. The additional time should, however, still be used to prepare the next step rather than simply postpone the decision.
When and how to upgrade
If SQL Server 2016 is part of a stable environment and supports applications that cannot be changed quickly, it may be appropriate to address interim security first and then gradually prepare for modernisation.
The situation is different for a system that the company intends to operate for another five years or more. In such a case, postponing the upgrade may only extend technical debt and increase both the costs and risks of a future change.
Before choosing a specific version, it is useful to clarify several practical considerations:
How long do we want to continue operating the current database system?
Which applications depend on SQL Server, and which versions do their vendors support?
Which version of Windows Server is the database running on, and are we planning to change it?
Do we need new features, higher performance or longer support, or is our main objective secure and stable operation?
Licensing is also important. The optimal option may vary depending on the number of cores in use, the number of users, the selected SQL Server edition and the extent of virtualisation. It is therefore not appropriate to compare only the price of a single licence without considering the entire technical and licensing environment.
SQL Server 2019 or 2022?
If a company decides to upgrade, it does not automatically have to choose the latest version. SQL Server 2019 can be a practical option where compatibility with existing applications is the main priority, where the company wants to make a more conservative change to its environment, or where it is planning another major modernisation within a shorter timeframe. Microsoft provides extended support for SQL Server 2019 until 2030.
SQL Server 2022 offers an even longer lifecycle. Its mainstream support continues until 2028 and extended support until 2033. If an organisation is therefore investing in an environment that it intends to operate for many more years, the length of support is one of the strongest arguments in favour of this version.
The end-of-support date alone, however, is not enough to make the decision. The target version must also be supported by the applications in use, must fit the existing infrastructure, and its deployment must make sense from a licensing perspective. The differences between SQL Server 2019 and SQL Server 2022 therefore cannot be reduced simply to the question of which option is newer or more cost-effective. What matters is which version best fits the company’s specific situation (more in a separate article).
An upgrade does not necessarily mean replacing the entire infrastructure
Moving to a newer SQL Server version does not automatically mean that a company must also replace Windows Server, its hardware or its entire virtualisation platform. According to Microsoft’s current documentation, SQL Server 2019 and SQL Server 2022 can both run on Windows Server 2016, 2019, 2022 and 2025.
Modernisation can therefore be divided into several stages. The database layer and applications can be addressed first, followed later by a decision about the future of the server operating system or hardware. This approach can reduce project risk, allow for more thorough testing and spread investment over time.
Start with your needs, not the version number
So what should you do if you are still using Microsoft SQL Server 2016? The first step should be to identify the exact version, edition and Service Pack of the SQL Servers in use and verify which databases and applications are actually running on them. It is then advisable to confirm with the vendors of key applications whether they support SQL Server 2019, SQL Server 2022 or, potentially, the latest SQL Server 2025.
At the same time, the company should determine whether it is looking for a transitional solution for the next two to three years or wants to build a platform for the next five, seven or more years. The overall comparison should include not only the licence purchase price, but also the costs of migration, infrastructure, virtualisation, the required edition and future operation. If the organisation remains on SQL Server 2016, it should have a clear security plan and a specific date for the next decision so that a temporary situation does not become a permanent problem.
Forscope offers SQL Server 2019, SQL Server 2022 and SQL Server 2025 and can help you identify a solution based on your actual requirements. The aim is to propose an option that is technically viable, properly licensed and economically reasonable.