The short answer
- SQL Server 2016 end of support (EOL) was 14 July 2026, when extended support ended. Without Extended Security Updates, there are no more security patches.
- The quickest safe option is often to move the databases to Azure. SQL Server on Azure VMs gets ESUs at no extra charge, and Azure SQL Managed Instance removes version upgrades altogether.
- On-premises ESUs are available through Azure Arc for up to three years, but they're a paid bridge, not a fix.
- Check application vendor support first, as it usually decides the target.
When was SQL Server 2016 end of support?
| Version | End of extended support | Status in October 2026 |
|---|---|---|
| SQL Server 2014 | 9 July 2024 | Out of support |
| SQL Server 2016 | 14 July 2026 | Out of support |
| SQL Server 2017 | 12 October 2027 | Ending in 12 months |
| SQL Server 2019 | 8 January 2030 | Extended support |
| SQL Server 2022 | 11 January 2033 | Supported |
Option 1: Buy Extended Security Updates on-premises
ESUs for SQL Server 2016 are available through Azure Arc for up to three years after end of support. They need Software Assurance or a subscription licence and are billed as you go.
Use it for: a database whose application can't be upgraded or moved yet. Remember: it adds cost and doesn't fix the underlying hardware or version issue.
Option 2: Upgrade SQL Server 2016 to 2022
Upgrade to SQL Server 2022 on existing servers, in place or side by side.
Use it for: recent hardware, vendor-certified upgrade paths and teams comfortable owning the infrastructure. Remember: you'll need new licences if not covered, and you'll face the same question again in the 2030s.
Option 3: Move to SQL Server on an Azure VM
Lift the database to an Azure VM, keeping SQL Server 2016, and get ESUs at no extra charge while you plan an upgrade.
Use it for: a fast route back to a supported position, and applications that need OS-level access or specific SQL features.
Option 4: Move to Azure SQL Managed Instance
Migrate to a fully managed service that's always on a current, supported SQL Server engine. Microsoft handles patching, backups and high availability.
Use it for: most line-of-business databases where the vendor supports it. It ends the upgrade cycle for good.
Choosing quickly
| Your situation | Best option |
|---|---|
| Vendor supports Managed Instance | Azure SQL Managed Instance |
| Vendor requires a specific SQL version or OS access | SQL Server on Azure VM (ESUs included) |
| Server hardware is new and you want to stay on-premises | Upgrade in place |
| Can't change anything for 6–12 months | ESUs as a bridge, with a plan |
Next steps
- Inventory every SQL Server instance and version. Older versions often hide inside third-party products.
- Check vendor support for each application against Azure SQL Managed Instance and newer SQL versions.
- Run the Azure SQL migration assessment to find any compatibility blockers.
- Decide per database and include SQL Server 2017 in scope.
Wondering what SQL Server costs to run in Azure? Our Azure migration cost guide covers typical monthly costs. Our SQL Server migration service covers all four options. Get a free assessment to find the right one for your databases.
Frequently asked questions
When is SQL Server 2016 end of life?
SQL Server 2016 reached end of life on 14 July 2026, when its extended support ended. Mainstream support had already ended in July 2021. Since then, only organisations with Extended Security Updates receive security patches.
Is it safe to keep running SQL Server 2016?
Not without Extended Security Updates. Since 14 July 2026, newly discovered vulnerabilities in SQL Server 2016 are not patched for unprotected installations, which raises cyber and compliance risk, especially for databases holding personal or financial data.
What's the easiest way to get SQL Server 2016 back into support?
Moving it to an Azure VM is the fastest like-for-like option, because ESUs are included at no extra charge. You can then upgrade at your own pace. If the application supports it, Azure SQL Managed Instance is a better long-term home because it's always on a supported version.
Do I need to change my application to use Azure SQL Managed Instance?
Usually not. Managed Instance supports SQL Agent, cross-database queries, linked servers and CLR, so most line-of-business applications work unchanged. Run a compatibility assessment first to catch any blockers.
What about SQL Server 2017?
SQL Server 2017 extended support ends on 12 October 2027. If you're planning a SQL Server project now, include 2017 instances too so you don't repeat the exercise next year.