This feature requires the use of .NET Enterprise Services, which manages the distributed transactions.
The COM+ services infrastructure can be accessed from managed and unmanaged code. Services in unmanaged code are known as COM+ services. In .NET, these services are referred to as Enterprise Services. Working with transactions in Enterprise Services using ADO.NET is very straightforward.
To program using Enterprise Services
Derive the components from System.EntrepriseService.ServicedComponent.
Specify the custom attributes (such as Transaction, AutoComplete, and others) to specify the requested services and their options. For a complete list of the attributes, refer to the Enterprise Services documentation.
The Timeout Option in the .NET
Transaction attribute has to be explicitly set to -1 or
a very high number. .NET documentation states that the ADO.NET transaction
timeout default is 0, which means it will never time
out. However, this actually causes an immediate transaction timeout, which
rolls back the entire transaction.
Sign and build the assembly.
Register the assembly.
The following are the connection properties used in conjunction with Distributed Transaction support.
Distributed Transaction Protocol (DistributedTransactionProtocol) – To specify the protocol used to support the distributed transaction, XA Interface standard, or MS DTC OLE Native protocol, by setting up the property DistributedTransactionProtocol=OLE native protocol in the connection string. The default protocol is XA.
Tightly Coupled Transaction (TightlyCoupledTransaction) – When you have a distributed transaction using two resource managers that point to the same ASE server, you have a situation called a "Tightly Coupled Transaction." Under these conditions, if you do not set this property to 1, the Distributed Transaction will fail.
To summarize, if you open two database connections to the same ASE server and enlist these connections in the same distributed transaction, you must set TightlyCoupledTransaction=1.
Enlist – The AseConnection object automatically enlists in an existing distributed transaction if it determines that a transaction is active. Automatic transaction enlistment occurs when the connection is opened or retrieved from the connection pool. You can disable this auto-enlistment by specifying Enlist=0 as a connection string parameter for an AseConnection.
If auto-enlistment is disabled, you can enlist in an existing distributed transaction by calling the EnlistDistributedTransaction method on the AseConnection with a passed-in ITransaction parameter that is a reference to an existing transaction. After calling the EnlistDistributedTransaction, all updates made using this instance of AseConnection will be made as part of this global transaction. As a result, it will be committed or rolled back when the global transaction is committed or rolled back.
The AseConnection object must be
open before calling EnlistDistributedTransaction.
You can use EnlistDistributedTransaction when you pool business objects. If a business object is pooled with an open connection, automatic transaction enlistment occurs only when that connection is opened or pulled from the connection pool. If multiple transactions are performed using the pooled business object, the open connection for that object will not automatically enlist newly initiated transactions. In this instance, you can disable automatic transaction enlistment for the AseConnection and then enlist the AseConnection in transactions using EnlistDistributedTransaction.
WARNING! EnlistDistributedTransaction returns an exception if the AseConnection has already begun a transaction either by using BeginTransaction or by executing the BEGIN TRANSACTION statement explicitly with an AseCommand.
