SQL Server 2017 end of life: October 12, 2027 — your options

SQL Server 2017 end of life is October 12, 2027 — that's the date Microsoft's Lifecycle page lists as the end of extended support, and it's the closest thing to a hard deadline this product has. A year out is early enough to plan this properly and late enough that it's worth starting: long enough for an inventory, a decision, and a real migration or upgrade; short enough that "later" quietly becomes "next quarter" if nobody owns it. This post works from Microsoft's own Lifecycle and end-of-support pages, as read on September 27, 2026, to lay out what's actually documented and what isn't.

SQL Server 2017 end of life: what Microsoft's Lifecycle page says

SQL Server 2017 follows Microsoft's Fixed Lifecycle Policy. Per Microsoft's Lifecycle page, it started servicing September 29, 2017; mainstream support ended with a listed Mainstream End Date of 10/12/2022 6:59:59 AM Pacific Time, which is October 11, 2022 by the calendar-day convention Microsoft's own prose uses; and extended support ends with a listed Extended End Date of 10/13/2027 6:59:59 AM Pacific Time — October 12, 2027. The Lifecycle page states this single set of dates covers on Linux (all editions), on Windows (all editions), so if you were searching for a separate date for Enterprise, Standard, or Express, there isn't one — all editions, on both operating systems, share this timeline.

Microsoft's own Ending Support in 2027 list independently confirms the date in plain prose, outside the Lifecycle table: it names SQL Server 2017 with an End of Support date of October 12, 2027. The same list shows SQL Server 2014, Extended Security Updates Year 3 ending July 12, 2027 — a reminder, covered more below, that even ESU coverage on other versions runs out on its own schedule rather than lasting indefinitely.

"End of life" and "end of support" mean the same thing here

Microsoft's own SQL Server documentation mostly avoids the phrase "end of life" and uses "end of support" instead — but its end-of-support overview page states directly that the two describe the same event: End of support (also sometimes known as end of life) means that a product reached the end of its support lifecycle. Microsoft no longer provides servicing and support for the product. So when this post, or a search you ran, uses "SQL Server 2017 end of life," it points at the same October 12, 2027 date that Microsoft's own pages call "end of support." There's no separate, later "true" end-of-life date hiding behind different terminology.

Mainstream support already ended — extended support is what expires in 2027

Microsoft's model gives every SQL Server version a minimum of 10 years of support: five years of mainstream support, then five years of extended support. Per Microsoft, Mainstream support includes functional, performance, scalability, and security updates, while Extended support includes only security updates. SQL Server 2017's mainstream support ended October 11, 2022 — already about four years ago as of this post — so any instance still in production has been on security-only updates for a while. October 12, 2027 is the date that ends even that.

Extended Security Updates: not listed for SQL Server 2017

Microsoft offers Extended Security Updates (ESUs) — security-only patches beyond a product's normal support window — for some older SQL Server versions, and they're often the first thing people look for when a deadline like this shows up. They're not free by default: Microsoft's SQL Server end-of-support page prices the option at roughly 75% of the on-premises license cost annually. There's a notable exception, though it doesn't reach SQL Server 2017: Microsoft's ESU page states SQL Server 2014 customers receive free ESUs when they migrate their workloads to SQL Server on Azure VMs. None of that applies here either way, because Microsoft's ESU page for SQL Server states plainly: ESUs are available for SQL Server 2014 (12.x), and SQL Server 2016 (13.x). SQL Server 2017 isn't on that list. As of September 27, 2026, Microsoft's ESU documentation doesn't name an ESU offer, a price, or an availability window for SQL Server 2017 at all — we're not going to guess whether Microsoft adds one before October 2027 or what it would cost if they do, because the source material doesn't say either way.

If you're used to ESUs as the default "buy more time" lever from other Microsoft end-of-support cycles — including SQL Server 2016, covered in our post on SQL Server 2016's end of support — don't assume the same option exists here until Microsoft actually publishes it. And even where ESUs are available, they're not a permanent reprieve: Microsoft's own 2027 list shows SQL Server 2014's third and final year of ESU coverage ending July 12, 2027, three months before SQL Server 2017's own end-of-support date.

Your options, as Microsoft frames them

