Dropping or Deleting Database Objects That Contain Triggers - Advanced SQL Engine - Teradata Database

SQL Data Definition Language Detailed Topics

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
June 2020
Language
English (United States)
Last Update
2021-01-24
dita:mapPath
jpx1556733107962.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1184
lifecycle
previous
Product Category
Teradata Vantage™

Teradata Database 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.