January 23, 2007 at 8:42 am
What's your opinion on requiring certain attributes in tables such as CreateDate, CreateUser, ModifyDate, ModifyUser? I know there are situations where this does not make sense such as fairly static lookup tables, however there are also times where it would be nice to track who created or changed a record and when the change occurred. Just curious how you approach this issue with your designs?
Thanks, Dave
January 23, 2007 at 9:23 am
Using a trigger to update those fields works great, and at the same time why don't you write the inserts/updates/deletes to an audit table tracking the old and new values. This allows you to report the whole trail of when the record was inserted and what/who/when has made changes to the record .... your auditors will love you!
-BLM
January 23, 2007 at 9:35 am
At my last job we took the audit table approach to comply with Sarbanes-Oxley, but fortunately my current employer is not subject to SOX. I would still consider audit tables, but probably only for our critical data. My thought in this environment is to create defaults so the date and user are automatically applied to the record, but I agree audit tables would make an auditor happier.
Thanks, Dave
January 25, 2007 at 8:19 am
Space not being much of an issue these days, create and last modified user / date is something I require on every table. Why not have it? Someone will ask at some point.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply