SQL Server 2016 End of Support: What Happens After July 14, 2026

Published: November 7, 2026 | Updated: November 7, 2026

Last reviewed: November 2026. Microsoft can change prerequisites and SQL Server servicing guidance, so confirm current requirements before changing a production database environment.

SQL Server 2016 end of support arrived on July 14, 2026, when the product’s extended support phase finished. That date ended Microsoft’s servicing commitment for SQL Server 2016; it did not stop your databases from starting, answering queries or running backups.

The real questions are more practical. Is your SQL Server 2016 instance now a security risk? Can you still get patches through Extended Security Updates? Should you move to SQL Server 2022 or SQL Server 2025, and can you upgrade in place or do you need a new server?

The answer also depends on two separate things that are easy to mix up: the SQL Server version and the Windows Server version underneath it. Each has its own lifecycle, and the newest SQL Server release no longer installs on Windows Server 2016.

This guide explains what the SQL Server 2016 end of support date means, what still works, which options Microsoft offers, and how to choose a sensible next step for a small business server or a larger estate.

SQL Server 2016 End of Support: Quick Answer

Here is the current position as of November 2026:

• SQL Server 2016 reached the end of extended support on July 14, 2026.
• Mainstream support had already ended on July 13, 2021.
• Service Pack 3 (build 13.0.6300.2) is the final service pack.
• Microsoft offers paid Extended Security Updates (ESUs) for up to three years, through July 2029.
• ESUs require Software Assurance or subscription licensing, so a standalone perpetual license does not qualify.
• SQL Server 2016 SP3 can upgrade in place to SQL Server 2019, 2022 or 2025.
• SQL Server 2025 requires Windows Server 2019 or later; SQL Server 2022 still supports Windows Server 2016.

In short, the software still runs after SQL Server 2016 end of support, but without ESUs it no longer receives security fixes, so the risk grows with every month it stays exposed.

Is SQL Server 2016 Still Supported?

No. SQL Server 2016 follows Microsoft’s Fixed Lifecycle Policy, which means a published start date, roughly five years of mainstream support and five years of extended support. Both phases have now ended.

A quick definition of each phase:

• Mainstream support: functional, performance, scalability and security updates.
• Extended support: security updates only.
• Extended Security Updates: a paid bridge that delivers critical security fixes after extended support ends.

Microsoft’s official SQL Server 2016 lifecycle page lists these dates along with the covered editions: Developer, Enterprise, Enterprise Core, Express, Standard and Web.

SQL Server End-of-Support Dates by Version

SQL Server 2016 end of support is easier to plan around when you see it next to the newer releases:

If you are moving off SQL Server 2016 today, SQL Server 2022 and SQL Server 2025 are the only versions still in mainstream support.

SQL Server 2017 is worth a second look if you run it alongside 2016. Its extended support ends in October 2027, so upgrading straight to 2017 would mean doing the same project again in about a year.

What Changed After the SQL Server 2016 End of Support Date?

The change is about servicing, not functionality. Microsoft states that end of support means the product has reached the end of its lifecycle and Microsoft no longer provides servicing or support for it.

In practical terms, the SQL Server 2016 end of support date means:

• No new security updates unless you subscribe to ESUs
• No cumulative updates or bug fixes
• No standard Microsoft technical support cases
• No new compliance certifications for the version
• Growing gaps with newer drivers, tools and application vendors

Microsoft’s final public updates before SQL Server 2016 end of support were SP3 GDR releases from July 2026 (General Distribution Releases, which contain security fixes only), including build 13.0.6500.1. If your instance reports an older SP3 build, it is missing the last free fixes and should be patched before anything else.

Does End of Support Mean SQL Server 2016 Will Stop Working?

Usually not. There is no kill switch. A licensed SQL Server 2016 instance keeps running, keeps its databases online and keeps accepting connections after July 14, 2026.

What stops is the safety net:

• Security vulnerabilities found from now on stay unpatched without ESUs
• Auditors and cyber-insurance questionnaires may flag the version
• Application vendors may stop certifying new releases on it
• Microsoft support will not troubleshoot it under standard support

