The Road to Katmai
-
It's been an interesting week in the database world. After a whirlwind tour at TechEd two weeks ago, I disappeared for a week in Mexico to unwind and recharge. I came back to find that Katmai information is slowly trickling out and it looks interesting. I think at this point my thoughts are to recommend that you hold off on upgrading to SQL Server 2005 if you haven't, and instead get ready to upgrade to SQL Server 2008 next year.
First a quick note: Don't try to install the June 2007 SQL Server 2008 CTP on any machine where you have SQL Server installed. I had written some comments on my impressions at TechEd, but the comments showed people having issues and luckily I got Andy's Risk Averse Installation before I put it on my laptop. Instead I wisely set up a VPC and installed it there. It won't work with SQL Server 2000 and there are tool problems with SQL Server 2005, so I'd recommend keeping it separate for now.
The best comparison I can make, and one I'll be making more as we go forward, is to look at SQL Server 7 and 2000. V7 was a paradigm shift from 6.5, which I'd been using for what seemed like forever at the time (and for a few years afterward). When SQL Server 2000 was released (after being upgraded from SQL Server 7.5), it didn't seem like a huge amount of new stuff. However it was way more stable and the changes made built a very, very solid product that I would still recommend today if support were not ending next year.
I think SQL Server 2008 is similar. Lots of the little things that have been learned with SQL Server 2005 will be fixed, the improvements are minor, but some are significant (think policy), and I think this will be the new standard for SQL Server for the next 5 or 6 years, much like SQL Server 2000 has been in the past.
Steve's Pick of the Week : Cumulative update package 2 for SQL Server 2005 Service Pack 2 is available. It was promised and it's happening. This updates you to build 3175 and includes all the updates (quite a few) since Service Pack 2. Now if we can just get this as a slipstream. Right now you have 3 installs for a new server: RTM, SP2, this update. -
I just want to know how many company has migrated from SQL Server 2000 to 2005 and running in production. While we are still struggling with SQL Server 2005 and how do they expect us to do SQL Server 2008?
Maybe my company is the only one that is struggling and our developers and DBAs are stupid.
-
You aren't the only one - that's for sure. Where I was before, they still have SQL Server 7.0 machines in production, in addition to the SQL Server 2000 machines. When I was there, there weren't any plans to upgrade to 2005, as their business needs weren't calling for it. So they'll have fun getting to 2008... heh.
-
Wow here I thought 2008 was only BI stuff .....we have a few 2005 clusters ect but the rest of the enviroment is 2000 - all our consolidation servers ect ..we planned to go to 2005 ..so what must a person do now ? ....couldn't microsoft hold back 2005 and rather aimed getting 2008 in ..I understand that microsoft will have some plan with the licensing model ..but what about budget's that have been approved , planning for application upgrades ect ..don't tink this was a clever move ....
But hey still thinks SQL server kick's ass !!.....
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply