FIX: Secondary SPIDs Enlisted in DTC Transaction do not Obtain DTC Isolation Level

Article translations Article translations
Article ID: 243664 - View products that this article applies to.
This article was previously published under Q243664
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 56633 (SQLBUG_70)
Expand all | Collapse all


SQL Server provides distributed transaction capabilities through the Distributed Transaction Coordinator (DTC). When you establish a DTC transaction (ITransactionDispenser::BeginTransaction), the isolation level is specified.

The first SQL Server connection to enlist in the specified DTC transaction obtains and maintains the isolation level. However, subsequent connections, which enlist in the transaction, retain their current isolation level and do not obtain the DTC isolation level.


Immediately after enlisting in the DTC transaction, perform an explicit set operation to establish a matching isolation level for the connection and DTC transaction scope.


Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.


Article ID: 243664 - Last Review: October 22, 2013 - Revision: 2.0
  • Microsoft SQL Server 7.0 Standard Edition
kbnosurvey kbarchive kbbug kbfix KB243664

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from