Management Studio with SQL2000

Question

Management Studio with SQL2000

MissPukeyCow

Ten Centuries

Points: 1146
More actions
September 18, 2006 at 1:46 pm

#172497

Hi y'all - Are there any known issues accessing SQL Server 2000 databases with the SQL Server 2005 tools that replace Enterprise Manager and Query Analyzer? I'm thinking of items that may stop us effectively accessing the existing corporate environments, especially production when we need to provide support. Thanks!!

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

MarkusB SSC-Dedicated Points: 37370 More actions · Answer 1

The only two issues I'm aware of are the fact that you can't edit DTS packages unless you download the editor which is included in the 2005 feature pack and DB diagrams won't work for SQL 2000 databases. Other than that you should be fine.

Markus

[font="Verdana"]Markus Bohse[/font]

MissPukeyCow Ten Centuries Points: 1146 More actions · Answer 2

Thanks - are they any issues from a developer's perspective?

John McC Hall of Fame Points: 3410 More actions · Answer 3

I only use EM to create/edit DTS packages now. Everything else is done via the Management Studio.

I love the ability to modify without having to script out an ALTER Table / Proc / View.

-------------------------------------------------------------------------
Normal chaos will be resumed as soon as possible. :crazy:

Marino van der Heijden SSC-Addicted Points: 412 More actions · Answer 4

Also, take a look at this thread: http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=149&messageid=309030

It describes problems with editing User Defined Functions on a SQL2000 machine via Management Studio.

DonaldW SSCarpal Tunnel Points: 4525 More actions · Answer 5

I've been using SSMS for a couple of months to manage my SQL Server 2000 development work and so far I have not run into any problems. (I don't use DTS in my current job, so that's a non-issue for me.) SQL Server 2005-specific features simply don't work (DB diagrams) or are not available (2005-stlye schemas) when operating on a 2000 database. So far I have not had a moment's trouble with any of the stored procedure work I've been doing.

One thing I absolutely LOVE about using SSMS is that you can open a stored procedure in Modify mode so you can read the whole thing and even change it, if necessary. It's not that hard to script it off as a file from EM then open it, but being able to skip the scripting part is great. This is an issue for me because I work with a database that someone else created and I don't have their source files for the stored procedures. If I want to work on one I have to open it up and get the code. In 2000 I would have had to script it first then open it, etc. This is a time saver.

HTH

Cheers,

Don

MissPukeyCow Ten Centuries Points: 1146 More actions · Answer 6

Alright, that's cool that a buncha y'all already have it up and running and that there are no HUGE issues. We'll be rolling out mgmt studio to a couple of our developers first for them to try out. I gave them a heads-up of the problems you have all run into, thank you SOOOOOOOOOOOOOO much for your help, muchly appreciated!

Pukey

MissPukeyCow Ten Centuries Points: 1146 More actions · Answer 7

One more question - is there a way for me to roll out management studio and only management studio without the other client tools??