Why is TransactionScope using a distributed transaction when I am only using LinqToSql and Ado.Net

Question

We are having problems on one machine, with the error message:

\"MSDTC on server XXX is unavailable.\"

The code is using a T

Answer 1

This almost always happens when your transaction uses more than one database connection. So, let's say you are updating two tables. You might update the first table using one connection but update the second table using a different second connection. This will cause the transaction to be escalated to MSDTC, even using a TransactionScope object.

The way we got around this is when performing transactions, we use a single database context object for all our writes. This eliminated the escalation. Since doing this, we've never had the MSDTC message appear.

Randy