Thank you all for your responses. From the links sent by Carl Federl (part II), I believe it is possible to make the trigger not abort the transaction by issuing a RaiseError statement. Is there a way to somehow ensure that a RaiseError statement is executed and that the transaction of the calling statement is not aborted. It seems like the RaiseError can only be called when we do are doing some condition checking (like, Business rules) and we manually code to raise the error. But, when an error happens for reasons beyond our control, there is no way to ensure that the trigger does not abort the transaction. I am beginning that a trigger should never be used anywhere since there is no way to capture the error and handle it gracefully within the trigger.