Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

An Auditing Slution with XML And XSL Expand / Collapse
Author
Message
Posted Thursday, August 9, 2007 12:13 PM
SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Today @ 1:55 AM
Points: 648, Visits: 1,873
Comments posted here are about the content posted at http://www.sqlservercentral.com/columnists/dmckinney/3179.asp
Post #389416
Posted Friday, December 11, 2009 8:22 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, December 14, 2009 10:16 AM
Points: 20, Visits: 3
That is nice and robust solution! But since triggers can be disabled by privileged users, this won't work for internal access violation...
Post #832978
Posted Friday, December 11, 2009 9:34 AM
SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Today @ 1:55 AM
Points: 648, Visits: 1,873
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.
Post #833034
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse