January 15, 2009 at 12:02 pm
I am new to this part of SQL.
Is there a less painful way to set user permissions than manually checking ON litterally hundreds of check boxes from the Mirosoft Management Console ?
Regards
January 15, 2009 at 12:06 pm
Create database roles for different types of user access, assign database and object permissions to database roles only, and then add individual users to the correct database roles.
January 15, 2009 at 12:56 pm
You should be able to grant users & roles access to the Schema.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
January 15, 2009 at 1:07 pm
Michael Valentine Jones
Create database roles for different types of user access, assign database and object permissions to database roles only, and then add individual users to the correct database roles.
Even though this reduces the amount of clicking, I still find the whole tedious.
RBarryYoung
You should be able to grant users & roles access to the Schema.
Now, this sounds like something that can be done wholesale. But just how can I do this ?
Regards
January 15, 2009 at 3:13 pm
Erp! Sorry, I missed that this was SQL Server 2000...
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
January 15, 2009 at 3:29 pm
J (1/15/2009)
Michael Valentine JonesCreate database roles for different types of user access, assign database and object permissions to database roles only, and then add individual users to the correct database roles.
Even though this reduces the amount of clicking, I still find the whole tedious...
Feel free to write SQL Scripts or procedures to make the whole process simpler if clicking is too tedious.
January 15, 2009 at 5:09 pm
In addition to Michael Valentine Jones' answer be sure to review the Public Role, remember:
New Information - SQL Server 2000 SP3.
1. public role is a special database role to which every database user belongs. The public role:
2. Captures all default permissions for users in a database.
3. Cannot have users, groups, or roles assigned to it because they belong to the role by default.
4. Is contained in every database, including master, msdb, tempdb, model, and all user databases.
5. Cannot be dropped.
6. To protect against unauthorized data access, minimize the permissions granted to the public role. Instead, grant permissions to other database roles and to user accounts associated with logins.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply