Statement:INSERT INTO is as useful as a chocolate teapot. Regardless of the type of compliance activity in place for meeting your obligations, you can’t just set it and forget it like a countertop kitchen appliance.
Īnd that's great! But if I turn it into a stored procedure with parameters, I get : Audit event: event_time: 14:07:29.3099731 This makes it much easier to audit your compliance program, and brings more defensibility to how well you are truly meeting your compliance obligations. Shop Eat Sleep Audit Repeat Funny Activity And Hobby Lovers Sarcasm Quote Auding Gift auditing t-shirts designed by sunnymood as well as other auditing merchandise at TeePublic. If I run an INSERT statement, I get a 33205 event contain this : Audit event: event_time: 14:06:53.4855165 I've got basic auditing working, writing to the security log. Is it possible to audit the changed values using SQL Server Auditing for stored procedures? Note: I'm not talking about CDC.