February 2, 2015 at 1:10 pm
What is the general opinion of Lifecycle for OS and Database Platform. I had always lived by 3-4 years for OS and the same for Database Platform. So for example of the first full release of Windows 2008 or SQL Server 2008 was August 2008. Those platforms should be replaced by no later than summer 2012. new company does not really have a policy on this and turned down going from 2008R2 to 2012. The fact that the last service pack for 2012 will be release later this year and that 2014 is fully released worries me. We run mostly 3rd party apps and tools and getting support for 2008r2 issues is becoming it's own issue. From both a hardware and software perspective companies are not putting any resources for 2008r2 and have not for a while.
February 3, 2015 at 5:37 am
It's really up to the organization. I know a few places that still have SQL Server 2000 in place (I'm aware of two places that have SQL Server 7.0 running). "If it ain't broke, don't fix it" is a pretty common refrain from a lot of organizations. And then, you're dealing with third party support which frequently has contractual limitations on what server version you can run things on.
I don't think there is a standard. If there was one, I'd be comfortable with 3-5 years, with 3 being the goal and 5 the outlier. That would be roughly in keeping with Microsoft's support cycle too.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply