Enterprise Transaction Services—Summary

CSharp-Online.NET:Articles

.NET Articles

Enterprise Transaction Services Transaction Overview Programmatic Transactions Automatic Transactions Transactions Without Components ASP.NET Transactions Support Transaction Isolation Monitoring the DTC .NET 2.0 Transactions Summary

© 2005 Pearson Education, Inc.

Summary

This chapter covered the transaction features offered by Enterprise Services. Instead of doing transactions programmatically, you can task transactions automatically by applying the attribute [Transaction] to specify transactional requirements. The transactional options Required, RequiresNew, Supported, NotSupported, and Disabled influence the Enterprise Services interception code so that a new transaction is created, an existing transaction is used, or no transaction is used at all.

The automatic transactions make use of the distributed transaction coordinator, so transactions can also flow across multiple systems.

This chapter also discussed the problems with concurrency and consistency with transaction isolation levels. Changing the isolation level can increase concurrency, whereas consistency is reduced, and vice versa.

Windows Server 2003 also offers the new feature named services without components; transactions are part of this service.

---

¹ The connection string defines whether a connection should be enlisted with the transaction context of the thread. With the .NET data provider for SQL Server, you can define whether the transaction should be enlisted with the Enlist parameter. The Enlist parameter has a default value of true, so that the connection is enlisted with the transaction context. Microsoft .NET data provider for Oracle has the same Enlist parameter.