This week, let’s cut to the chase with a single image that speaks volumes about the urgency of the situation:
If that visual cue wasn’t clear enough, let’s spell it out plainly.
SQL Server 2012 Support Officially Ends This July
Mark your calendars, folks. July 12th of this year is the definitive end of extended support for SQL Server 2012. There are no asterisks, no footnotes about “mainstream” versus “extended” support – this is the final curtain call. While extended security updates might linger for a few more years, remember they are solely for security vulnerabilities. In less than 141 days, your SQL Server 2012 instances will be operating without any official support. Imagine reaching out to Microsoft for assistance, only to be met with the recommendation to upgrade – it’s not just a suggestion, it’s the inevitable solution. Frankly, after a decade of service, it’s a completely reasonable expectation.
It Wasn’t Always a “Bad Version” Meme
Let’s be fair; SQL Server 2012 wasn’t always considered a “bad version.” In fact, back in its day, it was quite the opposite. If we look back at its predecessors, 2008 and 2008R2, SQL Server 2012 was a significant leap forward. While my review of 2008 R2 highlighted its incremental nature, 2012 brought genuine innovation to the table.
Remember the excitement around Always On Availability Groups? It was touted as a revolution in high availability and disaster recovery. Though the initial implementation had its rough edges, it laid the groundwork for a feature that has become a cornerstone of modern SQL Server deployments. Similarly, columnstore indexes in 2012, while initially limited to read-only tables, were a bold step towards advanced data warehousing capabilities.
These features, though perhaps not perfect at launch, represented significant investments in technologies that Microsoft has diligently refined and enhanced. Today, in 2023, features like columnstore indexes and Availability Groups are robust and widely adopted.
(pauses, as if listening to an off-screen voice)
Hold on a moment…
(continues listening)
I’m hearing that Always On Availability Groups still have their complexities, but their widespread use is undeniable. (Is “complexities” the right word? Perhaps “nuances”?)
But let’s refocus. The crucial takeaway is this: SQL Server 2012 in 2023 is essentially a “bad version” meme. It’s become outdated and unsupported. If you’re still relying on 2012 in your production environment, the time for discussion is over – it’s time for action. Start the conversation with your business stakeholders with a straightforward question: “Is it acceptable for application ___ to operate on an unsupported and increasingly vulnerable version of SQL Server?” The answer, unequivocally, should be no. Don’t let your database infrastructure become the IT equivalent of a dated, out-of-touch meme. Upgrade now to a supported, secure, and performant version of SQL Server.
