Apparently, the first (and only) CTP of SQL 2005 SP1 has just been posted:
http://blogs.msdn.com/euanga/archive/2006/03/16/552349.aspx

Alex, I certainly agree that SQL 2005 is a new product, and a shift in paradigm. I even agree, at the risk of being strangled by other dbas, with doing away with some of the old commands and features that arn't terribly useful. I guess what I was trying to get at is: why take away something that's useful, and not replace it with anything? Like bookmark, for example... But that's another story

John, I was talking about connecting to sql 2000, in which case sys tables are still there. U r right, in 2005 you'd want to use DMVs.

Just to nitpick a bit (it was a nice article), but last I heard the systables are being depricated, as well, in favor of the system views. As such you would want to do away with the calls to sysobjects:

SELECT name FROM sysobjects
should be
SELECT name FROM sys.objects

and

Select crdate as DateCreated
From dbo.sysobjects
should be
Select create_date as DateCreated
From sys.objects

Nice article.

External tools also don't work the same in sql2k5.  Managing 100+ sql server environments, using the [SRV] parameter in enterprise manager's external tools is handy for accessing explorer, server manager & event viewers on current sql server environments.  Even though sql2005 books online says it works the same, it doesn't work in management studio.

Polling is controllable in sql 2k enterprise manager, but no control in sql2k5 management studio.  With several DBAs having management studio open with 100+ servers registered = a lot of clutter in security event logs, unneccessary network traffic & overhead on workstations.

-- J.T.

"I may not always know what I'm talking about, and you may not either."