>Good thought for a redesign when this gets moved to a new backend - some sort of generalized audit table for all the key tables. If you did this, did you have one audit table per table to be tracked or did you have an overall audit table that had a field to indicate the table being tracked?
>
Wasn't done by me, but FWIW, the latter. Then when we need to move the database for demoing somewhere, just zap that one table and the overall size of the database drops to about 45% :).