I agree with leon, the best method is to have an audit table. But depending on your requirements on detail a shadow audit table might serve you better.
A shadow audit table contains the same fields as your original table with the only difference being for example extra field for "last modified timestamp" and "last modified by" to show who made the change and when. Each time a user updates the record in the original table, you add the new state of the record to the shadow audit table (not replacing - but adding). This way you will have a complete backup of the history of the record from when it was first created.
Only negative here is that your shadow table will be large (depending on the amount of update activity your users do, it could be huge).
Main Topics
Browse All Topics





by: leonstrykerPosted on 2004-05-17 at 12:29:40ID: 11092048
Well there is a transaction log file which is generated on the database and you can place a trigger on the table(s).
But, to tell the truth, I think the easiest method is to it is to setup a Audit table where you will log the user, name of the table modified, the column,the old value, the new value, and posibly the reason for modification.
Leon