SQL Server 2016 end of support also has a neighbor to watch, because the operating system has its own clock. Windows Server 2016 extended support ends on January 12, 2027, so a SQL Server 2016 box on Windows Server 2016 is about to lose security updates on both layers. Bcdkey’s guide to Windows Server 2016 End of Support covers that side of the stack.

A database server that works perfectly today can still be the oldest, least-patched machine on the network. Those two facts are not in conflict; they just tend to meet at the worst possible moment.

What Are Your Options After SQL Server 2016 End of Support?

Microsoft’s end-of-support guidance describes three broad paths. Which one fits depends on your licensing, your applications and how much change your team can absorb.

1. Upgrade On-Premises to SQL Server 2022 or 2025

This is the most common route for small businesses. You install a supported version, either in place or on a new server, and keep the database on hardware you control.

It needs a new SQL Server license. Your SQL Server 2016 key does not activate SQL Server 2022 or 2025.

2. Buy Extended Security Updates

ESUs push back the security side of SQL Server 2016 end of support, but they buy time rather than solve the problem. Microsoft releases them only when a vulnerability is rated Critical, so there is no regular monthly cadence and no new features or general bug fixes.

Microsoft states that only customers with Software Assurance or subscription licenses can use ESUs, and that they cost roughly 75% of the on-premises license price each year. Instances connected to Azure Arc can subscribe and are billed hourly.

One change catches people out: moving SQL Server 2016 to an Azure virtual machine no longer gives you free ESUs, unlike earlier versions.

3. Migrate to Azure SQL

Azure SQL Managed Instance and Azure SQL Database remove the version treadmill because Microsoft handles servicing. They also change your cost model, backup approach and some feature availability, so they suit organizations already planning a cloud move.

For the full list of paths, Microsoft’s SQL Server end of support options page explains each one in detail.

Who Is Affected by SQL Server 2016 End of Support?

SQL Server 2016 end of support affects every edition, but the impact differs by reader.

Home users and students usually meet SQL Server 2016 as Express or Developer edition on a laptop. If it only holds practice databases, the risk is low, but installing SQL Server 2022 Express or Developer is the easy fix.

Freelancers and small businesses often run SQL Server 2016 Standard behind an accounting, ERP or line-of-business application. Here the application vendor decides a lot: ask which SQL Server versions their current release supports before buying anything.

IT admins may have SQL Server 2016 hidden inside reporting servers, SharePoint farms, monitoring tools or old backup appliances. For SQL Server 2016 end of support, an inventory comes first, because the instance nobody remembers is usually the one nobody patched.

How to Check Your SQL Server Version

Before you plan anything for SQL Server 2016 end of support, confirm exactly what you have. Use these steps on each server:

1. Open SQL Server Management Studio (SSMS) and connect to the instance.
2. Select New Query.
3. Run the command below.
4. Read the version number: 13.0.x is SQL Server 2016, 16.0.x is SQL Server 2022 and 17.0.x is SQL Server 2025.
5. Note the edition (Express, Standard, Enterprise, Web or Developer) and the build.

SELECT @@VERSION;
SELECT SERVERPROPERTY('ProductVersion')  AS Build,
       SERVERPROPERTY('ProductLevel')    AS ServicePack,
       SERVERPROPERTY('Edition')         AS Edition;

If ProductLevel shows anything other than SP3, you are below the minimum level for an in-place upgrade to SQL Server 2022 or 2025. Apply SP3 and the latest GDR first.

Also record the Windows Server version, CPU core count, memory, database sizes and each database’s compatibility level. Those details decide which upgrade path is open to you.

Can You Upgrade SQL Server 2016 In Place?

Yes, if the instance is on SP3 or later. Even after SQL Server 2016 end of support, Microsoft lists SQL Server 2016 SP3 as a supported in-place upgrade source for SQL Server 2019, 2022 and 2025.

Two blockers are worth checking first. Setup refuses to run when a restart is pending, and it is also blocked if the Windows Installer service is not running.

An in-place upgrade is convenient, but it has no easy undo. Many administrators prefer a side-by-side migration: build a new server, restore the databases, test, then switch connection strings. It costs a second machine for a while and buys you a clean rollback.

SQL Server 2022 vs SQL Server 2025: Which Should Replace 2016?

Newer is not automatically better when you plan for SQL Server 2016 end of support. The right target depends mostly on your Windows Server version and your application vendor.

