Logo-Icon
HOMEABOUTSERVICESHOW WE WORKBLOGInstagram-Icon Talk To an Expert
RadixTrie-image
SQL Server 2017 end of life: 12 October 2027
Architecture

SQL Server 2017 End of Life: 12 October 2027 and What to Do First

SQL Server 2017 reaches end of life on 12 October 2027, when Microsoft's extended support ends; mainstream support ended on 11 October 2022. No Extended Security Updates have been announced for it. The dates, what stops, the upgrade paths to SQL Server 2022 and 2025, a twelve-month plan and the questions people ask.
By RadixTrie16 October 20267 min read
SQL Server 2017 reaches end of life on 12 October 2027, when Microsoft's extended support ends. Mainstream support ended on 11 October 2022, so for four years the version has received security fixes only: no cumulative updates and no fixes for non-security bugs.
No Extended Security Updates programme has been announced for SQL Server 2017. Microsoft's ESU page lists SQL Server 2014 and SQL Server 2016 only, so treat 12 October 2027 as the last day of security fixes. Both SQL Server 2022 and SQL Server 2025 accept a direct in-place upgrade from 2017, which makes the move a project of months rather than a redesign.
Checked against Microsoft's SQL Server 2017 lifecycle page and Microsoft's Extended Security Updates page on 16 October 2026. Running SQL Server 2019 as well? Its date is 8 January 2030: see SQL Server 2019 end of life (8 January 2030).

SQL Server 2017 dates

Released: 29 September 2017
Mainstream support ended: 11 October 2022
Extended support ends (end of life): 12 October 2027
Service packs: none; from SQL Server 2017 onwards Microsoft ships cumulative updates only
Extended Security Updates: none announced; Microsoft offers ESUs for SQL Server 2014 and 2016 only, as at 16 October 2026
Platforms covered: the same dates apply on Windows and on Linux, all editions
Time left on 16 October 2026: 361 days
Microsoft's lifecycle page shows the cut-offs as timestamps in Pacific time (10/12/2022 6:59:59 AM and 10/13/2027 6:59:59 AM), which is why some pages quote the day after. Microsoft's own documents quote the day before the timestamp (its ESU FAQ gives 14 July 2026 for SQL Server 2016, whose lifecycle page shows 7/15/2026 6:59:59 AM), and this article follows Microsoft.

Where to move

SQL Server 2025: released 18 November 2025; mainstream support ends 6 January 2031; extended support ends 6 January 2036; direct in-place upgrade from 2017: yes
SQL Server 2022: released 16 November 2022; mainstream support ends 11 January 2028; extended support ends 11 January 2033; direct in-place upgrade from 2017: yes
Azure SQL Managed Instance: no version and no end-of-support date (Microsoft describes it as a fully managed service that never reaches end of support); a migration rather than an upgrade
Dates from Microsoft's lifecycle pages for SQL Server 2022 and SQL Server 2025. Upgrade paths from Microsoft's supported version and edition upgrades for SQL Server 2025, which lists SQL Server 2017 (14.x) as a supported source. One edition detail: Web edition does not exist in SQL Server 2025, so a 2017 Web edition instance upgrades to Standard or Enterprise.

What changed in October 2022, and what changes on 12 October 2027

Microsoft's lifecycle has two stages. In Microsoft's words, mainstream support 'includes functional, performance, scalability, and security updates' and extended support 'includes only security updates'. SQL Server 2017 left mainstream support on 11 October 2022. Since then there have been no new cumulative updates: a bug you hit in 2017 today will not be fixed in 2017, and a support case for a non-security problem ends with advice to upgrade. Security fixes continue until 12 October 2027. After that date nothing ships, and because no ESU programme exists for this version there is no paid way to extend it. Microsoft's end of support options page describes the stages and the routes out.

The risks of running past the date

  • A twelve-month horizon, not a three-year one. For SQL Server 2016 Microsoft sells paid security updates for up to three years after the date. Nothing of the kind has been announced for 2017, so the date on the lifecycle page is the real deadline.
  • Unpatched vulnerabilities. A database engine holding personal and financial data with no security updates is exactly the exposure that cyber-insurance questionnaires, auditors and privacy laws such as POPIA ask about.
  • Application vendor certification. Vendors drop old database versions from their support matrices ahead of Microsoft's date. Ask each vendor for its certified SQL Server versions now; that answer often sets your deadline, not Microsoft's.
  • The Windows Server underneath. Windows Server 2016 reaches end of support on 12 January 2027, nine months before SQL Server 2017 does, and Microsoft does not list SQL Server 2017 for Windows Server 2025. Plan the two together.
  • Compatibility drift. Newer drivers, backup tools, monitoring agents and cloud services stop testing against old versions quietly.
  • Compressed timelines. A version upgrade across a production estate is a project measured in months. The estates that end up in trouble are the ones that start in the last quarter before the date.
A useful test: for each instance, write down the SQL Server version, the Windows Server version, the application that depends on it and the versions its vendor certifies. Any row with two dates inside the next eighteen months is your priority list.

Your options, ranked

  1. Upgrade in place to SQL Server 2025 or 2022. Same hosting, same licence model, and the longest runway on 2025 (extended support to 6 January 2036). Microsoft supports the in-place upgrade from SQL Server 2017 to both. The work is a compatibility assessment and a rehearsed upgrade, not a redesign.
  2. Upgrade and consolidate. If several 2017 instances are underused, use the upgrade to consolidate onto fewer, better-specified servers or one newer instance. Fewer things to patch, back up and license.
  3. Move to Azure and upgrade at the same time. Azure SQL Managed Instance takes the version question away permanently; SQL Server on an Azure virtual machine keeps full control on a current version. Only merge the two decisions if the cloud move already has its own business case. Our guide to migrating SQL Server to Azure sets out the steps.
  4. Do nothing, written down. Legitimate only for an isolated, non-production or soon-to-be-retired instance, with the retirement date real and the risk acceptance signed.
  5. Not an option: an ESU bridge. Microsoft has announced no Extended Security Updates for SQL Server 2017. Plan without one, and treat any later announcement as a bonus rather than a plan.

