Some other problems using SSMS with a SQL 2000 instance:

• You can't view or modify multi-statement TVFs. If you try, you get an error message indicating that you don't have permission to access the object, even if you are the dbo.
• You can't view or modify full-text indexing properties. This produces a very similar error message.
• You no longer have the option to see a list of permissions for a user. Instead, you have to select the specific objects, and then select each object in the list to see the associated permissions.

The first two are apparently fixed in SP1, but there doesn't seem to be any indication of when we can expect to see it. The only current workaround is to re-install the SQL 2000 tools.

To work around the third problem, you can use the sp_helprotect procedure. However, this doesn't provide any simple way to see the list of objects which a user doesn't have access to.

Great article.  I'm glad that I am not the only one who is missing these features.  I especially miss the ability to DTS objects, such as SPs, from one db to another.  That feature is now completely gone in SSIS!  I don't see any reason why MS should not add it back in sp1.

Please MS, give us an easy way to script or copy stored procedures because some organizations rely on low tech admins to perform such tasks.  It used to be available in the SQL 2000 DTS wizard and was called "Copy Objects and Data Between Servers" but now that functionality is completely gone in SSIS.  It supposedly can still be done by creating a SSIS project in Visual Studio but that is too much for your average admin.

You're right, I think Advil's stock is going to go up as a direct result of this.

I would like to emphasis that SQL 2005 is another product versus just another version of SQL 2000. On the surface it may seem some of the features have disappeared in the product, but in actuality, it provides the DBAs with more flexibility.  For instance, there is an extended stored procedure facility that allows DBAs to write his own sprocs that would enhance the current xp_fixeddrives routine currently provided by today's version of SQL.  SQL 2005 also has the additional benefit of allowing the programmer or DBA wrote routines using VB.NET or C#.

In case to replace xp_fixeddrives just use scripting runtime library class Drive, which has property FreeSpace.

Some good new features, some missing old friends...what can you do. Do register your comments with MS and maybe somethings will be restored.

You will be upgraded. Resistance is futile. (Bill Gates)

Alex

I agreed with you.  SQL Server 2005 is another product.  I feel liked I have to learn SQL Server all over again.