Anyone have an example of how to trap and exception within a T-SQL
transaction and save diagnostic details on why the transaction failed to
an error log? If you insert the exception data to an error table this
information gets lost when you rollback the transaction. I'm sure I'm
missing something obvious :)
Thanks,
Malcolm


--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
---

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/1536872493.2148567.1507383664.41981...@webmail.messagingengine.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to