Linq To Sql Audit Trail / Audit Log: Should I Use Triggers Or Doddleaudit?

I'm working on a business app that requires that ALL database transactions be audited (for legal purposes mainly). I've looked around the web and came across DoddleAudit (http://ww

Solution 1:

If the audit is for legal purposes then you have to do it through a certified for compliance methodology. Such methodologyes are very specific to the specific threats being mitigated via audit. You need to read up on Auditing (Database Engine) and more than likely consult a specialist that can give you guidance on the various legal frameworks that surround data audit, specific to your location and domain.

SQL Server has the C2 compliant audit mode, see c2 audit mode Option, which is a certified compliant mode. Linq2sql audit or custom data audit may be brilliant feats of engineering, but they're not gonna hold a drop of water if they are not certified for compliance (and they're not).

Solution 2:

If you are using SQL Server 2008 (the question didn't specify), have you looked at the support added in that version?

http://msdn.microsoft.com/en-us/library/dd392015.aspx