How an upgrade actually goes

Inventory every instance and database with version, edition, compatibility level and dependent applications. Run the compatibility assessment against the target version and fix what it finds on the current platform. Build the target, restore a copy of production, run the real application and compare query performance against a baseline, because plans change between versions and a handful of queries always need attention. Databases keep their compatibility level through the upgrade (Microsoft's upgrade page confirms a level of 100 or higher is unchanged), so an application only needs full recertification when you raise the level to use newer engine behaviour. Restore-test the new environment before cutover, not after. Then a rehearsed cutover with a rollback path, keeping the old instance intact until the new one has been through a month-end.

A twelve-month plan

  1. This quarter: inventory and vendor matrix. Every 2017 instance, its Windows version, its applications and each vendor's certified SQL Server versions. Decide the target per instance: 2025 by default, 2022 where a vendor certifies only 2022.
  2. Next quarter: compatibility assessment and target build. Run the assessment, fix the findings on the current platform, build the target environment and restore production copies onto it.
  3. The quarter after: rehearsal. Run the applications and the heaviest reports on the target, compare performance against the baseline, time the cutover and practise the rollback.
  4. Cutover with a month-end behind it before 12 October 2027. Keep the old instance intact but offline for a full business cycle, then decommission it.

SQL Server 2017 end of life: common questions

When is SQL Server 2017 end of life?

12 October 2027, the day extended support ends. Microsoft's lifecycle page for SQL Server 2017 shows the cut-off as 10/13/2027 6:59:59 AM Pacific time; Microsoft's own documents quote the day before such timestamps, so the date is 12 October 2027. Mainstream support ended on 11 October 2022.

Is SQL Server 2017 still supported in 2026?

Yes, for security updates only. SQL Server 2017 has been in extended support since 11 October 2022, which Microsoft defines as security updates only: no cumulative updates and no fixes for non-security bugs. Security fixes continue until 12 October 2027. Microsoft's end of support options page describes both stages.

Will Microsoft offer Extended Security Updates for SQL Server 2017?

Nothing has been announced. Microsoft's ESU page (updated 22 June 2026) says ESUs 'are available for SQL Server 2014 (12.x), and SQL Server 2016 (13.x)'. For those versions, ESUs cover security updates rated Critical, for a maximum of three years after extended support ends, at 'approximately 75% of the on-premises license cost annually' in Microsoft's words, through Software Assurance or Azure Arc pay-as-you-go billing. Since SQL Server 2016, moving an instance to an Azure virtual machine no longer brings ESUs at no charge. Plan SQL Server 2017 without an ESU bridge.

Can we upgrade SQL Server 2017 directly to SQL Server 2025?

Yes. Microsoft's supported version and edition upgrades page for SQL Server 2025 lists SQL Server 2017 (14.x) as a supported source for an in-place upgrade, alongside 2014 SP3, 2016 SP3, 2019 and 2022. Databases at compatibility level 100 or higher keep their level, so the application sees no change in engine behaviour until you choose to raise it. Web edition does not exist in 2025 and maps to Standard or Enterprise.

Does SQL Server 2017 run on Windows Server 2022 or 2025?

Windows Server 2022: yes. Microsoft's requirements page for SQL Server 2017 (updated 20 July 2026) lists Windows Server 2022 Datacenter, Datacenter: Azure Edition and Standard for every edition, including Server Core. Windows Server 2025 does not appear in that table, so treat SQL Server 2017 on Windows Server 2025 as unsupported unless Microsoft adds it. If the operating system needs replacing anyway, that is one more reason to upgrade SQL Server rather than move 2017 onto a new server.

Is SQL Server 2017 on Linux on the same dates?

Yes. Microsoft's lifecycle page states that the dates apply to SQL Server 2017 'on Linux (all editions), on Windows (all editions)'. The 12 October 2027 date is the same whichever Linux distribution or container platform the instance runs on, and the upgrade targets are the same: Microsoft's lifecycle pages list SQL Server 2022 and 2025 on Linux and on Windows alike.

Should we move to SQL Server 2022 or 2025?

SQL Server 2025 for the longest runway: mainstream support to 6 January 2031 and extended support to 6 January 2036, against 11 January 2028 and 11 January 2033 for 2022. Choose 2022 only when an application vendor certifies 2022 and not yet 2025, and record when you expect that to change. Both accept the direct upgrade from 2017, so the engineering effort is similar either way.

How RadixTrie helps

RadixTrie is a database specialist with senior engineers across Microsoft SQL Server, Oracle and PostgreSQL, based in South Africa and working with organisations in the US, UK, Europe and beyond through our remote DBA services. We assess estates against these dates, rank the options for each instance, run the upgrades and migrations, and then keep the estate patched and supported afterwards. The model is direct access to senior database experts, with no service desk and no escalation loops. Our SQL Server DBA services page describes the cover; for estates in South Africa, see SQL Server support in South Africa. A database health check is the usual first step, and every one of our database services is delivered by the engineer who does the work.
Still on SQL Server 2017? Let's build the list of instances and dates together.
TAGSSQL ServerSQL Server 2017End of SupportUpgradeMigrationEnd of Life