Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage News The Curious Nature of Transactions in ADO.NET and LINQ

The Curious Nature of Transactions in ADO.NET and LINQ

Transactions in LINQ rely on TransactionScope, a .NET 2.0 class that uses a distinctly non-OO design pattern that relies on gloabls.

TransactionScope is used to implicitly attach a transaction to a set of changes. Unlike the Transaction object in ADO.NET, TransactionScope is not limited to a single database connection. One of the most common use cases is running a transaction across multiple servers.

When a TransactionScope object is created, it automatically registers itself as the transaction for the thread. All transaction aware operations will automatically use this transaction, with no need to pass the transaction object to the object. Examples of transaction aware objects include the SqlCommand class and LINQ to SQL objects.

One serious side effect of this design is that the link between transactions and operations are not explicit.

Public Sub OperationWithTransaction() 
Using t As New Transactions.TransactionScope
End Using
End Sub

In the above example, when OperationWithTransaction is called everything in the Operation1 function is associated with the transaction. This happens even though the transaction is not explicitly passed to the method. This can make debugging Operation1 problematic, especially when the transaction scope is created several layers up the stack trace.

A final note, when using multi-threading, a given TransactionScope only applies to the current thread.

Rate this Article