SQL Server 2017 End of Support: 12 October 2027 and What to Do Before Then

The short answer

SQL Server 2017 reaches end of extended support on 12 October 2027. 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.

That leaves about twelve months to upgrade, move to Azure SQL or move to another database. For a large estate, that is not much time.

SQL Server 2017 lifecycle dates

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.

Where SQL Server 2017 sits among other versions

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.

Your 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 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 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.

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.