Re: SQL 2005 public role
- From: "Uri Dimant" <urid@xxxxxxxxxxx>
- Date: Tue, 28 Mar 2006 14:48:26 +0200
Hi
Who is an owner of this SP?
Avoid adding logins to the public role. Grant an execution permission to the
stored procedure ( be aware if you are using dynamic sql within this sp ,
you'll have to grant permissions on underlying tables as well)
"Franky" <Franky@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:37C732BA-FAD2-43F8-A0EF-1F23383674B8@xxxxxxxxxxxxxxxx
I've made a stored procedure stp_LogError which will be used to have a
central errorhandling system.
(So in the usermade stored procedures in the catch-block stp_Logerror will
be used to log the error).
I've granted execute permissions for stp_LogError to the public role.
Afterward I added a NT-login to the server and added this login to the
role
public in the database.
I granted this user execute rights to a stored procedure in which
stp_Logerror is used.
When this user calls this stored procedure, this stored procedure
executes,
but when an error occurs we receive an execute permission denied on
stp_LogError for this user.
When I check the login for this user it is made a user in the database
through the role public.
When I check the role public in the database the user is not a member of
the role public.
I thaught that every user which is granted acces to a database is member
of
the public role, so when i granted execute rights for stp_logerror to the
public role, everyone (except the explicitly denied ones) would have
execute
rights on stp_LogError.
Can someone explain this to me
.
- Follow-Ups:
- Re: SQL 2005 public role
- From: Tom Moreau
- Re: SQL 2005 public role
- Prev by Date: Very strange: Connection under process info not whats in front-end
- Next by Date: Re: SQL 2005 public role
- Previous by thread: Very strange: Connection under process info not whats in front-end
- Next by thread: Re: SQL 2005 public role
- Index(es):
Relevant Pages
|
|
