What is the most recent best practice on how transaction auditing should be done for transactional systems using ASP.NET 3.5 and SQL Server 2008?
My requirement is to track changes done by a user and allow them to view the audit trail history in the front-end.
Here’s the different ways I found so far:
- Create triggers and separate table(s). There are 2 options on this approach:
- Create an audit table for each table. This will be exact copy of the table, but will have additional field such as transactionID and datetime fields, etc.
- Create one audit table to keep track of all tables. This will be a more generic table to keep track of changes to the table's data.
- I read about the new auditing feature on SQL Server 2008 (http://msdn.microsoft.com/en-us/library/dd392015%28v=sql.100%29.aspx). Can this be leverage for in ASP.NET? Can I access the file directly and allow users to view it? Or is this really more of a DBA Admin usage?
Thanks for your help in advance!
View Complete Post