Help · section 7 of 44
Triggers
Mirrors the in-app Help. The live copy in your console and `dlake guide help` are always current.
User triggers on your tables (AFTER/INSTEAD OF, insert/update/delete). Bodies are validated against a blocklist (no DDL, EXEC, xp_*, cross-schema escapes). System triggers — audit triggers (tr_<table>_Insert/Update/Delete), platform feature triggers (tr_<table>_dl_*: AuditStamp, AuditFreeze, OptimisticConcurrency, BlockDirectDelete, Event), and change-log triggers (trg_cl_*) — are badged System and protected from non-admin modification; their name shapes are reserved.
Creating, replacing or re-enabling a trigger on a table breaks that table’s Data API writes until you Restart DAB — see Triggers and the Data API. Dropping or disabling one does not.
