What ends on 12 October 2027
After 12 October 2027 Microsoft publishes no more security updates for SQL Server 2017 and offers no technical support for it. The last cumulative update, CU31, appeared in 2022; since then only security updates have been released, and those stop too.
In November 2026, Microsoft's Extended Security Updates programme covers SQL Server 2014 and 2016 only. No ESU offer for SQL Server 2017 has been announced, so do not count on one when you plan.
Upgrade paths
- In place: on Windows, SQL Server 2022 and SQL Server 2025 can both upgrade SQL Server 2017 in place. On Linux the operating system usually decides: see below.
- Backup and restore on a new server: a SQL Server 2017 backup can be restored on SQL Server 2022 or 2025. The database keeps compatibility level 140, so most code behaves as before.
- Log shipping or an availability group to a new server: for large databases with little room for downtime; you switch over in minutes.
SQL Server 2019 is not a sensible target any more: its extended support ends on 8 January 2030. SQL Server 2022 is supported until 11 January 2033 and SQL Server 2025 until 6 January 2036.
Points of attention specific to 2017
- Machine Learning Services: SQL Server 2017 installed R and Python with setup. From SQL Server 2022 the runtimes are no longer included and have to be installed and configured separately.
- Linux: SQL Server 2017 runs on RHEL 7 and 8, SLES 12 and Ubuntu 18.04. SQL Server 2022 needs RHEL 8 or 9, SLES 15 or Ubuntu 20.04 or 22.04; SQL Server 2025 needs RHEL 9 or 10 or Ubuntu 22.04 or 24.04 and no longer supports SLES. An in-place package upgrade is therefore only possible to 2022 on RHEL 8; in all other cases you install a new server and restore the databases.
- Client drivers: newer ODBC and OLE DB drivers encrypt connections by default and check the server certificate.
- Query plans: after raising the compatibility level some queries may get a different plan. Turn on Query Store before the change so you can compare.
Cloud options
Azure SQL Managed Instance and Azure SQL Database are versionless, so you will not face this kind of deadline again. Amazon RDS for SQL Server and Google Cloud SQL for SQL Server run SQL Server 2017 now, but follow Microsoft's dates: Cloud SQL ends support for SQL Server 2017 on 13 October 2027, and when SQL Server 2016 reached its end of support, RDS scheduled the remaining instances for an automatic upgrade. Check the RDS deprecation schedule for 2017 and upgrade before RDS does it for you.
A timeline that works
- Now: inventory your SQL Server 2017 instances and ask your application vendors which versions they support.
- First half of 2027: restore recent backups on a test server with the new version, test the applications and fix what breaks.
- Mid-2027: migrate production, one instance at a time, keeping the old server as a fallback.
- Before 12 October 2027: switch off the last SQL Server 2017 instances, or have a documented exception for those that cannot move yet.
How the free scan helps
The MigrateMyDatabase scan runs a read-only script on your SQL Server 2017 database that collects the structure and which features your code uses. Paste the result in the page, choose SQL Server 2022, 2025 or an Azure or AWS target, and see per target which objects need attention. The analysis runs in your browser and nothing is uploaded.
Questions
When does support for SQL Server 2017 end?
Extended support ends on 12 October 2027. Mainstream support already ended in October 2022.
Will there be Extended Security Updates for SQL Server 2017?
In November 2026 Microsoft offers ESUs for SQL Server 2014 and 2016 only, and none have been announced for 2017. Plan as if there will be none.
Should I upgrade to SQL Server 2022 or 2025?
Both are supported for years: 2022 until 11 January 2033, 2025 until 6 January 2036. 2025 gives the longest runway; 2022 has been in use longer. Check what your application vendor supports.
Can I upgrade SQL Server 2017 on Linux in place?
Only where the distribution is supported by both versions, which in practice means SQL Server 2022 on RHEL 8. SQL Server 2025 does not run on any distribution that SQL Server 2017 supports, so for 2025 you set up a new server and restore the databases.
Start your SQL Server 2017 upgrade with facts: run the read-only script, paste the result and pick SQL Server 2022, 2025 or a cloud target. Free, and nothing leaves your browser.
Start the free scan