Working on the distributed database management system; we are familiar with using the SqlTransaction. The purpose of using Transaction is to get your SqlTransaction info / status from the front end and much more important is to add the rollback functionality to call, so that you can perform a smooth transaction on your client-server application module.
As I discussed earlier, we are familiar with SqlTransaction (.NET framework 2.0)... We will not discuss about using of SqlTransaction… .NET provides us with the
System.Transaction assembly where you will find the
System.Transactions.TransactionScope class. Using of
TransactionScope() is much easier rather than the SqlTransaction such as ease of managing your transaction, need to write couple of code to manage, calling
Commit, etc. A sample code snippet is given below:
TransactionOptions txOptions = new TransactionOptions();
using (TransactionScope txScope =
new TransactionScope(TransactionScopeOption.Required, txOptions))
catch (SqlException sqlError)
Be careful when using this. If you are not careful to perform all steps of the transaction on the same connection, the transaction is treated as a distributed (multi database) transaction and incurs a rather steep performance penalty. Examine the Microsoft Enterprise Model application blocks to see how they managed this.