Earlier this week, Microsoft SQL Server 2008 and 2008 R2 support ended. Lots of people were caught unaware of the same. Last two weeks has been extremely busy for me as lots of organizations have been procrastination of the SQL Server upgrade and suddenly started to react when the support ends date is approaching. Once users upgrade from SQL Server 2008/2008 R2 to the different version, quite many of them are in for surprise as well as they get poor performance as they had not planned the upgrade properly and also easily miss out the MUST DO steps after SQL Server upgrades. All the emails and calls, lead me to write this blog post where I am mentioning Microsoft’s Official Support End Dates for different versions of SQL Server.
Support End Date
| SQL Server Version | Support End Date |
| SQL Server 2005 | 2016/04/12 (April 12, 2016) |
| SQL Server 2008 / SQL Server 2008 R2 | 2019/07/09 (July 09, 2019) |
| SQL Server 2012 | 2022/07/12 (July 12, 2022) |
| SQL Server 2014 | 2024/07/09 (July 07, 2024) |
| SQL Server 2016 | 2026/07/14 (July 14, 2026) |
| SQL Server 2017 | 2027/10/12 (October 12, 2027) |
If you are using any of the above product, I suggest you set up calendar alert six months ago and a month ago to remind you that you have to get started to upgrade your SQL Server.
Please note that, once official supports ends Microsoft will not support the product and will not release any further updates to the same. Additionally, if you got into trouble with SQL Server, Microsoft may not support you with the product as well. It is strongly recommended that you upgrade your SQL Server to the latest version of SQL Server.
Slow Performance After Upgrade
The most common issue my clients are facing after SQL Server upgrade is the slower performance of the SQL Server. This is an extremely common observation. Most of my clients when they upgrade their SQL Server to even more powerful hardware and latest software, they expect better performance from their SQL Server but once the upgrade is complete, they actually see the opposite behavior of SQL Server. This is due to not following a MUST DO checklist for SQL Server Configurations and Databases.
If you ever face slow SQL Server Performance after the upgrade, you can always reach out to me. I rather prefer that you reach out to me before you engage with SQL Server upgrade so I can help you strategize your SQL Server upgrade and you do not face any performance degradation after the upgrade. My clients give me rave reviews for Comprehensive Database Performance Health Check as it focuses on your SQL Server pain points and helps you gave maximum performance.
Reference:Â Pinal Dave (https://blog.sqlauthority.com)
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.