Re: protocol of db-changes

Stefan Poschenrieder <stefanp_at_raysono.com> wrote in message news:<3BC40972.1D5B9D5C_at_raysono.com>...
> Hi there,
>
> we are asked to make a protocol of EVERY (!!) change in database like
> this:
>
> table column old-value new-value
>
> whats the easiest way to solve this "problem"..
>
> many thanks...
> Stefan

1 Ask how long this history has to be maintained 2 Tell them keeping any change older than one month is useless as the offender in the meantime will have forgotten why on earth he or she changed that record
3 Get permission to buy more disk storage 4 Get permission to add an extra cpu
5 Develop triggers on *every individual* table to track the changes for you
6 Ideally the history table should have the same structure as the table it tracks, the structure proposed just above has *too many* drawbacks (I was forced to use it on a sie)

And no, with respect to 5: there is no other way, and any change in the table definition will also result in changing the trigger.

Hth,

Sybrand Bakker
Senior Oracle DBA Received on Wed Oct 10 2001 - 08:18:12 CDT