NBSteve,

I'm not exactly sure what you were referring too was a misconception, but my intent

wasn't to explain all the nuances of transaction commits and rollbacks.

I'm familiar with people trying to use savepoints and the like and using variables is

one approach and I've heard of several other approachs people have suggested to

handle the error logging issue where transactions are concerned.

However, my experience has been that using the CLR stored proc. approach is simple, extensible and really, for me at least, has made the transaction issue a non issue.

Transactions can be invoked outside the stored procedure, such as with a C# application or an SSIS package. This is what I meant when I said 'you can run stored procs from many different processes'. Still, the CLR approach has made the transaction issue for logging irrelavent.

Steve