SQL Server End of Life Dates: Every Version from 2012 to 2025

SQL Server 2016 lost extended support on July 14, 2026. SQL Server 2017 follows on October 12, 2027. If either one still runs something that matters, the end-of-support date is now a planning problem, not a footnote.

Below are Microsoft’s official dates for every version from 2012 to 2025, where each one stands as of October 22, 2026, and what we’d do about it. It’s the same advice we give our own clients.

When Is Your SQL Server End of Life?

Here are the key dates, newest release first. The countdowns update on their own:

Active Support is Microsoft’s mainstream support (all fixes); Security Support is extended support (security fixes only). Released shows the start of Microsoft’s lifecycle for each version. Rows show product dates. ESU and in-place upgrades need the final service pack (2016 SP3, 2014 SP3, 2012 SP4); earlier service packs lost support sooner and are listed under View More.

Source: Microsoft Lifecycle (checked October 22, 2026)

How to Check Your SQL Server Version

You can quickly find your current SQL Server version by running this query:

SELECT
    SERVERPROPERTY(N'ProductVersion')         AS ProductVersion,
    SERVERPROPERTY(N'ProductLevel')           AS ProductLevel,          -- RTM / SPn / CTPn
    SERVERPROPERTY(N'Edition')                AS Edition,
    SERVERPROPERTY(N'EngineEdition')          AS EngineEdition,         /* 2 = Standard, 3 = Enterprise or Developer, 4 = Express, 5 = Azure SQL Database, 6 = Azure Synapse, 8 = Azure SQL Managed Instance */
    SERVERPROPERTY(N'ProductUpdateLevel')     AS ProductUpdateLevel,    -- CUn
    SERVERPROPERTY(N'ProductUpdateReference') AS ProductUpdateReference; -- KB#

If you need to reference SQL Server for inventory or compliance, here are the standard product identifiers (CPEs):

1. cpe: cpe:/a:microsoft:sql_server
2. cpe: cpe:2.3:a:microsoft:sql_server

Looking for specific builds? View the comprehensive SQL Server Builds list.

SQL Server 2016 End of Support: July 14, 2026

Status: out of support. Paid ESU available until July 17, 2029. Mainstream support ended July 13, 2021 and extended support ended July 14, 2026. Security patches now come only through Extended Security Updates, and for 2016 those are paid even on Azure VMs.

What to do: upgrade to SQL Server 2022 or 2025 (in place from 2016 SP3, or side by side on a new server) and buy ESU only for the instances that can’t move this year. On 2025, the new OLE DB driver can break linked servers and replication that rely on untrusted certificates, so audit those first. The full walkthrough is in our SQL Server 2016 end of support guide.

SQL Server 2014 End of Life: Out of Support Since July 9, 2024

Status: out of support. ESU Year 3 runs until July 12, 2027. Mainstream support ended July 9, 2019 and extended support ended July 9, 2024. 2014 is the version where Microsoft gives ESUs free when you move the workload to an Azure VM or Azure VMware Solution.

What to do: you have less than nine months of ESU left. 2014 SP3 can upgrade in place to SQL Server 2022 or 2025, but with that little runway, a side-by-side SQL Server migration that keeps the old server available until you sign off on the new one is usually the safer bet.

SQL Server 2012 End of Life: No Patches of Any Kind Since July 2025

Status: fully out of support. No ESU. Mainstream support ended July 11, 2017, extended support ended July 12, 2022, and the last ESU year ended July 8, 2025. Microsoft no longer releases security updates for 2012, at any price.

What to do: move it now. 2012 SP4 can upgrade in place to SQL Server 2022, but not to 2025, which starts from 2014 SP3. To land on 2025, migrate instead: SQL Server 2025 restores backups taken on 2008 and later.

SQL Server 2017 End of Life: October 12, 2027

Status: extended support (security fixes only), ending in under 12 months. Mainstream support ended October 11, 2022. Extended support ends October 12, 2027. Microsoft’s lifecycle page lists no ESU years for 2017 as of October 2026.

What to do: treat it as a 2027 budget line now, not next summer. In-place upgrades from 2017 to 2022 and 2025 are supported. Start with an inventory of what connects to each instance, because that decides the downtime window. Our SQL Server upgrade services cover the inventory, the testing and the cutover.

SQL Server 2019 End of Life: Extended Support Until January 8, 2030

Status: extended support (security fixes only). Mainstream support ended February 28, 2025, so 2019 now gets security fixes but no functional or performance fixes. Extended support ends January 8, 2030.

What to do: no emergency, but don’t start new projects on it. Plan the move to SQL Server 2022 or 2025 for 2028 or 2029, ahead of the last-minute rush. If you’re on 2019 because a vendor certified it, ask that vendor now which newer version they support.

SQL Server 2022 End of Life: January 11, 2033

Status: mainstream support until January 11, 2028, then extended support (security fixes only) until January 11, 2033.

What to do: stay current on cumulative updates. Nothing dramatic needed. 2022 is a sensible landing spot for anything coming off 2016 or 2017.

SQL Server 2025 End of Life: January 6, 2036

Status: mainstream support until January 6, 2031, extended support until January 6, 2036. Released November 18, 2025, it’s the newest version and has the longest runway.