These are minimum specifications, not a promise of ideal performance. A production SQL Server instance benefits from far more memory than the minimum, fast SSD storage and separate drives or volumes for data, logs and backups.

Choose SQL Server 2022 when you need a supported version that still runs on Windows Server 2016, or when your application vendor has certified 2022 but not 2025. Choose SQL Server 2025 when you are building a new server on Windows Server 2022 or 2025 and want the longest runway.

Microsoft’s supported upgrades for SQL Server 2025 page lists every source version and edition path.

How to Upgrade Safely After SQL Server 2016 End of Support

A database upgrade rewards preparation more than speed. Follow this sequence:

1. Inventory every SQL Server 2016 instance, including Express installs bundled with applications.
2. Ask each application vendor which SQL Server version their software supports.
3. Patch SQL Server 2016 to SP3 with the latest GDR.
4. Take full backups of every user and system database, and test a restore.
5. Script logins, SQL Agent jobs, linked servers and credentials.
6. Run Microsoft’s migration assessment tooling against your databases to spot deprecated features.
7. Build a test copy on the target version and run the application against it.
8. Upgrade or migrate production during a planned maintenance window.
9. Keep database compatibility level at 130 at first, then raise it after testing.
10. Monitor performance for a week before decommissioning the old server.

Test these components first, because they break most often:

• Reporting Services and Integration Services packages
• Linked servers and old OLE DB or ODBC drivers
• Applications that connect with outdated TLS settings
• SQL Agent jobs that call scripts or file paths
• Third-party backup and monitoring agents

For more than a handful of servers, use a pilot group: move one low-risk database first, learn from it, then schedule the rest. Ten minutes spent on a pilot can save a long evening explaining why the payroll report no longer runs.

IMPORTANT: For business-critical databases, involve an experienced database administrator. A failed upgrade without a tested backup can mean lost data, not just downtime.

Do You Need a New Windows Server Too?

Often, yes. SQL Server 2016 end of support is a good moment to review the operating system as well. If your SQL Server 2016 runs on Windows Server 2016 and you want SQL Server 2025, you need Windows Server 2019 or later underneath it.

For most rebuilds, a fresh Windows Server 2025 Standard license is the cleaner choice. It covers one physical server and up to two virtual machines when licensed for all cores, which suits a small database host. You do not need Datacenter edition simply because the server runs SQL Server; Datacenter makes sense when you plan many virtual machines on one host.

If your applications or hardware are certified only for an earlier release, Windows Server 2022 Standard remains supported until October 14, 2031. Bcdkey’s Windows Server 2022 End of Support guide explains its lifecycle, and our Windows Server 2022 Standard installation and activation guide walks through setup.

Never install SQL Server on a domain controller. Microsoft advises against it for security reasons, and a domain controller is already wearing enough hats.

Which SQL Server License Do You Need?

Version and edition are separate decisions. The version (2016, 2022, 2025) sets the lifecycle and features; the edition (Express, Standard, Enterprise) sets the scale limits and advanced capabilities.

For most small and midsize workloads being replaced after SQL Server 2016 end of support, Standard edition is enough. Enterprise edition matters when you need more than the Standard compute or memory caps, or advanced high-availability and performance features.

Bcdkey’s Microsoft SQL Server 2022 Standard key covers one server installation and is a one-time purchase, which suits replacing a SQL Server 2016 Standard instance on Windows Server 2016 or later. It does not include Software Assurance, so it would not qualify you for ESUs on older versions.

If an application vendor certifies only SQL Server 2019, Microsoft SQL Server 2019 Standard is supported until January 8, 2030, although it is already in extended support and receives security fixes only. You can browse every version in the SQL Server category.

Licensing SQL Server for many cores, many users or virtualized hosts can get complicated. Business buyers with several servers can contact the Bcdkey B2B wholesale program, and anyone unsure about a key can open a support ticket before installing.

Should You Stay on SQL Server 2016 or Upgrade?

Not every server needs to move the day after SQL Server 2016 end of support.

Stay with SQL Server 2016 for now when:

• You already pay for ESUs through Software Assurance or Azure Arc
• The server is isolated from the internet and untrusted networks
• An application vendor has not yet certified a newer version
• The system is scheduled for retirement within months

