Dropping or Deleting Database Objects That Contain Triggers - 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™

Vantage imposes restrictions on DROP and DELETE operations on the following database objects to ensure that triggers are not orphaned, as indicated by the following table:

IF you specify this statement … IN this state … THE result is …
DROP TABLE triggers are defined on the specified table an error message.

You must first drop all the triggers before the table can be dropped.

  • DELETE DATABASE
  • DELETE USER
at least one table in the named database or user is the subject table of triggers created in a different database an error message.

You must first drop all such triggers before the database or user can be deleted.