Hi William, In a single stored procedure this will indeed allow you to have a trace of the exception, in real world you often have nested stored procedures, triggers called within the transaction-scope, and all log-records to assist you in trying to analyse the problem/flow are gone too once you've rolled back (but I realize i'm now mixing logging in general and Exception logging).

But your solution is already much better than having no logging at all, and imho also much better that having to fall back to external logfiles. It would be nice to have a statement/keyword to enable you to do DML beyond the scope of the current transaction, however dangerous that may sound 🙂