>>Yes, that was stated in the last paragraph in my original post (what I quoted above). This is a new Transaction (TransactionScopeOptions.RequiresNew) ... therefore, I assumed that it would not be dragged into the ambient distributed transactions. Is this a valid assumption?
>>
>>~~Bonnie
>
>From the point of SQL Server, if one transaction is started and not yet committed, everything that starts in the middle of it will be part of that transaction. I am not sure how distributed transactions work in .NET, but I assume this would hold true also.

After further testing, I discovered that the TransactionScopeOption.RequiresNew means that the new Transaction doesn't get enlisted in the existing Distributed Transactions, so I'm good to go now. I hoped that was the case and I'm glad I was right.

~~Bonnie