local transaction

A transaction considered to be a local transaction when it is a single - phase transaction and is handled by the database directly .

With this option set on, a remote stored procedure call causes a local transaction to be promoted to a distributed transaction.

The propagation is considered to be a push model where the local transaction is pushed to the destination.

When ON, a Transact-SQL distributed transaction is started when a remote stored procedure is executed from a local transaction.

When REMOTE_PROC_TRANSACTIONS is OFF, remote stored procedure calls are not made part of a local transaction.

When OFF, calling remote stored procedures from a local transaction does not start a Transact-SQL distributed transaction.

The instance manages the distributed transaction internally; to the user, it operates as a local transaction.

The resource adapter provides access to a remote IBM Cloudscape database with local transaction support.

Depending on the scope of the implementation, a JCA adapter can support no transaction, local transaction, or XA transaction.

The resource adapter provides access to a remote Derby database with local transaction support.

Messages can be retrieved from a local transaction queue with or without using a transaction.

The security demand affects the code that initiated the escalation, not necessarily the code that originally created the local transaction.

You can perform these updates within the scope of a single local transaction.

The work done by the remote procedure is not rolled back if the local transaction is rolled back.

At the application, a distributed transaction is managed much the same as a local transaction.

Local (Default): Component will execute in the context of a local transaction.

Calls to remote stored procedures execute outside the scope of a local transaction if REMOTE_PROC_TRANSACTIONS is set to OFF.

The current implementation of Encina Connector only supports a local transaction management contract.

If a global transaction is not present, the component will execute in the context of a local transaction.

Otherwise, the runtime environment will establish a local transaction environment.

The resource adaptor provides access to an embedded Derby database with local transaction support.

The resource adaptor provides access to a Microsoft SQL 2000 server database with local transaction support.

The following example performs a local transaction that consists of two separate statements in the try block.

The following example performs a local transaction consisting of two separate statements in the.

BEGIN TRANSACTION starts a local transaction for the connection issuing the statement.

Encina notifies the J2EE application server of the local transaction-related events; namely, begin, commit, and rollback.

False (default): Component will execute in the context of the existing global transaction (if present) or a local transaction.

Rolls back the local transaction and enlists in the existing distributed transaction as requested.

The model for controlling a distributed transaction in OLE DB is similar to controlling a local transaction.

Notice the absence of the resource local transaction calls because the transactionality is now container-managed.

Method to start the local transaction and get a transaction object.

What is the difference between a local transaction and an XA transaction on the Application Server level?

If an activity session is not present, the component will execute in the context of the existing unit of work scope or a local transaction.

The implication of only local transaction support is that only a flat transaction model (one-phase commit) is supported.

It provides an extended unit-of-work scope beyond the method boundary for local transaction based resource managers.

You cannot mix local transaction with XA transactions in WebSphere.

An LTC boundary is different from the Resource Manager Local Transaction (RMLT), which is a resource's view of a local transaction.

The local transaction joins an activity session if one is active.

Can I mix local transaction and XA transaction in WebSphere?

A local transaction is a unit of work between a WebSphere connection and the resource manager.

The local transaction has aborted.

However, a non-transactional message can be sent or received from a local transaction queue without explicitly using transactional

Public Service, Factors Fluxion and Factor's Spatial Distribution: Balance Analysis of Local Transaction Costs