August 9, 2007 at 12:13 pm
Comments posted here are about the content posted at http://www.sqlservercentral.com/columnists/dmckinney/3179.asp
December 11, 2009 at 8:22 am
That is nice and robust solution! But since triggers can be disabled by privileged users, this won't work for internal access violation...
December 11, 2009 at 9:34 am
I understand your point, but I would suggest that you could say the same about the data in the target audit tables. i.e. a privileged user would be able to delete / update data.
Whatever solution you use for auditing, you'll have to ensure that appropriate permissions are granted to make sure that the neither the auditing mechanism nor the audited data itself is tampered with.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy