This relates to the Nested Database transactions in C#.

The objects in collection I wish to consume transaction implement their very own transactions using SqlConnection.BeginTransaction method.

After reading through this post I don't know basically can mix individuals too or otherwise. I'm using SQL Server 2005 and every object uses connection particulars from static configuration class.

Does anybody have knowledge about this ?

This is actually the sample code:

using(TransactionScope scope = new TransactionScope())
  for (int i=0; i<=1000....) 
    SqlConnection con = new SqlConnection()
    SqlCommand cmd = new SqlCommand("delete from ...", con); 

    try {
       DbTransaction t = con.BeginTransaction();
       cmd.CommandText = .... ;
       t.Commit  ...
    catch {
       t.Rollback ...


After investing hrs to configure MSDTC to operate on machines, I finally got to the stage where I possibly could test the code.

It seems to operate (with 1 database)

The above mentioned problem might be helpfull to individuals that do not have the source code so can't eliminate "legacy" transactional system or maybe transactional areas of the code aren't localized or, as with my situation, you won't want to mess an excessive amount of using the complex code that's shown to be stable being produced atmosphere but you have to introduce nested transactions...

Tell me for those who have different experience.