03-03-08, 00:07 #1Registered User
- Join Date
- May 2002
- General Deheza, Cba, Arg.
Unanswered: migrate to sql server 2005 or wait to 2008
I have a question. I work in BI (with sql server 2000) and this year (2008) my idea is migrate to 2005, but, consulting to expert in Microsoft technology, they suggested wait to 2008, sql 2005 have many problem, sql server 2008 was completed re-write.
The question is, what problem have sql server 2005?
03-03-08, 04:10 #2King of Understatement
- Join Date
- Feb 2004
- One Flump in One Place
2008 is not a complete rewrite. He may mean it was a complete rewrite of reporting services but the core engine, the main client tools etc are the same. The jump from 2005 to 2008 is shallower than previous iterations.
Depends on your needs. I wouldn't be keen on putting 2008 stuff into production until the first service pack (depending, by and large, on how things go in the early months). That might be too long for you, it may not.
03-03-08, 13:19 #3Registered User
- Join Date
- Dec 2002
Consider the needs of your business, the complexity of your environment and MS' projections and statements regarding SQL 2005 and SQL 2008.
According to a statement that I found on January 25th, 2008, SQL 2008 now will not be ready until Q3 2008 (my guess is late Q3 or even Q4, but that's a guess). Also consider:
1) SQL 2000 goes off mainstream support in April.
2) The features and capabilities in SQL 2005 are very attractive; you will pay a price in terms of the learning curve, but the rewards are pretty attractive
3) The upgrade from SQL 2005 to SQL 2008 is more evolutionary that the huge leap that we took from SQL 2000 to SQL 2005 (my head is still spinning from that one).
4) It may take several months (up to a year) before SQL 2008 is really production-class. We evaluated SQL 2005 in November 2005 and our judgment at the time was to hold off. We ended up waiting until December 2006 before rolling it out (and that rollout was just to our development environment). We didn't finish rolling it out to production until August/September 2007 and the wait was worth it (in my opinion). Consider that a similar wait for SQL 2008 might put you well into 2010.
Just some food for thought....
hmscottHave you hugged your backup today?