You add a method that executes an INSERT command to write state information to a database.

You put the write code in a TransactionScope using block. You must ensure that if this method throws an exception within the context of an outer, ambient transaction, it does not affect the completion status of the ambient transaction. Your solution should use the fewest system resources.

What should you do?

Setting TransactionScopeOption to Suppress is useful when you want to preserve the operations performed by the code section and do not want to abort the ambient transaction if the operations fail. For example, you can do this when you want to perform logging or audit operations, or when you want to publish events to subscribers, whether or not your ambient transaction commits or aborts.

Removing the TransactionScope using block does not make the code fail to participate in an ambient transaction if there is one present.