SqlConnection.EnlistDistributedTransaction(ITransaction) Method
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Enlists in the specified transaction as a distributed transaction.
public:
void EnlistDistributedTransaction(System::EnterpriseServices::ITransaction ^ transaction);public void EnlistDistributedTransaction (System.EnterpriseServices.ITransaction transaction);member this.EnlistDistributedTransaction : System.EnterpriseServices.ITransaction -> unitPublic Sub EnlistDistributedTransaction (transaction As ITransaction)Parameters
- transaction
- ITransaction
A reference to an existing ITransaction in which to enlist.
Remarks
You can use the EnlistTransaction method to enlist in a distributed transaction. Because it enlists a connection in a Transaction instance, EnlistTransaction takes advantage of functionality available in the System.Transactions namespace for managing distributed transactions, making it preferable to EnlistDistributedTransaction for this purpose. For more information, see Distributed Transactions.
You can continue to enlist in an existing distributed transaction using the EnlistDistributedTransaction method if auto-enlistment is disabled. Enlisting in an existing distributed transaction makes sure that, if the transaction is committed or rolled back, modifications made by the code at the data source are also committed or rolled back.
EnlistDistributedTransaction returns an exception if the SqlConnection has already started a transaction using BeginTransaction. However, if the transaction is a local transaction started at the data source (for example, by explicitly executing the BEGIN TRANSACTION statement using an SqlCommand object), EnlistDistributedTransaction rolls back the local transaction and enlists in the existing distributed transaction as requested. You do not receive notice that the local transaction was rolled back, and are responsible for managing any local transactions not started using BeginTransaction.