NGWS SDK Documentation  

This is preliminary documentation and subject to change.
To comment on this topic, please send us email at ngwssdk@microsoft.com. Thanks!

Manual Transactions

Transaction-based applications have been available for years. Early TP applications were extremely specialized programs that required a developer to have an in-depth knowledge operating systems and business logic. These systems were expensive, reliable, and costly to modify.

Since those early days, TP programming has become less specialized and more widespread. ADO, OLE DB, ODBC, and MSMQ resource APIs enable manual transaction processing, which is one of two transaction models available to NGWS developers.

A manual transaction allows the developer to explicitly begin a transaction boundary, control each connection and resource enlistment within the boundary, determine the outcome of the transaction (commit or abort), and end the transaction. Although this model offers measured control over a transaction, it lacks some of the ease built into the automatic transaction model. For example, there is no automatic enlistment and coordination between data stores in a manual transaction. Further, transactions do not flow from object to object, as is the case in automatic transactions.

If you choose to control a distributed transaction manually, you must manage recovery, concurrency, security, and integrity. In other words, you must apply all the programming technique necessary to maintain the ACID properties associated with transaction processing.

The following topics describe NGWS runtime support for the manual transaction model:

See Also

Automatic Transactions

ACID Properties