RIP SQL Server 2005

Microsoft Ends Support For SQL Server 2005

To quote Microsoft:

“If you are still running SQL Server 2005 after April 12, 2016, you will no longer receive security updates. Now is the time to upgrade to SQL Server 2014 and Azure SQL Database to achieve breakthrough performance, maintain security and compliance, and optimize your data platform infrastructure.”

So what does this mean for those of us who will continue to maintain SQL Server 2005 Service Pack 4 tomorrow?  Maybe a lot or maybe very little.  We have known since April of 2011 that the extended support cycle could not last forever…and it didn’t.  So…no more security patches for the product.  Some companies, under special arrangements through Premier Support agreements, will continue to operate with a secure product until those arrangements conclude.  Where does that leave those of us who have yet to migrate to a more recent product?  In regard to SQL Server 2005 and considering we work in Austin/Central Texas, we should frame the situation with 2005 as a true Texan would;  “She’s got one wheel down and the axel dragging.”

Need help making the switch to SQL Server 2014? Contact Magnet Solutions Group at (512) 298-2101 for more information.

Time to Move to SQL Server 2014

Time to move on folks.  Get your 2005 house in order and make the leap to SQL Server 2014.  Microsoft states that; “SQL Server 2005 can be upgraded in-place to SQL Server 2014” (32 bit versions excluded).  The other option, as mentioned in the statement above, is a move to Microsoft’s cloud Azure SQL Database v12 which is claimed to offer close to “complete compatibility” with the stand-alone SQL Server products.  Additionally, Microsoft provides a tool to assist in the migration.

Many enterprise deployments of SQL Server 2005 will continue in operation even with the lack of support.  We have seen this in any number of Microsoft products through the years, and with little or no detrimental effect.  However, all of us in IT services know that we are just buying a little more time.  Maybe just to get in the next budget year or maybe just to wind down a legacy product configured to use that platform.  There is always some justification to continue. Now it would be best to make plans for that upgrade.  Procrastination is not your friend in the event there is a failure.

The cost of   migrations at the end of life for a product can be significant.   But again, our concern is for what the cost and impact would be in the case of a security breach should we not migrate.

So again, as we would say in Texas, “Keep your saddle oiled and your gun greased” cuz you’ll never know what might be up around the network bend.