Is it a good idea to use management studio to manage SQL 2000?

Thank you, MaxYes , you can but I have my doubt that it is a good /efficient/wise
practice.
Why not just to upgrade to SQL Server 2005 and use SSMS?
"Maxwell2006" <alanalan@.newsgroup.nospam> wrote in message
news:%23obaw7$UGHA.5808@.TK2MSFTNGP12.phx.gbl...
> Thank you, Max
>|||I use management studio to manage both 2000 and 2005 servers. The reason
being that we only have 2005 in test environments at the moment (awaiting the
first service pack before production), and because I am used to the
Management Studio now, I would rather have everything in one place and in one
tool.
'Just upgrading your servers to 2005' isnt really that quick and easy when
you have management and politics involved. And there are some
incompatibilities between 2000 and 2005 that you need to resolve, such as the
use of table hints (ie, in 2000 you dont need the WITH clause in a SELECT
statement. In 2005, you need to specifiy WITH).
Andy Price,
Sr. Database Administrator,
MCDBA 2003
"Maxwell2006" wrote:
> Thank you, Max
>
>|||Maxwell2006 wrote:
> Thank you, Max
>
I've also been using SSMS for several months for managing both SQL2000
and SQL2005 and I haven't seen any problems. This biggest issue I can
think of right now, is that you can't use SSMS to edit/design DTS packages.
Regards
Steen