Question : capturing transaction rollbacks using SQL Server 2008 Audit

SQL Server 2008 Audit allows tracking of specific events and logging them to an audit (file or Application log). It allows tracking of any INSERT, UPDATE or DELETE statement issued against a database for which I define a Database Audit Specification. The events will be logged regardless of whether the DML statements were issued inside of a transaction. How can I tell that a specific DML SQL statement that appears in the Audit log has not been rolled back?

Answer : capturing transaction rollbacks using SQL Server 2008 Audit

That surprises me but I guess there is some rationale that I am just not thinking of. Yeah you could use trace to track rollbacks but that could get complicated.

You might look at Change Data Capture (again depending on how you are using this) or look at a tool like Apex SQL Log (or really any SQL Log reader, I haven't used one in awhile. I believe Quest makes one as well, at least they did have one for SQL 2000. Lumigent also makes tools for auditing changes. Sentrigo is another vendor.