Aborting SQL Requests | SQL Fundamentals | VantageCloud Lake - Aborting SQL Requests - Teradata Vantage

Teradata® VantageCloud Lake

Deployment
VantageCloud
Edition
Lake
Product
Teradata Vantage
Published
January 2023
Language
English (United States)
Last Update
2024-04-03
dita:mapPath
phg1621910019905.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
phg1621910019905

If an error is found in a request, that request ends, but typically, the entire transaction does not end.

A single statement or multiple-statement request that does not include the BEGIN TRANSACTION and END TRANSACTION statements is treated as an implicit transaction. If an error is found in any statement in this type of request, then the entire transaction is aborted.

Abort Processing

Following are the steps for ending processing:
  1. Back out any changes made to the database as a result of any preceding statements in the transaction.
  2. Delete any associated spooled output.
  3. Release any associated locks.
  4. Bypass any remaining statements in the transaction.

Completed Requests

A request is considered to have completed when either an End of Text character or the request terminator is encountered. The request terminator is a semicolon (;) as the last nonpad character on an input line.

A request terminator is optional except when the request is embedded in an SQL macro or trigger when entered through BTEQ.