current transaction

When used, it specifies that this is meant to be a unique savepoint within the scope of the current transaction.

At this point, the row updates aren't permanently written to the database; that doesn't happen until the current transaction is committed.

All data modifications made to that point in the current transaction are rolled back, including any that were made by the trigger.

If the MATCH keyword is omitted, the backup copy of the log will have the same name as the current transaction log for the database.

When instantiated, it could store the current Transaction into a thread-static field.

This prevents other transactions from modifying any rows that have been read by the current transaction.

Log roll works by periodically closing the current transaction log file and creating the next generation.

Or, if the optional svpt1 identifier is not used, rollback happens to the last savepoint specified in the current transaction.

These locks are held until the end of the current transaction for both cursors and independent SELECT statements.

Notice that there is no code in this example to enlist the JDBC connections in the current transaction -- the container does this for us.

The current transaction of the victim is rolled back and deadlock error message 1205 is returned to the client.

Fair value is an asset's purchase or sale price in a current transaction between willing parties.

If the current transaction is in an uncommittable state, the transaction is rolled back before executing uspLogError.

No other transactions can modify data that has been read by the current transaction until the current transaction completes.

Other transactions can insert new rows that match the search conditions of statements issued by the current transaction.

The Accountant would prefer to avoid such surprises in future, so he raises the isolation level of his current transaction to level 3.

After SET XACT_ABORT ON is executed, any run-time statement error causes an automatic rollback of the current transaction.

The table lock prevents conflicting DDL operations that would override data changes in a current transaction.

However, the updates are generally visible within the current transaction.

For withdrawals, we enter the current transaction as a negative number so the balance gets smaller.

when true , the pooler automatically enlists the connection in the creation threads current transaction context.

However, we can also rollback the current transaction, resetting the state of our database to the last commit point.

This will indicate not to commit the current transaction after the activity completes.

These locking hints override the current transaction isolation level for the session.

Any existing previous logs are deleted, while transactions in the current transaction log file are marked as obsolete.

New transactions eventually overwrite the obsolete entries in the current transaction log before a new log file is created.

Previous log files reside in the same directories as the current transaction log file.

When this occurs, any uncommitted changes to the database are lost and the current transaction is rolled back.

Locks associated with the current transaction are released when the transaction commits or rolls back.

Amazingly, resources accessed by remote object B will still be enlisted in the current transaction.

The lock will be held until the end of the current transaction.

This tells the server to commit the current transaction after this activity completes.

If asked, the context votes to abort the current transaction, and the object is deactivated on method return.

Locks placed on a resource are associated with either the current transaction or the current session.

The following example releases the lock associated with the current transaction on the resource Form1 in the AdventureWorks database.

True if the current transaction is marked for rollback, false otherwise.

That represents the current transaction context.

Gets the description of the current transaction.

ESE uses reserved transaction log files only to complete a current transaction process.

A previous statement has caused query notifications to fire under the current transaction.

A description of the current transaction.

Token that describes the current transaction.

An object that represents the current transaction.

That describes the current transaction.

One common option is to specify that the information is used only for the current transaction, for example in the case of a Web order.

Mark the current transaction for rollback.

Stores objects in the current transaction.

Name of the current transaction code.

Specifies whether SQL Server automatically rolls back the current transaction when a Transact-SQL statement raises a run-time error.

The EventSubClass column indicates if a new transaction will be started after the current transaction is committed.

In SQL Server 2005, only cursors that are opened within the current transaction are closed at transaction commit time.

That is a copy of the current transaction object.

The current transaction based with extra top-ups has to change.

The Database Engine skips past the rows or pages instead of blocking the current transaction until the locks are released.

Method, you can create a named or unnamed savepoint within the current transaction, and the method will return a

It also attempts to escalate all locks held by the current transaction on

Cancels any changes in the current transaction and ends the transaction