January 20, 2009 at 1:23 pm
It is my feeling that SQL 2000 is not so popular as SQL 2005 nowadays.
This makes me think how long it will take for SQL 2005 not to be so popular as SQL2008.
Another 2 years? 3 years?
What do you think?
Gotta get ready to pick up SQL 2008. 🙂
January 20, 2009 at 1:33 pm
I think you will find SQL 2000 is more popular than you think, there are still a lot of 2000 instances out there.
Almost everyone installing from new though will be going for 2005, and I would predict by the end of this year most will go for 2008.
2005 may even get squeezed out with people going directly to 2008 from 2000, so I think 2008 will be more popular within a couple of years.
---------------------------------------------------------------------
January 20, 2009 at 3:19 pm
Not only is SS2000 popular, but I have a feeling there are many companies in the same boat we are: we'll never have enough staff to have time to migrate all our apps off of it to 2005/2008/2045!
Even migrating a single app to 2005 has been extremely painful, mostly having to deal with SSIS and the new security model.
January 20, 2009 at 3:21 pm
We still use 2K in production. A lot of companies that have highly customized software packages built on earlier versions have a very hard time upgrading.
January 21, 2009 at 6:30 am
The overwhelming majority of our production systems are 2000. We're starting an initiative this year to get them upgraded to 2008 over the next two years because, in 2010, extended support for 2000 is scheduled to end.
Regular 2005 support will extend just past the release of the 2010 (or whatever it actually is when it's released) version of SQL Server. Then it will go into extended support until the next release and then it goes out of support. In theory, assuming MS sticks to a strict two year release cycle (and I hope they don't) 2005 will go out of support after the 2012 release.
The fact is, at this point, I think most people are still in 2000. Upgrading to 2005 is a waste. You should only be upgrading to 2008.
"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
January 21, 2009 at 6:57 am
Grant Fritchey (1/21/2009)
The overwhelming majority of our production systems are 2000. We're starting an initiative this year to get them upgraded to 2008 over the next two years because, in 2010, extended support for 2000 is scheduled to end.Regular 2005 support will extend just past the release of the 2010 (or whatever it actually is when it's released) version of SQL Server. Then it will go into extended support until the next release and then it goes out of support. In theory, assuming MS sticks to a strict two year release cycle (and I hope they don't) 2005 will go out of support after the 2012 release.
The fact is, at this point, I think most people are still in 2000. Upgrading to 2005 is a waste. You should only be upgrading to 2008.
Grant, all the info I can find shows SQL 2000 SP4 going out of extended support on 9th april 2013, e.g
http://blogs.msdn.com/sqlreleaseservices/Default.aspx?p=2
http://support.microsoft.com/lifecycle/?p1=2852
and 2005 is good till 12th april 2016
http://support.microsoft.com/lifecycle/?p1=2855
However, with SQL 2000 out of mainstream support and 2005 and 2008 mature now's the time to start looking at upgrading. Going straight to 2008 would be best technical option but there may be extra costs depending on how you are licensed and third party apps still might not be certified on 2008.
---------------------------------------------------------------------
January 21, 2009 at 7:06 am
george sibbald (1/21/2009)
Grant Fritchey (1/21/2009)
The overwhelming majority of our production systems are 2000. We're starting an initiative this year to get them upgraded to 2008 over the next two years because, in 2010, extended support for 2000 is scheduled to end.Regular 2005 support will extend just past the release of the 2010 (or whatever it actually is when it's released) version of SQL Server. Then it will go into extended support until the next release and then it goes out of support. In theory, assuming MS sticks to a strict two year release cycle (and I hope they don't) 2005 will go out of support after the 2012 release.
The fact is, at this point, I think most people are still in 2000. Upgrading to 2005 is a waste. You should only be upgrading to 2008.
Grant, all the info I can find shows SQL 2000 SP4 going out of extended support on 9th april 2013, e.g
http://blogs.msdn.com/sqlreleaseservices/Default.aspx?p=2
http://support.microsoft.com/lifecycle/?p1=2852
and 2005 is good till 12th april 2016
http://support.microsoft.com/lifecycle/?p1=2855
However, with SQL 2000 out of mainstream support and 2005 and 2008 mature now's the time to start looking at upgrading. Going straight to 2008 would be best technical option but there may be extra costs depending on how you are licensed and third party apps still might not be certified on 2008.
Oops. I hadn't checked in a while. Last time I looked it was 2010. I guess I need to update my documentation locally. Sorry about the misinformation.
"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
January 21, 2009 at 7:12 am
Hi
Here is a scenario, i attended a Conference on SQL 2008 Nov last year, when we took a poll there were 95% of people who are still using SQL 2000, they have no plans to convert to 2005 at least for the next 2 years or so, so this will give u a example of how famous 2000 is, and some were more interested to jump to 2008 rather than 2005 😀
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply