Home > Articles > Programming > Windows Programming

Enterprise Services with the .NET Framework: Transaction Services

Transaction services are usually the main reason why Enterprise Services is used. This chapter opens with an overview of transactions, examines how you can task transactions programmatically, and finally turns to how you can use Enterprise Services transactions, and how you can access the new features offered with Windows Server 2003.
This chapter is from the book

Transaction services are usually the main reason why Enterprise Services is used. So that you do not have to deal with transactions programmatically, Enterprise Services offers a way to use transactions by using attributes.

This chapter opens with an overview of transactions, and then examines how you can task transactions programmatically. With this knowledge, you will see the advantages of transaction services offered by .NET Enterprise Services. The focus of this chapter then turns to how you can use Enterprise Services transactions, and how you can access the new features offered with Windows Server 2003.

Specifically, this chapter covers the following topics:

  • Transaction overview

  • Programmatic transactions

  • Automatic transactions

  • Transactions with services without components

  • Transaction isolation levels

Transaction Overview

So that you can fully understand the transaction support offered by Enterprise Services, it is important for you to have an overall understanding of transactions.

Let’s start with an example of a course database and attendees registered for courses. If an attendee who is registered for the Programming ADO.NET course wants to change to the Introduction to .NET course because he does not have the necessary prerequisites for attending the first course, he will be removed from the attendee list of the first course, and added to the attendee list of the second one. If one of these operations fails, the other should not happen either. Here a single transaction is needed. Transactions ensure that data-oriented resources are not permanently updated unless all operations complete successfully.

A transaction is defined by a unit of operations that either all succeed or all fail. If all operations complete successfully inside a transaction, the transaction is committed, and the updated data is written permanently. If one operation fails, however, a rollback is done; as a result, the data exists as it was before the transaction started.

ACID Properties

Transactions can be defined by four basic properties, easily remembered with the acronym ACID (atomicity, consistency, isolation, durability).


Atomicity ensures that either all updates occur or none at all. Because of the atomicity guaranteed by transactions, you do not have to write code to handle the situation where one update was successful, and another was not.

With the course example just mentioned, if removing the attendee from the first course succeeds, but adding him to the second course fails, the transaction is aborted, and the attendee is not removed from the first course.


Consistency means that the result of a transaction leaves the system in a consistent state. Before the transaction was started, the data is in a valid state, as it is after the transaction is finished.

Consistency can be described with the same scenario as discussed with atomicity, to move an attendee from one course to the other. If removing the attendee from the first course fails, but adding him to the second course succeeds, the attendee would be registered for two courses at the same time. This is not a valid scenario; the database would not be consistent. The consistency property says that the transaction must leave the database in a consistent state; so if one part of the transaction fails, all other parts must be undone.


Multiple users can access the same database simultaneously. With isolation, it is assured that it is not possible outside of a transaction to see data that is being changed inside a transaction before the transaction is committed. It is not possible to access some in-between state that might never happen if the transaction is aborted.

If you do a query to get the list of attendees for all courses, while at the same time a transaction is running to move an attendee from one course to another, the attendee will not be listed on both courses. Isolation guarantees that an interim state of the transaction from outside of the transaction cannot be seen.


Durability means that a consistent state is guaranteed even in case of a system crash. If the database system crashes, it must be guaranteed that transactions that have been committed are really written to the database.

Distributed Transactions

Enterprise Services supports distributed transactions, where a transaction can cross multiple database systems. These database systems can also be from different vendors.

With distributed transaction resource managers, a transaction manager and a two-phase commit protocol are needed.

Resource managers, as is obvious from the term itself, manage resources. Examples of resources are databases, message queues, or simple files. SQL Server is a resource manager, as is the Oracle database, and the Message Queue server. Resource managers must support the two-phase commit protocol.

The two-phase commit consists of a prepare phase and a commit phase. When updating data, a prepare phase occurs first, during which all participants in the transaction must agree to complete the operations successfully. If one of the participants aborts the transaction, a rollback occurs with all other participants. Agreeing to the prepare phase, the database must also guarantee that the transaction can commit after a system crash. If all participants of a single transaction had a successful prepare phase, the commit phase is started, during which all data is permanently stored in the databases.

A distributed transaction must be coordinated by a transaction manager. For Enterprise Services, the distributed transaction coordinator (DTC) is such a transaction manager. The DTC is a transaction manager that supports the X/Open XA Specification for Distributed Transaction, and the OLE Transactions protocol. The X/Open XA protocol is not used natively by the DTC; it must be converted to OLE Transactions by the ODBC driver or OLE DB provider. The X/Open XA Specification is not only supported by Microsoft SQL Server, but also by Oracle. The DTC is a Windows service that is part of the Windows operating system.

The distributed transaction coordinator manages transactions to multiple databases and connections from multiple clients. To coordinate work from different systems in a single transaction, the DTCs of different systems communicate with each other. Connections to resource managers that should participate in a distributed transaction must be enlisted with the DTC. To enlist database connections, the ADO.NET data providers for SQL Server and OLE DB are aware of the DTC, and the connections are enlisted automatically if transactional attributes are used with serviced components.1

Figure 7-1 shows a single transaction that is running across multiple systems. Here the transaction is started from component A that is running on server A. Component A has a connection to the database on server C. The connection is enlisted with the DTC on the local system (in this case, the DTC of server A). Component A invokes a method in component B that itself requires a transaction. Component B has a connection to the database on server D. The database connection is enlisted in the DTC of server B. On the database systems C and D, we also have DTCs running that manage the transactional interaction with the resource managers of the dependent systems. Because all four DTCs coordinate the transaction, anyone participating in the transaction can abort it. For example, if the resource manager of server D cannot complete the prepare phase successfully, it will abort the transaction. The DTC of server D will tell all other DTCs participating in the transaction to do a rollback with the transaction. On the other hand, if all members of the transaction are happy with the prepare phase, the DTCs coordinate to commit the transaction.

Figure 7.1

Figure 7-1 Transactions with the distributed transaction coordinator.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020