DDL and DCL Requests, Dictionary Access, and Locks | Teradata Vantage - DDL and DCL Requests, Dictionary Access, and Locks - Analytics Database - Teradata Vantage

SQL Request and Transaction Processing

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
2024-10-04
dita:mapPath
zfm1628111633230.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
evd1472255317510
lifecycle
latest
Product Category
Teradata Vantageā„¢

The execution of a DDL or DCL request causes the data dictionary to be updated and appropriate locks to be placed on system tables while that request is processing.

Optimizing the Locking Granularity for Data Dictionary Access

To improve concurrency, DDL and DCL processing use the finest locking granularity that is practical and delay placing locks as long as possible. Depending on the dictionary table, the system may downgrade rowhash READ lock requests made on the dictionary to ACCESS locks to prevent the query from being blocked by WRITE locks placed on those tables by ongoing DDL operations.

If not blocked, these rowhash READs are not blocked use the standard READ locks.

The following dictionary views and tables are affected by this locking downgrade on a blocked READ lock request:
  • DBC.AccLogRuleTbl
  • DBC.ConstraintNames
  • DBC.Indexes
  • DBC.TableConstraints
  • DBC.TextTbl
  • DBC.TriggersV
  • DBC.TVFields
  • DBC.TVM
  • DBC.UDFInfo
The only SQL statements eligible for a dictionary access READ lock-to-ACCESS lock downgrade upon being otherwise blocked are the following:
  • SELECT
  • HELP COLUMN
  • HELP CONSTRAINT
  • HELP INDEX
  • HELP STATISTICS
  • SHOW FUNCTION/HASH INDEX/JOIN INDEX/MACRO/METHOD/PROCEDURE/TABLE/TRIGGER/TYPE/VIEW

These are system-initiated lock downgrades that you cannot specify using the LOCKING request modifier. See Teradata Vantageā„¢ - SQL Data Manipulation Language, B035-1146.