Confysed by the roles

DaI have an application that uses the Extended Stored Procedures sp_OA...
I thought that I read that members of the System Administrators Role could
access the Extended Stored Procedures in the Master Databasewithout
specifically granting execute permissions on each procedure. When the sorce
code executes an error stating that "EXECUTE permission denied on
'sp_OACreate', database 'master', owner 'dbo'
I then granted the user the Execute permissions and had the same error
message
I then Granted the Execute Permissions to Public and it worked
I then removed the permissions from the user and it still worked.
So in the end just adding the Public made this work BUT to reduce my
security risks I would prefer not to give Public the rights to execute the
Extended Stored Procedures.
Can this be done? if so how?Yes, it's possible. It sounds like an issue somewhere with
the login - maybe it's executing under a different login
than the one being granted permissions. You can run a
profiler trace and include login, user info to check this.
-Sue
On Tue, 16 Aug 2005 09:31:09 -0700, "Jim Abel"
<JimAbel@.discussions.microsoft.com> wrote:

>DaI have an application that uses the Extended Stored Procedures sp_OA...
>I thought that I read that members of the System Administrators Role could
>access the Extended Stored Procedures in the Master Databasewithout
>specifically granting execute permissions on each procedure. When the sorc
e
>code executes an error stating that "EXECUTE permission denied on
>'sp_OACreate', database 'master', owner 'dbo'
>I then granted the user the Execute permissions and had the same error
>message
>I then Granted the Execute Permissions to Public and it worked
>I then removed the permissions from the user and it still worked.
>So in the end just adding the Public made this work BUT to reduce my
>security risks I would prefer not to give Public the rights to execute the
>Extended Stored Procedures.
>Can this be done? if so how?