Locks and Concurrency - Analytics Database - Teradata Vantage

SQL Data Definition Language Detailed Topics

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-07-11
dita:mapPath
vuk1628111288877.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
B035-1184
lifecycle
latest
Product Category
Teradata Vantage™

When you do not specify the SPOOL, TEMPORARY, or PERM options, MODIFY USER places an ACCESS lock on the database being altered to run concurrently with all DML requests.

Specifying the SPOOL, TEMPORARY, and PERM options require an EXCLUSIVE lock.

This statement also places a rowhash WRITE lock on the database for DBC.DBase. The SPOOL, TEMPORARY, and PERM options then place a second lock on the immediate parent for DBC.DBase. For PERM, the second lock is a rowhash-level WRITE lock. For SPOOL or TEMPORARY, the second lock is a rowhash-level READ lock.

The SPOOL, TEMPORARY, and PERM options also place a rowhash-level WRITE lock on DBC.DataBaseSpace. The PERM option then places a second rowhash-level WRITE lock on the immediate parent for DBC.DataBaseSpace.