Menu
Is there any way to determine precisely why a System.Transaction TrasactionScope is being escalated to the DTC? We are hitting a bump with one of our components that seem to escalate the transaction while all other components (which seem deceptively similar) does not do escalation.
Are any information made available on the reasons for the escalation and how can they be found and observed? SQL Profiler? Log files? Or am I out of luck on this one?
UPDATE: I'm running against SQL Server 2005 for info
655
Transaction management escalation describes the process of migrating a transaction from one of the transaction manager's components to another. System. Transactions includes a transaction manager component that coordinates a transaction involving at most, a single durable resource or multiple volatile resources.
Direct to consumer is exactly what it is, selling directly to end customers. The strategy behind this approach is that it bypasses wholesalers and retailers, thus cutting out unnecessary costs associated with having intermediaries between manufacturers and the consumer.
The Microsoft Distributed Transaction Coordinator (MSDTC) service is a component of modern versions of Microsoft Windows that is responsible for coordinating transactions that span multiple resource managers, such as databases, message queues, and file systems.
When using TransactionScope a transaction is escalated whenever application opens a second connection (even to the same database) within the Transaction Scope in question.
182
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
