SQL Server 2016 reached the end of extended support on 14 July 2026, with the final Cumulative Update released on that date. Mainstream support ended back in 2021. Under standard terms, Microsoft will provide no further security patches, bug fixes or technical support.
Despite that, SQL Server 2016 is still heavily deployed across ERP, billing and other line-of-business systems. Plenty of organisations are still running critical workloads on it, which creates both a risk and an opportunity.
Why you need to act now
Running unsupported SQL Server 2016 exposes the business to unpatched vulnerabilities, compliance gaps and rising operational risk. The obvious next step is an upgrade to SQL Server 2022 or 2025, but that is rarely straightforward. The real impediments are almost always the application and its dependencies, not the database engine itself.
Alternative paths exist, and each carries a clear limitation:
- Pay-as-you-go licensing through Azure Arc, combined with Extended Security Updates (ESUs), can buy time without an immediate upgrade. It is an expensive three-year bridge, and it delivers critical security fixes only, not full product support.
- Lifting SQL Server 2016 onto an Azure Virtual Machine no longer qualifies for free ESUs, which is now Microsoft’s stated position.
- A commercial SLA for operational continuity, for organisations that genuinely need more time. First Digital provides ongoing monitoring, incident response, performance support and operational management while ESUs cover critical security patches. It is designed as a controlled, time-boxed bridge, typically 12 to 36 months, not a permanent answer.
Doing nothing is no longer viable, and the cheapest or quickest-looking option often creates more cost and complexity later.
Turning the deadline into an opportunity
A SQL Server 2016 estate is worth treating as the entry point to a wider Azure and modernisation conversation, rather than a licensing renewal exercise. The database version is the trigger. The question underneath it is what your application estate should look like for the next five years.
If you need breathing space first, the operational continuity SLA above is the controlled way to take it: stable, supported day-to-day operations while ESUs handle critical security updates, with a fixed end date so the bridge does not quietly become the destination.
Two things we would recommend before you commit to any path:
1. Run a proper end-of-life and application compatibility assessment first. It surfaces the true blockers early and prevents costly false starts. Choosing a path before you know what your applications can tolerate is how upgrade projects stall halfway. 2. Frame the decision around the full modernisation journey, not a narrow database upgrade. That opens up Azure-native options, better cost control and longer-term resilience. It also gives you a clear, accurate basis for any Microsoft funding discussion, since those programmes are assessed against the wider migration rather than the database alone.
Get in touch with First Digital for an assessment of your SQL Server estate, or a conversation about which of these paths fits your business.
