March 2, 2009 at 3:59 am
We are planning to upgrade to SQL 2008 in the not too distant future, but we are currently on SQL 2000. Some of our developers are working on an application which will use SQL 2008, and they want my help checking what they've done so far.
What would be really nice would be if I could upgrade my machine to the SQL 2008 client tools to look at their server, and still work with my SQL 2000 servers.
Would this work OK? I've read that you have to download some extra things to be able to work with SQL 2000 DTS packages - is that the only thing?
I can't upgrade my machine until I am utterly sure that it won't mess up anything with the administration of the old databases.
Another completely different question - are SQL 2008 client tools from SQL Express different from the Standard/Enterprise edition client tools?
Thanks,
Rachel.
March 2, 2009 at 4:55 am
You can manage 2000 databases from the 2008 Management Studio. Out of the box you can't edit DTS packages and I'm not sure how you would go about doing that. Probably best to keep the 2000 client tools installed. They can operate side-by-side with no issues.
To my knowledge, Express doesn't have client tools. You would be using the same Management Studio that you use for other things. However, if you don't buy the Standard/Enterprise editions, you won't have a gui at all with the free express. That's part of what makes it free.
"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
March 2, 2009 at 4:57 am
Brilliant - thanks.
March 2, 2009 at 5:47 am
OK, so I've installed Management Studio for 2008 side by side with the SQL 2000 install - so I can still use that on my old server. Out of interest, I tried to look at my SQL 2000 server through the new management studio, and it looks fine until you try and do "Activity Monitor", which says:
This operation does not support connections to Microsoft SQL Server Enterprise Edition version 8.00.2039.
Yet this article http://msdn.microsoft.com/en-us/library/ms175518.aspx implies that it should be doable.
Am I missing something?
March 2, 2009 at 6:25 am
I've never been able to do it either. When I'm working 2000 instances I just go back to sp_who2 and other TSQL methods for seeing what's going on. Not as nice, but there you go. All the more reason to push upgrades.
"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
March 2, 2009 at 6:26 am
Reading that BOL entry, I'll bet it's a holdover from 2005. It did work in 2005, but it doesn't seem to in 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
March 3, 2009 at 12:30 pm
Yep
I have SSMS 2008 on my laptop, managing 2000/2005/2008 boxes
Activity Monitor don't work for 2000 (SSMS 2005 does), but that's more reasons to upgrade 2000. I rely on sp_who2 and other procs
DTS or Maint. Plan editing sucks in SSMS 2008 for 2000 as well
so I remote desktop to 2000 boxes to do it on the box
I have SSMS 2005 installed locally as well, but I rarely use it
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply