END TRANSACTION
Purpose
Defines the completion of an explicit Teradata session mode transaction, commits the transaction, and drops its Transient Journal.
An explicit Teradata session mode transaction must always start with a BEGIN TRANSACTION statement, and you must always specify both BEGIN TRANSACTION and END TRANSACTION statements to define the limits of an explicit transaction in Teradata session mode.
See “BEGIN TRANSACTION” on page 308 for additional usage information about END TRANSACTION.
Syntax
ANSI Compliance
END TRANSACTION is a Teradata extension to the ANSI SQL:2011 standard.
The statement is valid only in Teradata session mode. If you submit an END TRANSACTION statement in ANSI session mode, Teradata Database aborts the request and returns an error.
For ANSI session mode transaction control statements, see “COMMIT” on page 343 and “ROLLBACK” on page 484.
Required Privileges
None.
BEGIN TRANSACTION/END TRANSACTION Pairs and Explicit Transactions
When you code an explicit transaction in Teradata session mode, you must initiate the transaction with a BEGIN TRANSACTION statement (see “BEGIN TRANSACTION” on page 308) and complete it with an END TRANSACTION statement.
END TRANSACTION and Multistatement Requests
There can be no more than one END TRANSACTION statement specified in a multistatement request, and that statement, if specified, must be the last statement in the request.
Differences Between the Effects of END TRANSACTION and ABORT or ROLLBACK
While an END TRANSACTION request terminates and commits a transaction and drops its Transient Journal, ABORT and ROLLBACK requests terminate a transaction with rollback (see “ABORT” on page 301 and “ROLLBACK” on page 484).
In general, the rules for committing transactions using the COMMIT statement (see “COMMIT” on page 343) also apply to END TRANSACTION.
Rules for END TRANSACTION Using Embedded SQL
The following rules apply to the use of END TRANSACTION in embedded SQL.