May 3, 2011 at 10:08 am
:w00t:
I have a user account that has certain select and update access to a limited number of tables, however, in testing we discovered that the user fires a trigger that updates a completely different table and succeeds. We then tried a deny on that udpated table and the trigger still fires and updates the table. How do I stop this behavior?
Urgent help is needed as we are deploying this into production Thursday evening!
May 3, 2011 at 10:20 am
Are you executing ad-hoc SQL or executing a stored procedure that they have EXECUTE permission on?
May 3, 2011 at 10:22 am
adhoc
May 3, 2011 at 10:35 am
I believe it's to do with ownership chaining - there was a similar thread here:
http://www.sqlservercentral.com/Forums/Topic694107-146-1.aspx#bm694237
May 3, 2011 at 10:43 am
HowardW THANKS MUCH!
It makes complete sense.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply