Skip to main content
Guide, 6 minute read

SQL Server 2017 End of Support: Plan Before October 12, 2027

Extended support for SQL Server 2017 ends October 12, 2027. What changes, which versions to move to, why Windows Server 2016 complicates the move, and how to plan it.

Planning guidesIT managers, database owners, and finance leads at organizations running SQL Server 2017, including those on Windows Server 2016By , Founder and CEO, Days Dynamics. Published November 10, 2026.

SQL Server 2017 extended support ends October 12, 2027

Microsoft ends extended support for SQL Server 2017 on October 12, 2027. Mainstream support already ended on October 11, 2022. After extended support ends, Microsoft provides no patches or security updates for the product. As of November 2026, Microsoft's Extended Security Updates documentation covers SQL Server 2014 and SQL Server 2016 only, so plan to move SQL Server 2017 rather than count on paid extensions.

SQL Server lifecycle dates

The last day of each support phase as Microsoft lists it on its lifecycle pages, checked November 2026. Every version here follows Microsoft's Fixed Lifecycle Policy.

VersionReleasedMainstream support endsExtended support ends
SQL Server 2017September 29, 2017October 11, 2022October 12, 2027
SQL Server 2019November 4, 2019February 28, 2025January 8, 2030
SQL Server 2022November 16, 2022January 11, 2028January 11, 2033
SQL Server 2025November 18, 2025January 6, 2031January 6, 2036

The Windows Server 2016 catch

If a SQL Server 2017 instance runs on Windows Server 2016, that operating system's extended support ends January 12, 2027, nine months before the database deadline. The operating system decides which SQL Server version you can move to on the same machine.

  • SQL Server 2022 lists Windows Server 2016 or greater as a supported operating system, so it can be installed on the existing operating system, but that operating system's support ends January 12, 2027.
  • SQL Server 2025 lists Windows Server 2019 or greater. Windows Server 2016 is not on its supported list, so moving to 2025 means a new or upgraded server first.
  • Planning the database and the operating system together avoids migrating the same workload twice in one year.

See the Windows Server 2016 end of support guide and the Windows Server 2016 Decision Snapshot.

Your options for SQL Server 2017

OptionWhat it involvesUsually fits when
Upgrade in place to SQL Server 2022Microsoft lists SQL Server 2017 as a supported source for upgrading an existing instance to SQL Server 2022The server and its operating system are being kept and the application vendor supports 2022
Move to a new server on SQL Server 2022 or 2025Build a supported operating system and SQL Server version, then migrate the databases and cut overThe hardware or Windows Server 2016 is also due for replacement
Move the databases to AzureRun SQL Server on an Azure virtual machine or move to a managed Azure SQL serviceYou are already reducing on-premises hardware and the application supports it
Retire or consolidateArchive the data and shut the instance down, or merge small databases onto a supported instanceThe application is no longer used or the databases are small

See the Replace the server or move to Azure and the Enterprise infrastructure modernization.

How to plan the move

  • Inventory every SQL Server 2017 instance: edition, operating system, the databases on it, and the applications that use them.
  • Ask each application vendor which SQL Server versions they support. Their answer often decides between 2019, 2022, and 2025. Mainstream support for 2019 already ended February 28, 2025.
  • Check the operating system under each instance. If it is Windows Server 2016, plan both changes in one project.
  • Confirm how the instance is licensed today, because the licensing route shapes whether you upgrade in place, move servers, or move to Azure.
  • Test the upgrade or migration on a copy of the databases, including backups, jobs, linked servers, and reports.
  • Schedule the cutover with a rollback plan, then run a test restore on the new version.

See the Infrastructure End-of-Support Assessment.

Frequently asked questions

When does SQL Server 2017 support end?

Extended support for SQL Server 2017 ends October 12, 2027. Mainstream support ended October 11, 2022. The dates apply to SQL Server 2017 on Windows and on Linux, all editions.

Will Microsoft offer Extended Security Updates for SQL Server 2017?

As of November 2026, Microsoft's Extended Security Updates documentation lists SQL Server 2014 and SQL Server 2016 only. It does not announce ESUs for SQL Server 2017, so do not build a plan that depends on them.

Can SQL Server 2017 be upgraded directly to SQL Server 2022?

Yes. Microsoft lists SQL Server 2017 as a supported source for an in-place upgrade to SQL Server 2022. Check the operating system and the application vendor's support before you do.

Can SQL Server 2025 run on Windows Server 2016?

No. Microsoft lists Windows Server 2019 or greater for SQL Server 2025. To move a SQL Server 2017 instance on Windows Server 2016 to 2025, the server has to move to a supported operating system first.

What happens if we keep running SQL Server 2017 after October 2027?

Microsoft provides no further patches or security updates for it. Microsoft also states that third-party application control tools are not a replacement for product security fixes.

Plan SQL Server 2017 and Windows Server 2016 as one project

Send us the SQL Server instances you run, the operating systems under them, and the applications that depend on them. We will map each one to a supported path and a sequence that avoids moving the same workload twice. A planning call is planning support, not a quote, an audit, or a commitment on licensing, availability, or delivery dates.

Sources

Primary sources checked when this guide was written. Dates and product status can change, so confirm on the source before you rely on them.

Planning this project now?

Turn the checklist into a plan

The 2-minute IT quiz turns this checklist into ranked priorities for your situation, before any contact details.