16.10 - Aborting SQL Requests - Teradata Database

Teradata Database SQL Fundamentals

Product
Teradata Database
Release Number
16.10
Published
June 2017
Language
English (United States)
Last Update
2018-04-25
dita:mapPath
klx1480972732157.ditamap
dita:ditavalPath
changebar_rev_16_10_exclude_audience_ie.ditaval

If an error is found in a request, that request is aborted. Normally, the entire transaction is not aborted. However, some failures will abort the entire transaction.

A single statement or multistatement 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 abort 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 character. It is 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 or when it is entered through BTEQ.