We're beginning to use Management Studio with some of our SQL Server 2000 databases and are having difficulty viewing and assigning permissions on objects to roles &/or users.
Even though permissions currently exist they do not appear in the "securables" tab on the properties page. In order to view the various permissions you must first manually select all of the objects and they will then appear.
Is there some way to get Management Studio to automatically display the objects that currently have permissions setup for the particular role or user
Basically, I'm looking for the same functionality as the permissions button gave from the role/user property page in Enterprise Manager in SQL 2000.

Setting Permissions using Management Studio
PhaneB
Yeah, I just ran into this too. Apparently not possible. See this thread:
http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=283470&SiteID=1
Of course, I am pretty sure sp_helprotect will give you what you want manually.
MPlowman
My god... this is a potentially massive UI problem.
I constantly have to manage permissions when developing new systems... what happend to the perfect list view from Enterprise manager.
Why make this so much more complicated... a simple setting of all permission for a Database will now take a huge amount of time and be incredibly tedious. I hope this gets sorted!
To make matters worse 2005 server won't let me connect 2000 Enterprise Manager to it!! However made this decision needs to to think about what they've done. :-(
Gkl
Terry Starkey
It isn't possible in Management Studio to automatically display all the objects a principal has permissions for. You have to manually add the objects you want to assign permissions for in securables control. You can do this by clicking the Add button and then selecting the securables you want to assign permissions for. The rationale behind this is that in large databases there could potentially be thousands of objects in the securables list for a principle, which would make the UI unusable.
If this is causing you significant trouble, I would appreciate it if you could file a defect report for this issue on the MSDN feedback center here: http://lab.msdn.microsoft.com/productfeedback/
Thanks,
Steve