|
|
Posted by Ed Murphy on 05/03/07 20:28
--CELKO-- wrote:
>>> I have an Audit trigger that logs changes to tables. I want to apply this trigger to many different tables. It's the same trigger, with the exception of the table name. <<
>
> Go tell the lawyers and the accountants that the audit data is being
> kept in the same schema as the data being audited. They will want to
> put that in the "reason for termination" in your personnel file.
>
> Get a third party audit tool that will run outside the schema and trap
> things as they cross the system boundary. This data should then be
> sent to physically separate data store, so that if (read: WHEN) the
> database is trashed or crashes, you can still reconstruct the audit
> trail. Do you keep your backup on the same hard drive as the
> database? No! Of course not! This is the same thing.
This depends on how strict the audit needs to be, and particularly
whether you need to retain audit data for activity that was subsequently
lost due to reverting to a backup. And what are you supposed to do if
(read: when) the audit database is trashed or crashes?
Navigation:
[Reply to this message]
|