|
|
Posted by Ots on 05/11/07 20:54
On May 3, 1:50 pm, --CELKO-- <jcelko...@earthlink.net> 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.
My goodness! Maybe I should explain a little... this is a
configuration database for a large
industrial process. The database itself is backed up every night, so
the machinery / process can
always be restored to a known working state. The purpose of my audit
table, which is indeed
stored in the same database, is so that when the process begins
behaving differently, folks can
go back and see that, during a previous shift, an operator tweaked (or
fat fingered) an operational
value.
I suppose the audit table could indeed provide a "reason for
termination" someday, but hopefully
not mine...
Navigation:
[Reply to this message]
|