Re: Stored Procedure and Table permissions
From: Sue Hoegemeier (Sue_H_at_nomail.please)
Date: 06/03/04
- Next message: newbie: "Re: when to sue sa and when not to"
- Previous message: Robert Mooney: "Stored Procedure and Table permissions"
- In reply to: Robert Mooney: "Stored Procedure and Table permissions"
- Next in thread: Rand Boyd [MSFT]: "RE: Stored Procedure and Table permissions"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 03 Jun 2004 07:08:17 -0600
It will work. Make sure the ownership chains are maintained
- in your example, the table and stored procedure need to
have the same object owner. Then you only need to grant
execute permissions on the stored procedure.
-Sue
On Thu, 3 Jun 2004 05:51:47 -0700, "Robert Mooney"
<anonymous@discussions.microsoft.com> wrote:
>I want to:
>
>1. create a user whose only permissions are to run a
>stored procedure.
>
>2. the stored procedure reads specific data from a table -
> allowing the user read-access to the specific data.
>
>I've created the user and the stored procedure. I've
>given the user EXEC permission for the stored procedure.
>But I find I must give the user SELECT permission to the
>table in order for the stored procedure to work - thus
>exposing the entire contents of the table. I'm executing
>the stored procedure from VBA in Excel.
>
>Is there a way to configure permissions so that the user
>only has EXEC permission to the stored procedure but no
>permissions to the table? In that way I can control what
>information the user sees.
>
>Bob Mooney
- Next message: newbie: "Re: when to sue sa and when not to"
- Previous message: Robert Mooney: "Stored Procedure and Table permissions"
- In reply to: Robert Mooney: "Stored Procedure and Table permissions"
- Next in thread: Rand Boyd [MSFT]: "RE: Stored Procedure and Table permissions"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|