End of Mainstream Support for SQL Server 2016

What a release SQL Server 2016 was! Query Store, temporal tables, and R Services were among the many exciting and notable features available in the June 1, 2016, release. And now, some five short years later, SQL Server 2016 is reaching its end of Mainstream Support. That’s right. The end is nigh. The actual date is July 13, 2021. See SQL Server 2016 – Microsoft Lifecycle | Microsoft Docs for details.

What does end of support mean for SQL Server 2016?

The end of Mainstream Support. Is that really as dire as it sounds? Because it sounds like I’ll be completely on my own. No support. At least no “mainstream” support, whatever that means. What happens if something goes wrong?

According to Microsoft’s lifecycle phases and definitions, here’s what Mainstream Support provides:

• Request to change product design and features
• Security updates
• Non-security updates
• Self-help support
• Paid support

Mainstream Support typically means that the SQL Server dev teams are still working on some aspects of the product. They are fixing some issue or bug, the are refining some aspect of the product they’d like to see improved, and they are addressing any security issues discovered internally or in the wild. It’s this active development from the teams that produces hotfixes and Cumulative Updates (CUs) for SQL Server periodically.

But all good things must come to an end. Microsoft cannot support a product forever. So, after five years, a product like SQL Server usually leaves Mainstream Support and enters into the Extended Support phase.

With Extended Support, Microsoft offers:

• Security updates
• Paid programs
• For eligible Unified Support customers, the ability to request non-security fixes for select products.

Notice that the only development performed for most customers in Extended Support is for security updates. That’s significant, and I’m glad Microsoft will continue to provide security fixes during Extended Support. But don’t expect other improvements to SQL Server 2016 to be released after July 13, 2021. And that’s noteworthy.

Like Mainstream Support, Extended Support typically lasts for five years.

So, should you starting planning to upgrade your SQL Server 2016?

For most companies with applications dependent on SQL Server, the answer is yes. Begin planning your upgrade because it may take some time to plan, provision, test, and upgrade/migrate. And while you’re at it, you may even find some opportunities to consolidate instances, reducing your overall SQL Server footprint and licenses.

In some specific scenarios, it may not be worth while to upgrade. For example, if you’re sunsetting an application or the vendor won’t support a newer version of SQL Server, an upgrade may not be worth it. In the latter case, though, you may want to look for another vendor.

The following posts talk about some of the factors to consider when deciding whether or not to upgrade your SQL Server. Check them out.

• Why Not Upgrading Could Be Risky for Your Data
• Should I Upgrade SQL Servers that Are Out of Support?
• Should I Upgrade Now? Or Wait for SQL Server 2019?
• 4 Options Now That Your SQL Server 2008 Is Out of Support

Want to work with The Sero Group?

Would you like some guidance while making an informed decision? Or would you like some assistance with the upgrade/consolidation project? We’d like to help.

We’ve helped companies with as few as one and as many as 150 instances of SQL Server. And we’ll be glad to work with your team, too.

Let us take help take the guesswork out of managing your SQL Servers. It’s easy and there is no obligation. 

Schedule a call with us to get started.