Last week, you used SQL ConstantCare® to analyze 2,396 SQL Servers across a variety of versions:
- 15% (362 instances) of SQL Server 2008 and 2008 R2
- 18% (438) SQL Server 2012
- 27% (650) SQL Server 2014
- 32% (777) SQL Server 2016
- 7% (169) SQL Server 2017
That means 15% of your servers are going to be out of support in about 106 days: SQL Server 2008 & R2 both end support on July 9th.
So I’m curious:
- What does your company plan to do about that?
- If the answer is “nothing,” what have you tried to convince them otherwise? Or have you?
- What’s the single biggest thing stopping you from moving to a supported version?
I’m asking because it influences how we support these older versions in the First Responder Kit, SQL ConstantCare, and Consultant Toolkit. For years, I’ve said, “If Microsoft can’t support it, neither can we,” but given the relatively high market penetration of these old versions, I’m not sure I can still say that. (After all, if I look at the market numbers, it’s more profitable to support 2008 and R2 right now than it is to support 2017!)