SQL Server support end dates belong in upgrade planning before the deadline. Here are the dates for every release from SQL Server 2005 to SQL Server 2025, and what to do with them.
| SQL Server release | Standard extended-support end, Pacific date |
|---|---|
| 2005 | 12 April 2016 |
| 2008 / 2008 R2 | 9 July 2019 |
| 2012 | 12 July 2022 |
| 2014 | 9 July 2024 |
| 2016 | 14 July 2026 |
| 2017 | 12 October 2027 |
| 2019 | 8 January 2030 |
| 2022 | 11 January 2033 |
| 2025 | 6 January 2036 |
The table shows standard extended support end dates. Mainstream support and service-pack servicing have separate periods. Eligible Extended Security Updates form a separate program. As of October 2026, standard extended support for SQL Server 2016 and every older release has ended.
Check the exact edition, service level, date and ESU eligibility for your own servers. Use the published Pacific end date; search summaries can format time zones differently.
I like a reminder six months and one month before each date. Those are starting points; not every upgrade fits those windows. Rehearse recovery, compatibility changes and application behavior, and capture a performance baseline. A newer engine or faster hardware does not guarantee every plan improves.
If you want a second pair of eyes on an upgrade plan, my Comprehensive Database Performance Health Check starts with exactly this list.
A lifecycle date is not an upgrade rehearsal, it is a deadline to plan around with tested recovery and applications.
Published by Pinal Dave on SQLAuthority. More of my work at pinaldave.com.
Discover more from SQL Authority with Pinal Dave
Subscribe to get the latest posts sent to your email.
2 Comments. Leave new
I believe you meant 4/12 is April 12th, not March 12th.
That is correct and I have reflected the same. Thanks for bringing to my attention.