A computer transaction which requires the successful completion of multiple events on multiple systems before it can be completed. For example, when transferring money from a savings account to a checking account, the transaction involves both a debit and a credit. It is imperative that both parts of the transfer occur: (1) the withdrawing of funds from the savings account, and (2) the deposit into the checking account. All steps in the process must succeed, otherwise no steps are allowed to succeed. A distributed transaction processing monitor ensures completeness of a complex distributed transaction.
A transaction that spans multiple resource manager instances. It starts with an XA-compliant xa_begin, and ends with an XA-compliant xa_commit, xa_rollback, or xa_end.
a combination of two or more related transactions that execute in a coordinated manner
a database transaction that must be synchronized among multiple participating databases which are distributed among different physical locations
a series of database changes that affect two or more databases residing on two or more machines
a single transaction that applies to multiple, heterogeneous databases that may reside on separate server machines
a transaction across multiple data sources (Oracle, SQL Server, SAP)
a transaction in which the transactional unit of work spans across multiple nodes in a network
a transaction that includes one or more statements that, individually or as a group, update data on two or more distinct nodes of a distributed database
a transaction that involves more than one connection
a transaction that may span multiple resources
a transaction that modifies tables on more than one database and then expects all the changes to be committed
If a transaction is started on a specific system and all requests to other remote objects maintain and propagate that transaction, the environment is said to support distributed transactions.
A single transaction that can apply to multiple heterogeneous database s that may reside on separate server
A single transaction that can apply to multiple heterogeneous databases that may reside on separate servers.
A distributed transaction is an operations bundle, in which two or more network hosts are involved. Usually, hosts provide transactional resources, while the transaction manager is responsible for creating and managing global transaction that encompasses all operations against such resources. Distributed transactions, as any other transactions, must have all four ACID properties, where atomicity guarantees all-or-nothing outcomes for the unit of work (operations bundle).