Consider SQL Server 2022 or 2025 when:

• The database holds customer, financial or personal data
• You face audits, cyber insurance or compliance reviews
• The server also runs on out-of-support Windows Server 2016
• You need more memory or cores than the old limits allow
• You do not have Software Assurance, so ESUs are not an option

A legacy Microsoft SQL Server 2016 Standard license still has a narrow use: activating a test or archive system for an application that refuses to run on anything newer. It is not a good choice for new production work after SQL Server 2016 end of support.

Recommended Action by Installed Version

Use this table to match your SQL Server 2016 end of support response to what is installed on each server:

Common Mistakes After SQL Server 2016 End of Support

1. Assuming the Database Will Shut Down

It will not shut down at SQL Server 2016 end of support, which is exactly why unsupported instances linger for years without anyone noticing.

2. Upgrading SQL Server but Not Windows Server

A current SQL Server on an unsupported operating system still leaves an unpatched layer, so check both lifecycles together.

3. Skipping the Restore Test

A backup you have never restored is a theory, so test it before the upgrade window starts.

4. Raising Compatibility Level Too Early

Keep the old compatibility level on day one, then raise it once query performance is confirmed.

5. Forgetting Bundled Express Instances

Many applications quietly install SQL Server 2016 Express, so include them in your inventory and in your SQL Server 2016 end of support plan.

Final Thoughts

SQL Server 2016 end of support is not really about a database that stops working. It is about a database that stopped receiving security fixes on July 14, 2026, while it still holds data your business depends on.

The simplest path for most small businesses is a move to SQL Server 2022, which still runs on Windows Server 2016 and is supported until January 2033. If you are building a new server anyway, SQL Server 2025 on Windows Server 2022 or 2025 gives you the longest runway, through January 2036.

Organizations with Software Assurance can use ESUs to stretch SQL Server 2016 end of support by up to three years, but treat them as a bridge rather than a destination.

Start this week with one concrete step: run SELECT @@VERSION on every server you manage and list which ones still report 13.0.

When you are ready to choose a version, compare the SQL Server licenses on Bcdkey.

FAQ About SQL Server 2016 End of Support: What Happens After July 14, 2026

When did SQL Server 2016 end of support happen?

July 14, 2026. That is when SQL Server 2016 extended support ended; mainstream support had already ended on July 13, 2021.

Will SQL Server 2016 stop working after end of support?

No. After SQL Server 2016 end of support, the software keeps running and serving databases, but it no longer receives security updates unless you subscribe to Extended Security Updates.

Can I get Extended Security Updates for SQL Server 2016?

Yes, if you have Software Assurance or subscription licensing. After SQL Server 2016 end of support, ESUs are available for up to three years, through July 2029, via Azure Arc or volume licensing.

Are SQL Server 2016 ESUs free on Azure virtual machines?

No. Microsoft states that moving SQL Server 2016 to an Azure VM no longer provides free ESUs, unlike some earlier versions.

Can I upgrade SQL Server 2016 directly to SQL Server 2025?

Yes, if the instance runs SQL Server 2016 SP3 or later and the server runs Windows Server 2019 or later. SQL Server 2025 does not support Windows Server 2016.

Does my SQL Server 2016 product key work for SQL Server 2022?

No. SQL Server 2016 end of support does not change licensing: each SQL Server version needs its own license, so upgrading to SQL Server 2022 or 2025 requires a new key for that version.

What was the last update for SQL Server 2016?

The July 2026 GDR for SP3, build 13.0.6500.1, was among the final public updates. Service Pack 3 (13.0.6300.2) was the last service pack.

Is SQL Server 2019 also out of support?

No. SQL Server 2019 left mainstream support on February 28, 2025, but extended support with security fixes continues until January 8, 2030.

Does SQL Server 2016 end of support affect Windows Server 2016?

No, they have separate lifecycles. Windows Server 2016 extended support ends on January 12, 2027, so servers running both need a plan for each.

Should I choose SQL Server 2022 or SQL Server 2025 to replace 2016?

It depends on your operating system and application vendor. SQL Server 2022 suits servers that stay on Windows Server 2016, while SQL Server 2025 suits new builds on Windows Server 2019 or later.