Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Stored Procedure Permissions
- Thread starter CliveW
- Start date
Hi
Grant permissions to their logons and deny them permissions to the stored procedures. Write click on the stored proc, all tasks, manage permissions.
If they logon with their nt domain account create windows groups on the server and add them to the relevant groups eg, basic, full etc.
Then create a sql login for the server group eg. server1\developers.
It is much easier to handle permissions thorugh groups than individual logins. In this way you can limit which databases the group accesses and what the members of the group can perform.
Very importantly NOBODY should be logging in as the 'sa' user. You can grant certain logins sysadmin rights such as the dba's but that should be all.
If the people can only have read access then give them the 'datareader' database role on the databases they need to access.
Right click on the login, go to the database access tab and choose the relevant database and select 'datareader' from the roles.
John
Grant permissions to their logons and deny them permissions to the stored procedures. Write click on the stored proc, all tasks, manage permissions.
If they logon with their nt domain account create windows groups on the server and add them to the relevant groups eg, basic, full etc.
Then create a sql login for the server group eg. server1\developers.
It is much easier to handle permissions thorugh groups than individual logins. In this way you can limit which databases the group accesses and what the members of the group can perform.
Very importantly NOBODY should be logging in as the 'sa' user. You can grant certain logins sysadmin rights such as the dba's but that should be all.
If the people can only have read access then give them the 'datareader' database role on the databases they need to access.
Right click on the login, go to the database access tab and choose the relevant database and select 'datareader' from the roles.
John
If they are currently logging in as sa, tell them not to and then change the password and don't tell anyone except dbas what it is!
(Of they are doing this, I bet some of your applications will break if you do it because they probably use sa in the connection string to avoid having to deal with permissions, this is why you give them fair warning that sa is being changed and they won't know what it is.)
(Of they are doing this, I bet some of your applications will break if you do it because they probably use sa in the connection string to avoid having to deal with permissions, this is why you give them fair warning that sa is being changed and they won't know what it is.)
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question