You add a method that updates tables with two update commands. These commands execute within a TransactionScope using block to ensure that these commands either both complete or both fail. You want to ensure that the completion status of these commands does not affect any transactions started before the method was called.

What should you do?

If the scope is instantiated with RequiresNew, it is always the root scope. It starts a new transaction, and its transaction becomes the new ambient transaction inside the scope.

If the scope is instantiated with Required and an ambient transaction is present, the scope joins that transaction. This is not the desired behavior.

If the scope is instantiated with Suppress, it never takes part in a transaction, whether or not an ambient transaction is present. This negates the desired transaction behavior within the method.