What to do: pick it for new builds if your applications and vendors support it, and test before you move. Its OLE DB driver enforces encrypted connections, which breaks some linked server and replication setups (what breaks and how to fix it).

The Reality of SQL Server Versions in the Wild

You know what’s interesting? A 2024 analysis of over a million SQL Server instances found nearly 20% already running unsupported versions. SQL Server 2014 and 2016 have both dropped out of support since then.

You're definitely not alone if you're running older versions. One IT consultant found a client running 13+ servers on SQL 2008 and over 30 on SQL 2012 even after EOL, creating massive technical debt. Even SQL Server 7.0 (from 1998) instances are still detected in production environments.

As one former Microsoft SQL Server product team member noted: "It was a problem back then, getting people off old versions." The "stickiness" of applications built on aging databases creates significant technical debt that eventually carries a high price in risk and lost agility.

What Happens When Support Ends?

Security becomes your problem (entirely)

• No more security updates means every vulnerability found after the end date stays unpatched.
• Here’s a wild stat: unpatched vulnerabilities cause 60% of cyber compromises. Attackers rarely need something new when a known, fixable bug is still open.
• Hackers actively scan the web for old SQL servers that are unpatched, then use automation to break in.

Compliance Red Flags

• Out-of-support SQL? That’s a big flag for auditors, especially under regulations like PCI-DSS, SOX, HIPAA, and GDPR.
• Even Microsoft’s Extended Security Updates (ESU) are only a stopgap. Auditors want to see an actual plan to get off those versions.

Operational and Performance Risks

• No bug fixes means unresolved issues: potential corruption, random outages, or degraded performance.
• New apps (and even your monitoring tools) are gradually dropping compatibility with old SQL Server editions.
• Talented DBAs won’t stick around if all they do is babysit unsupported legacy systems. They want roles that mix real technical challenge with growth: modern features, automation, and a path forward, not a dead end.

The Real Costs of Running End-of-Life SQL Server

What’s your return on investment on changing the oil in your car? If you don’t, you might destroy the engine.

Same with SQL Server: running an outdated version isn’t just a technical risk. It can become a legal and financial one too.

This risk extends far beyond just security concerns. The price tag of maintaining EOL SQL Server includes both direct and hidden costs.

Direct Costs:

• For 2016, Extended Security Updates cost money for every year you stay, and late sign-ups are back-billed to the start of the ESU year.
• Emergency migrations, often triggered by critical failures, cost far more than planned upgrades: rushed work, overtime, and no time to test.
• Breach recovery, compliance fines, and firefighting efforts can easily blow past the cost of a proactive transition

Indirect Costs (“Technical Debt”):

• Running outdated versions like SQL Server 2012, 2014, or 2016 means more time spent on maintenance and less on innovation.
• Teams lose productivity wrestling with old tech that lacks modern features.
• Cybersecurity insurance coverage may be reduced or denied entirely for unsupported environments. Auditors and business stakeholders apply growing pressure to justify the risk.
• Meanwhile, your competitors are gaining ground by using features you don’t have.

What Works for Smart Companies

The organizations I work with that handle this well are treating SQL Server EOL as a strategic opportunity, not just a maintenance headache:

1. They inventory everything - Smart migration planning starts with a detailed inventory of what's connecting to your SQL Server: reporting services, third-party tools, Excel spreadsheets with hard-coded connections, internal applications, and automated jobs.
2. They determine acceptable downtime - One critical question shapes the entire migration strategy: how much outage can your business tolerate? Seconds? Minutes? Hours? This completely changes the approach and cost. For businesses where even short outages mean massive revenue loss, near-zero downtime migrations are possible but require more preparation.
3. They test thoroughly - The difference between smooth and disastrous migrations comes down to testing. The best migrations include capturing production workloads and replaying them on the new environment to identify issues before the actual cutover.
4. They always have a rollback plan - Even with perfect preparation, things can go wrong. Smart organizations have a tested plan to revert to the original environment if necessary.
5. They check Azure (or AWS) migration incentives. Read the fine print: Microsoft gave free ESUs to SQL Server 2014 workloads moved to Azure VMs, but not to 2016.
   See how Integrated Dermatology saved thousands and improved performance by migrating their SQL Server to Azure with just minutes of downtime.
6. They consolidate while upgrading - Companies should use migration as an opportunity to review their entire SQL Server estate, identify redundancies, and implement better hardware utilization through virtualization and proper sizing.

Taking the Next Steps with Your SQL Server

If you take away just three things from this article:

1. Check your exposure now - Running SQL Server 2016 or earlier? You’re already out of support. On 2017? You have until October 12, 2027.
2. Budget for methodical modernization - It will cost something, but way less than an emergency response. Don't skimp on planning, preparation, and testing.
3. Use EOL dates as leverage to finally secure funding for modernization projects that have been needed for years.

The upgrades that go smoothly start early, test every dependency, and keep a fallback ready.

Let us know what SQL Server versions you’re currently running, and we’d be happy to help think through your upgrade or migration options. We’ve guided dozens of companies through this exact challenge, and we’ve found there’s usually a better path forward than what might initially be apparent.