>David suggested this code
>
>

>sqlConnection.EnlistTransaction(Transaction.Current);

>
>which worked after I introduced a new property and disabled check for uncommitted transactions (when this new property is set to true) and explicit committing of them which we were doing in each SQL call.

Ah ... I didn't think of that. With the normal use of TransactionScope (wrapping all database access, which eliminates the need for SqlTransaction use totally), that wouldn't be necessary because the TransactionScopeOption.Required automatically enlists the transaction in any existing current transaction. Sometimes you don't want to do that, however, and the way to prevent automatic enlistment is to use the TransactionScopeOption.RequiresNew ... then the scope will be "self-contained" (for lack of a better word).

~~Bonnie