SQL Server 2016 End of Support: Dates & Options

For teams that run SQL Server in production, July 14, 2026 was the date SQL Server 2016 end of support took effect. Extended support has ended. Microsoft no longer issues security patches for the product, and paid Microsoft assistance is no longer available for it. This page lists the verified dates, what changes in practice, and the three realistic options: upgrade, move to Azure, or continue running it with third-party support.

SQL Server 2016 end of life: the dates

SQL Server follows the standard Microsoft fixed lifecycle: roughly five years of mainstream support followed by roughly five years of extended support. Both phases have now closed for SQL Server 2016. The dates below are taken from the Microsoft Lifecycle page for SQL Server 2016.

One servicing detail worth knowing: only SQL Server 2016 Service Pack 3 (with the Azure Connect feature pack where applicable) was serviced through the final years of extended support. Earlier service pack levels fell out of support years before the 2026 date. An instance still on SP1 or SP2 stopped receiving patches long before July 2026.

What end of support means in practice

The instance keeps running. Nothing shuts off on the end-of-life date. What changes is the risk position:

• No security patches. New vulnerabilities found in the SQL Server 2016 engine will not be fixed by Microsoft, regardless of severity, unless you hold an ESU subscription. Vulnerabilities disclosed and patched in newer versions often apply to older shared code, which gives attackers a map of what to probe on unpatched instances.
• No Microsoft assistance. Microsoft support will not open cases for SQL Server 2016. If the engine corrupts a database or a cumulative update interaction breaks replication, there is no vendor escalation path.
• Compliance exposure. PCI DSS Requirement 6 requires that system components be protected from known vulnerabilities through vendor-supplied patches; software that can no longer receive vendor patches fails that test and must be documented with compensating controls at minimum. The HIPAA Security Rule requires covered entities to protect against reasonably anticipated threats to ePHI; running a database engine that cannot be patched is difficult to defend in a risk analysis, and HHS guidance flags unsupported software as a risk factor. Cyber-insurance questionnaires increasingly ask directly whether unsupported operating systems or databases are in use.
• Vendor certification drift. Application vendors drop certification for out-of-support database versions on their own schedules. New releases of the application may refuse to install against 2016.

Microsoft's own definition is in the SQL Server end of support options article: after extended support ends, no servicing and no support, with ESU as the only paid bridge.

Also recently ended, and what ends next

Dates for other versions: SQL Server 2014 lifecycle and SQL Server 2017 lifecycle. If you are consolidating multiple old instances, our SQL Server versions reference lists every version and date in one table. Note the 2017 date: an organization upgrading off 2016 in 2026 should not target 2017 or 2019, both of which are already past mainstream support.

Option 1: upgrade to SQL Server 2022 or 2025

The standard path. SQL Server 2016 supports a direct in-place upgrade to SQL Server 2022, and side-by-side migration (new instance, backup/restore or detach/attach the databases) works to either 2022 or 2025. Side-by-side is the safer pattern: it leaves a rollback target and lets you move databases in batches.

• Compatibility level. A database restored from 2016 keeps compatibility level 130. The engine runs it without modification, and Microsoft's compatibility certification means level 130 behavior is preserved on newer engines. You can upgrade the compatibility level later, after testing, to pick up newer optimizer behavior. This decouples the platform upgrade from application regression testing.
• What to test anyway. Linked servers, SQL Agent jobs, SSIS packages (project deployment model version), CLR assemblies (newer versions enforce stricter signing defaults), and any application connection strings using old drivers or TLS 1.0/1.1, which newer builds reject by default.
• 2022 vs 2025. SQL Server 2022 has mainstream support to January 2028 and extended to January 2033. SQL Server 2025 resets the clock to roughly 2031/2036. If the application vendor certifies 2025, take it; the versions are covered in our SQL Server 2025 overview.
• Licensing. Without Software Assurance, a new version means new licenses. Price this before choosing between upgrade and Azure, because for some workloads the license cost decides the question.

Option 2: move it to Azure

Two distinct destinations, with different consequences:

Azure SQL Managed Instance. A platform service with near-full SQL Server engine compatibility (SQL Agent, cross-database queries, CLR). It is versionless: Microsoft patches the engine continuously, so the end-of-support cycle stops applying at all. Migration runs through Azure Database Migration Service or a managed-instance link. Features that touch the OS directly (FILESTREAM, some cross-instance patterns) do not carry over; check the compatibility list before committing.

SQL Server on an Azure VM. Lift-and-shift of the existing installation. One correction to a common assumption: for SQL Server 2014 and earlier, Microsoft granted free Extended Security Updates to instances running on Azure VMs. That benefit does not extend to SQL Server 2016. Microsoft changed the ESU structure for 2016, and migrating a 2016 instance to an Azure VM no longer provides ESUs at no additional cost; you subscribe and pay, as documented in What are Extended Security Updates for SQL Server. ESUs cover only Critical-rated security fixes, no bug fixes and no feature work, and on-premises ESU pricing runs at roughly 75% of the license cost per year. The economics therefore favor either upgrading the version on the Azure VM or going to Managed Instance, rather than paying to keep 2016 alive in the cloud.

Option 3: continue running it with third-party support

Third-party support means a services firm, not Microsoft, takes responsibility for keeping the instance operable. Stated flat, this is what it covers and what it does not:

• Covered: monitoring, performance tuning, backup and restore verification, corruption response, failover management, security hardening around the engine (network isolation, restricted authentication, auditing), and escalation when the database breaks at 2 a.m.
• Not covered: engine security patches. No third party can write patches for Microsoft's binaries. A vulnerability in the 2016 engine stays open; the mitigation is isolation and compensating controls, not a fix.

This option fits a narrow case: an application that cannot be recertified on a newer version, is scheduled for retirement, and can be fenced off the general network. It is a way to run out the clock on a known-terminal system in a controlled manner, not a substitute for patching. Medha Cloud provides Microsoft SQL Server support for exactly this situation as well as for the upgrade and Azure paths above.

How to check what you are running

Run this against each instance:

SELECT @@VERSION;

Or, for structured output:

SELECT SERVERPROPERTY('ProductVersion'), SERVERPROPERTY('ProductLevel'), SERVERPROPERTY('Edition');

SQL Server 2016 reports a ProductVersion starting with 13.0. The final serviced build line is 13.0.7xxx (SP3 plus subsequent security updates). A ProductLevel of RTM, SP1, or SP2 means the instance fell out of servicing even earlier than the 2026 date. Also inventory SQL Server Express instances: Express follows the same lifecycle dates and is routinely installed silently by line-of-business applications, so unsupported 13.0 instances tend to surface in places nobody lists.

Decision table

FAQ

When did SQL Server 2016 reach end of life?

Extended support ended July 14, 2026. Mainstream support had already ended on July 13, 2021. Paid Extended Security Updates are available to eligible customers until July 17, 2029.

Does SQL Server 2016 stop working after end of support?

No. The software runs unchanged. The difference is that no new security patches are produced and Microsoft support is unavailable, which shifts the risk and compliance position rather than the functionality.

Are ESUs free if I move SQL Server 2016 to an Azure VM?

No. The free-ESU-in-Azure benefit applied to SQL Server 2014 and earlier. For SQL Server 2016, ESUs on Azure VMs are a paid subscription. Azure SQL Managed Instance avoids ESUs entirely because the platform is versionless.

Should I upgrade to SQL Server 2019 instead?

No. SQL Server 2019 left mainstream support in February 2025 and reaches end of support in January 2030. An upgrade performed in 2026 should target SQL Server 2022 or 2025.