Hi,
I am a junior DBA for SQL Server. I have some tables in the production that
want to give update access to group of data management personals, but without
giving them access to update the table directly. If I create an update-stored
procedure, and grant the sp execute write, they cannot execute it without
update permission to the table.
If create a different login to execute this procedure, I still have to give
that login the permission to update, and the users will have update access to
the table.
Is there is work around to this.. ?
I want to prevent the data management personals from running ad-hoc update
queries, that cost us some valuable data. Just want to make it so that they
can only update this through the sp.
Let me know if you know something.
Thank you
Blue Fish
Jens - 11 Oct 2005 18:36 GMT
If they both have the same owner, a technique named ownership chain
applies which means, that if they have access to the stored procedure
and the owner of the store procedure and the underlying table are the
same, they will also have access to the table.
Read more in BOL under Ownership chain.
HTH, jens Suessmeyer.
bluefish - 11 Oct 2005 18:42 GMT
Thank you.
> If they both have the same owner, a technique named ownership chain
> applies which means, that if they have access to the stored procedure
[quoted text clipped - 4 lines]
>
> HTH, jens Suessmeyer.