>> I'm not so sure about a timestamp column on every table. I'd certainly say most tables should have one (especially if the data is user entered - in that case then userID is a requirement also IMHO). Some reference tables just don't have that need IMO.
>>
>>Many organizations have rules/regulations that require timestamps on every table.
>>
>>You never know when it can help, even on the smallest of tables. A while back someone with admin rights modified a row (manually) in Management Studio, in a config table with about a dozen entries. Someone noticed that the spelling on a report for a discount promotion name was wrong. (About a year prior, I had convinced the DBA to put a trigger on every table to update the LastUser and LastUpdateDate.)
>>
>>So obviously we could see whodunnit it and when.
>
>How? Seeing who made the most recent modification to a row wouldn't tell you who made the change you were interested in...
>

Good point, you may want to have complete auditing history.