SQL Server 2008 Support Is Ending. Now What?

RIP SQL Server 2008 support. Unless you do your DBAing from under a rock, you probably already know that Microsoft ended support for SQL Server 2008 over the summer.

What Does the End of SQL Server 2008 Support Mean for Me?

Essentially, the end of support means that if you don’t migrate to a newer version, you are on your own. Some of the biggest implications of the loss of support include: 

• Microsoft will not issue security patches or updates, which will leave those who don’t upgrade vulnerable to cyberattacks. Cyberattacks are becoming more common and more destructive, so leaving your organization unprotected is inadvisable.
• They will no longer help resolve issues, so if you can’t figure out how to fix your own problem, you will need to hire someone who can. That could get expensive fast.
• Your SQL Server performance monitoring tool may not work with SQL Server 2008. SQL Server performance monitoring is essential to maintaining healthy, functional instances. If your monitoring tool is obsolete, you are putting your company’s operations and bottom line at risk.

What Can I Do?

Well, you can ignore it and hope that nothing bad happens. (Just kidding, that’s not really an option.) You have a few directions you can go, and which one you choose really depends on how long-term a solution you are looking for.

Option 1: Get an extension 

Purchasing extended security updates from Microsoft is really just a bandage, not a real solution to losing SQL Server support. First of all, the extension isn’t available to everyone. Those with an active subscription to the Software Assurance licensing program are able to purchase the extended security updates. The service is also available for no additional charge if you’re running SQL Server 2008 in the cloud using Azure Virtual Machines. Everyone else is out of luck.

The other big problem with opting for an extension rather than an upgrade is that the extension only buys you three more years; it doesn’t solve the problem for the long term. 

Option 2: Upgrade to a newer version of SQL Server

If you’re ready to migrate to a newer version of SQL Server, how do you decide how much newer? 

Brent Ozar compiled this overview of the different SQL Server versions currently available and the reasons why you should or should not select a particular version. For example, according to Ozar, SQL Server 2012 and SQL Server 2014 are good choices if you are looking for a well-known, well-documented product that lots of people know how to use. 

However, while there are some good features in both of these versions, SQL Server 2012 doesn’t have encryption capabilities, and they both lack some of the modern features that enable peak performance.

SQL Server 2016 is a good choice if you don’t want to switch versions again for a while, you need lots of data security features, or you want built-in query plan monitoring. The downside to SQL Server 2016’s cutting-edge features is that you won’t find a lot of documentation to teach you how it all works.

SQL Server 2017 has all the latest and greatest features, but you will be applying patches on the regular as all the kinks get worked out. Still, Ozar states it’s a good choice if you want easier future upgrades or you need features like columnstore indexes. 

SQL Server 2019 isn’t commercially available yet, but if you aren’t in a huge hurry to upgrade, it may be worth waiting for its general release. However, as with any new version, be prepared for heavy patching and frequent updates as problems are identified and resolved.

If you decide to bite the bullet and upgrade to a newer (but not the newest) version of SQL Server, make sure you pay attention to the end of support dates for whichever version you choose. Support for some of the older-newer versions ends relatively soon. For example, support for SQL Server 2012 ends in 2022, but support for SQL Server 2016 will carry you until 2026.

Option 3: Migrate to Azure

Moving SQL Server 2008 to Azure is a good choice if you aren’t quite ready to upgrade to a new version but you also aren’t OK with not having any support. As mentioned above, Microsoft is offering extended security updates free of charge if you migrate SQL Server to Azure. This not only buys you some time to decide your next move, but deploying in Azure also includes benefits like: 

• It’s cost-effective
• There’s little to no downtime
• Azure is secure
• You get fully managed services

Arguably the most important benefit is that once you deploy SQL Server 2008 in Azure, it’s easy to upgrade to your chosen SQL Server version at the end of the extension period. You will have to upgrade anyway, and the cloud simplifies the process.

As we bid SQL Server 2008 support a fond farewell, weigh your options carefully to determine your best next move. Consider which solution meets your SQL Server needs not only today, but also in the medium to long term. Remember that more end of support dates are on the horizon, and a migration to any of the newly released versions comes with its own set of benefits and challenges.