跟踪事务升级到 DTC 的原因 [英] Trace why a transaction is escalated to DTC

问题描述

有什么方法可以准确地确定 System.Transaction TrasactionScope 被升级到 DTC 的原因?我们的一个组件遇到了问题，其中一个组件似乎会升级事务，而所有其他组件(看似看似相似)却不会升级.

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.

是否提供有关升级原因的任何信息，以及如何找到和观察这些原因?SQL探查器?日志文件?还是我在这方面不走运?

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?

更新:我正在运行 SQL Server 2005 以获取信息

UPDATE: I'm running against SQL Server 2005 for info

推荐答案

您可以尝试关闭 Distributed Transaction Cordinator 服务并将其启动类型设置为禁用.这会在事务被提升时引发异常，调用堆栈中会有问题代码.

You could try shutting down the Distributed Transaction Cordinator service and setting its startup type to disabled. This will cause an exception when the transaction is promoted that will have the problem code in the call stack.

当然，如果您在需要此服务的机器上运行其他项目，这将无济于事，但在调试机器上是可能的.

Of course this won't help if you have other items running on the machine that require this service, but would be possible on a debug machine.

这篇关于跟踪事务升级到 DTC 的原因的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！