One of my clients is primarily using SQL Server 2008 R2 for most of their application. They are also using the same for their own clients and are managing over 100 installations of various versions of SQL Server. They have frequently hired me for Comprehensive Database Performance Health Check for their server and I must accept their business is nearly 10% of my total business. They recently reached out to me with the following email. Let us read it together.
“Pinal,
As you have worked with us many times, we work with every single SQL Server version from SS 2008 R2 to SQL Server 2017. We currently have no plans to upgrade SS 2008 R2 for next few years. Our senior management is a very concern with all the information they are receiving about the end of the support for SS 2008 R2. We very well understand that we need to upgrade to the latest version of SQL Server but we are not going to as there are many reasons behind it.
Here is the question for you – If we do not get official support for SQL Server 2008 R2, will you support us with any help we need with the regards of SQL Server 2K R2?”
As I have worked with this client for over the last 4 years and helped them upgrade many SQL Server from version 2000/2005 to the latest version, I know their challenges and unique situation why they can’t immediately migrate few of their clients to latest version. Here is one line response I gave them.
Of course, I will support SQL Server 2008 R2 beyond July 9th, 2019.
Afterward, I received a special thank you email from their CTO as well. Well, just so you know I do not support that you stay at the older version of SQL Server. However, if due to any reasons, if you are going to continue using the out of support version of SQL Server, count on me. I will help you with any issue with SS 2008 R2, till you decide to upgrade to the latest version of SQL Server.
So if you have any issue with SQL Server Performance Tuning for any version of SQL Server, please do not hesitate to reach out to me, I will support you as long as you need help.
Reference:Â Pinal Dave (https://blog.sqlauthority.com)
