Why is a nested transaction committed even if TransactionScope.Complete() is never called?

First off, there is no such thing as a nested transaction in SQL Server This is important.

First off, there is no such thing as a nested transaction in SQL Server. This is important. Second, both TransactionScopes use conn1 so you are (at the SQL Server level) incrementing @@TRANCOUNT for each BEGIN TRANSACTION Simple explanation: the inner transaction is committed when the outer transaction commits because rolling back the inner would rollback both transactions That is, COMMIT TRANSACTION (implied by .

Complete and . Dispose) decrements @@TRANCOUNT while ROLLBACK TRANSACTION (implied by . Dispose only) takes it back to zero.So the inner rollback is suppressed because of "no such thing as nested transactions" If you'd used conn2 correctly in the inner 'scope it would work as expected because the 2 transactions are unrelated at the database server level.

Which is where it matters...

Your second Command object is being created on conn1, not conn2, so it's very much like the other question - the connection on which you're running the command was opened before the second transaction scope was opened.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.