September 13, 2006 at 8:50 am
I am using Microsoft SQL Server Management Studio 9.00.1399.00
I have a very simple problem (hopefully easily resolved!)
I created a role and allocated securables against it.
When I go back into the role properties the securables that I previously allocated do not show up.
Does anyone know what I need to do ?
regards
Liz
September 14, 2006 at 7:38 am
When you open the role properties, the top window (securables) is blank. The button says "Add" which seems to say Add permissions. This is not what the Add button does. If you click "Add" you will be prompted to select which objects, or types of objects are to be used to populate the securables window. Once the objects are added to the top window, the bottom window will show what permissions (if any) are granted on the object ( that is currenty selected in the top window ). Once the objects are in the top window, you can both view and change permissions on the highlighted object.
September 15, 2006 at 7:29 am
I click add and select the securables and add the permissions and save. However when I go back into look at the properties no securables show up.
i.e. I've been doing what you suggest above but it doesn't seem to save them. Is it likely to be a configuration problem ?
September 15, 2006 at 7:35 am
I don't believe it does save them. Each time you want to see the permissions on a securable, you need to re-"Add" the securable to the top window.
September 15, 2006 at 7:43 am
If it doesn't save them - what is the point of it then ?
September 15, 2006 at 7:47 am
Sorry - I got the point of it just after sending my last reply!!
Thanks for the help.
October 16, 2006 at 2:54 pm
I have an issue with this as well. Is there any way to find out which "securables" have been secured? I have thousands of tables, of which half have been granted the "select" permission. So, I don't want to have to add 1000 tables, and scroll through them to find the 500 that have permissions. Is there something somewhere that will allow me to view only the objects that have any type of permissions against them. If not, this seems like a major bug in Management Studio.
October 24, 2006 at 10:24 am
Hello,
i have the same problem. The only solution seems to add then securables as described above or to use the following statement: exec sp_helprotect NULL, 'rolename' or exec sp_helprotect NULL, 'username'. I mean, referring to sql server 2000, this ist a step back for sql server 2005. I also have to look in dbs with some hundreds of tables and special rights for roles and users on parts of the tables. The new behaviour is not good for practive, i think. Or is ist really a bug, that the securables, i have added, are gone and must be re-addet again? I cannot imagine after service pack 1...
Especially migration of sql server 2000 to sql server 2005 seems to be pushed in future...
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply