Vantage Transaction Handling Protocol - Teradata VantageCloud Lake

Lake - Working with SQL

Deployment
VantageCloud
Edition
Lake
Product
Teradata VantageCloud Lake
Release Number
Published
February 2025
ft:locale
en-US
ft:lastEdition
2025-11-21
dita:mapPath
jbe1714339405530.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
jbe1714339405530

Vantage manages transactions to maintain valid, consistent, and available data for all users. A transaction may consist of one or more requests which are sent one at time and processed as each is received. Locks are applied as needed for each request. Locks are placed on its associated database objects according to the types of statements contained in the request.

If a statement does not complete successfully or causes processing to time out because of a statement error, deadlock, privilege violation, table constraint violation, or premature logoff, the system performs the following transaction management steps.

  1. The entire transaction is aborted. Abort processing performs the following actions.
    1. Performs an implicit END TRANSACTION.
    2. Backs out any changes made to the database by the transaction.
    3. Releases any usage locks associated with the transaction.
    4. Discards any partially accumulated results (spools) generated by the transaction.
  2. A failure or time-out response is returned to the requestor.

Most statement errors resulting from multiple-statement INSERT statements end the entire transaction.

Statement independence is a method of handling multiple-statement INSERT errors by only rolling back the individual statements that failed, not the entire transaction. See Multiple-Statement and Iterated INSERT Requests.

The client software you are using must support statement independence to prevent all multiple-statement requests and iterated INSERT statements in a transaction or multiple-statement request from being rolled back. See the documentation for your client software for information on support for statement independence.