OSSeva Blog
OperationsSQL Server 2017 End of Life: 12 October 2027 and What to Do Before Then
Dates checked on 20 October 2026 against endoflife.date and Microsoft's lifecycle pages.
Leaving SQL Server?
Migration to PostgreSQL, with 24/7 support afterwards on infrastructure you control. OSSeva does not support or patch SQL Server itself.
SQL Server to PostgreSQL migration →The short answer
SQL Server 2017 end of life is 12 October 2027, the date extended support ends. Mainstream support ended on 11 October 2022, so since then 2017 has received security updates only. After 12 October 2027, Microsoft ships no further updates for it. As of October 2026, Microsoft's ESU FAQ lists Extended Security Updates for SQL Server 2014 and 2016 only, so there is no published ESU programme for 2017 yet.
Deciding what to do about it? SQL Server end of life sets out each version's dates and ESU terms next to the migration to PostgreSQL option. Is the server under it Windows Server 2016? Windows Server 2016 end of support sets the operating system dates beside the SQL Server ones.
That leaves until then to upgrade, move to Azure SQL or move to another database, and a large estate needs testing time on top of the work itself.
SQL Server 2017 lifecycle dates
| Milestone | Date |
|---|---|
| Release | 29 September 2017 |
| End of mainstream support | 11 October 2022 |
| End of extended support | 12 October 2027 |
| Extended Security Updates | Not published as of October 2026 |
Source: the Microsoft Lifecycle page for SQL Server 2017, which covers all editions on Windows and Linux, and Microsoft's list of products ending support in 2027. SQL Server 2017 was the first version with no service packs; it is serviced through cumulative updates.
ESU prices for 2016 and 2017, checked on 26 October 2026, are in SQL Server ESU cost vs migrating to PostgreSQL.
Where SQL Server 2017 sits among other versions
| Version | Mainstream support ends | Extended support ends |
|---|---|---|
| SQL Server 2016 | 13 July 2021 | 14 July 2026 (ESUs to 17 July 2029) |
| SQL Server 2017 | 11 October 2022 | 12 October 2027 |
| SQL Server 2019 | 28 February 2025 | 8 January 2030 |
| SQL Server 2022 | 11 January 2028 | January 2033 |
| SQL Server 2025 | January 2031 | January 2036 |
Dates checked against endoflife.date and Microsoft's lifecycle pages on 20 October 2026, and re-read on 17 November 2026. The SQL Server versions and end-of-support dates chart lists every version from 2012 to 2025 with mainstream, extended and ESU dates, and the SQL Server 2019 end of support post has the same table with the Extended Security Updates column.
What changes on 12 October 2027
- Security updates stop. Extended support is the security-only stage, and it ends that day.
- No product support from Microsoft for SQL Server 2017.
- Audit and scanner findings for every 2017 instance, on Windows and on Linux.
- The databases keep running. Nothing stops on the day itself.
Will there be ESUs for SQL Server 2017?
Microsoft has run ESU programmes for SQL Server 2014 and 2016, each lasting up to three years and covering Critical security updates only. It has not published one for 2017. If it does, expect it to work like the 2016 programme, delivered through Azure, Azure Arc or volume licensing and described by Microsoft as a temporary bridge. Planning on an announcement that has not been made is a risk; plan the upgrade or migration first. The SQL Server 2016 end of support post explains how the current ESU programme works.
What Extended Security Updates cost, and whether 2017 gets them
There is no price for SQL Server 2017 ESUs, because Microsoft has not published a programme. The only guide to what one would look like is how Microsoft sells ESUs for SQL Server 2014 and 2016, summarised below. Microsoft publishes the per-core rates on its Azure Arc pricing page, and they change, so this post gives the structure and not a number.
| Term | How Microsoft charges for SQL Server 2014 and 2016 ESUs |
|---|---|
| Billing unit | Per core, billed hourly through Azure Arc, with a four-core minimum per machine |
| Editions | Enterprise and Standard. Express, Web and Developer cannot subscribe |
| Core limits | Standard is capped at 24 cores. A physical-core licence with unlimited virtualization has a 16-core minimum |
| Who can subscribe | Software Assurance or a SQL Server subscription, or pay-as-you-go billing through Azure Arc. Server+CAL licences without Software Assurance cannot |
| Length | Up to three years after the extended end date |
| Late start | Billed back to the start of the current ESU year |
| Free ESUs | SQL Server 2014 on Azure VMs and Azure VMware Solution; not offered for SQL Server 2016 |
| Coverage | Critical security updates only. No new features and no general technical support |
Source: Microsoft Learn, "What are Extended Security Updates?", "Extended Security Updates FAQ" and "Extended Security Updates enabled by Azure Arc", read 22 October 2026. Microsoft calls ESUs a temporary bridge, which is why this post treats the upgrade or migration as the plan and ESUs as a fallback that may not exist for 2017.
Your options
| Option | What you get on SQL Server 2017 | What it costs you |
|---|---|---|
| Upgrade to SQL Server 2022 or 2025 | A supported version; 2025 accepts an upgrade straight from 2017 | Licences on Microsoft's terms and application testing |
| Extended Security Updates (ESU) | None published for 2017. For 2016 they are Critical fixes only, for up to three years | Nothing to buy until Microsoft announces a programme |
| Azure SQL Managed Instance or Database | A managed service that Microsoft says never reaches end of support | Your databases move onto Microsoft's cloud service and its terms |
| Move to PostgreSQL | An open source database with no per-core licence, on infrastructure you control | A migration sized to each application, then a PostgreSQL support subscription priced per cluster |
The same four routes for every version are set out on SQL Server end of support options.
1. Upgrade
SQL Server 2025 supports a direct upgrade from SQL Server 2017, and 2025 has mainstream support to January 2031. SQL Server 2022 is the other current choice, with mainstream support to January 2028. Run the SQL Server migration component in SQL Server Management Studio to find compatibility problems before you start.
2. Move to Azure SQL
Azure SQL Managed Instance and Azure SQL Database are managed services that Microsoft says never reach end of support. They remove the version calendar but change who runs the database.
3. Move to PostgreSQL
For applications you control, the 2017 deadline is a reasonable trigger to leave SQL Server. It is a migration with real work in T-SQL, data types and connection paths, so start early; the scope is set by schema size, T-SQL volume, the clients that connect and your downtime window. The SQL Server to PostgreSQL migration guide covers the paths.
Where OSSeva fits
OSSeva does not support or patch SQL Server. If upgrading within SQL Server is the right call, Microsoft and its partners are the people to talk to. If you decide to leave, OSSeva's SQL Server to PostgreSQL offer handles assessment, data movement with tools such as pgloader, a side-by-side run and cutover, then supports PostgreSQL on infrastructure you control, priced per cluster. Book a 15-minute discovery call for a quote.
Frequently asked questions
When is SQL Server 2017 end of support?
12 October 2027, the end of extended support. Mainstream support ended on 11 October 2022.
When is the end of extended support for SQL Server 2017?
12 October 2027. After that date Microsoft ships no security updates for SQL Server 2017.
Will Microsoft offer Extended Security Updates for SQL Server 2017?
As of October 2026, Microsoft has not announced any. Its ESU FAQ lists only SQL Server 2014 and 2016.
How much do SQL Server Extended Security Updates cost?
Microsoft bills ESUs per core, by the hour, through Azure Arc, with a four-core minimum per machine. It has published no ESU programme for SQL Server 2017, so there is no 2017 price. The rates for 2014 and 2016 are on its Azure Arc pricing page.
Does the date apply to SQL Server 2017 on Linux?
Yes. The lifecycle page covers all editions of SQL Server 2017 on Windows and on Linux.
Can SQL Server 2017 upgrade directly to SQL Server 2025?
Yes. SQL Server 2025 lists SQL Server 2017 as a supported upgrade source.
Tags
Related articles
SQL Server 2016 End of Life: ESU Terms, Dates and Your Options
October 7, 2026OperationsWindows Server 2016 end of support: what happens to the apps on it
November 15, 2026OperationsSQL Server 2019 end of support: the dates, and when moving to PostgreSQL pays
October 7, 2026OperationsSQL Server 2016 on Windows Server 2016: Two Deadlines, One Plan
November 17, 2026OperationsWhat SQL Server ESUs Cost and When They Stop Making Sense
November 17, 2026SecurityDoes Microsoft Offer Extended Security Updates (ESU) for .NET?
November 17, 2026Get a quote
Leaving SQL Server? Send your work email.
An OSSeva engineer replies within 1 business day with an assessment plan and a quote, priced per cluster.
Prefer to talk or read more first?