Microsoft publishes a SQL Server end-of-support options page, but its own "Applies to" line scopes it to SQL Server 2014 (12.x) and SQL Server 2016 (13.x) specifically — it doesn't list SQL Server 2017 at all. Microsoft hasn't published an options page scoped to SQL Server 2017, so what follows is that 2014/2016 page's options, used here as the closest thing Microsoft has published on this question — not as a claim that Microsoft wrote them with SQL Server 2017 in mind: Upgrade to a current version of SQL Server, Migrate your SQL Server workload to Azure SQL Managed Instance, Azure SQL Database, or Azure Virtual Machine, or Subscribe to Extended Security Updates (ESUs) and stay on your current environment until you're able to upgrade or migrate to a supported version or platform. That third option, per the ESU page itself, isn't currently open to SQL Server 2017 anyway, so the paths that are actually available today are the first two:

• Upgrade on-premises to a current, supported version of SQL Server. Microsoft describes the control benefit exactly: You have the most control over features and scalability, because you manage both hardware and software. It also notes the tradeoff plainly: it requires up-front investment and involves higher ongoing management cost compared to other options.
• Migrate to Azure SQL Managed Instance, which Microsoft describes as lift-and-shift ready for most migrations, closely resembling an on-premises instance without needing to manage the underlying hardware or patching yourself.
• Migrate to SQL Server on an Azure VM, either as-is or upgrading during the move — Microsoft's overview says you can lift and shift your SQL Server and application infrastructure into the cloud with minimal or no changes, while keeping OS-level control.

What to inventory now, a year out

October 12, 2027 is a little over a year from this post — close enough that a decision needs to start now, far enough that you can do it properly instead of scrambling. Before deciding which path fits, a few things are worth inventorying:

• Every instance actually running SQL Server 2017. Microsoft's Lifecycle page covers on Linux (all editions), on Windows (all editions), so don't assume this only touches Windows hosts.
• Which edition each instance runs — Enterprise, Standard, or Express — since applications built against Enterprise-only capabilities may need different handling on an upgrade or migration than a plain Express footprint does.
• The applications and services that depend on each instance, and who actually owns them. The database is rarely the whole story.
• Compatibility level testing before any upgrade. Microsoft's own guidance on upgrading notes that an application only needs full recertification when it requires features available under a newer database compatibility setting — in other words, an application can often keep its existing compatibility level after an upgrade and be tested against that, rather than assuming every upgrade forces a full recertification.

SQL Server also rarely runs alone. If the Windows Server host underneath it is approaching its own end-of-support date on a different schedule, that clock can force the SQL Server decision earlier than October 2027 does — see our posts on Windows Server 2016 end of support and Windows Server 2019 end of support if either applies to your environment.

Where we fit

We don't resell SQL Server licenses, Azure subscriptions, or ESUs — we're not a reseller. What we help with is the inventory, the compatibility-level testing, and the upgrade or migration itself, on whichever path you choose: staying on-premises on a supported version, moving to Azure SQL, or running both in parallel during a transition. If you're weighing this against a broader hardware or server refresh, see our post on what a 2026 infrastructure refresh actually costs. Our server end-of-support service covers this kind of planning end to end.

Sources

• Microsoft Learn — SQL Server 2017 Lifecycle (retrieved September 27, 2026)
• Microsoft Learn — Ending Support in 2027 (retrieved September 27, 2026)
• Microsoft Learn — SQL Server end of support options (retrieved September 27, 2026)
• Microsoft Learn — What are Extended Security Updates for SQL Server? (retrieved September 27, 2026)

The 30-second version

SQL Server 2017 end of life is October 12, 2027, per Microsoft's Lifecycle page — the end of extended support, after mainstream support already ended October 11, 2022. Microsoft's own documentation treats "end of life" and "end of support" as the same event, and the date applies to every edition on both Windows and Linux. Unlike SQL Server 2014 and SQL Server 2016, Microsoft's Extended Security Updates page doesn't currently list an ESU offer for SQL Server 2017, so the realistic options today are upgrading to a current version or migrating to Azure SQL Managed Instance, Azure SQL Database, or an Azure VM. A year out is the right time to inventory every instance, edition, and dependent application, and to start compatibility-level testing before you commit to a path.

If you want a senior engineer to help inventory what's still running on SQL Server 2017 and scope the upgrade or migration path, the project intake form takes about three minutes. We'll come back with scope and a fixed-fee range.

Pro IT NW helps regulated mid-market organizations plan and execute Microsoft server and database upgrades and migrations. Vendor-neutral, labor-only — we don't resell SQL Server licenses or Azure subscriptions. This post reflects Microsoft's Lifecycle and SQL Server end-of-support pages as read on September 27, 2026.