When Explicit Locking Is Necessary - Teradata Database

SQL Data Manipulation Language

Product
Teradata Database
Release Number
15.10
Language
English (United States)
Last Update
2018-10-06
dita:id
B035-1146
lifecycle
previous
Product Category
Teradata® Database

When Explicit Locking Is Necessary

The system automatically places locks on database objects each time an SQL request is performed. Therefore, the use of the LOCKING modifier is seldom necessary. Explicit user‑specified locks are only useful when you need to override the automatic locking specified by the Optimizer and placed by the Lock Manager. Overriding the default may be necessary to prevent deadlock if subsequent requests in the transaction require a higher level lock for an object.