From ca4c7373314255a0d71b45fd9a48d0bc2d661059 Mon Sep 17 00:00:00 2001 From: Steve Jones Date: Fri, 21 Feb 2025 12:40:17 -0700 Subject: [PATCH] Update create-trigger-transact-sql.md Removed batches, as I'm not sure DNR applies there. If I'm wrong, please let me know and I can amend. This also does apply to functions. Tagging @rabryst for visibility. --- docs/t-sql/statements/create-trigger-transact-sql.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/t-sql/statements/create-trigger-transact-sql.md b/docs/t-sql/statements/create-trigger-transact-sql.md index 1cfd219c462..0bd42fafc6a 100644 --- a/docs/t-sql/statements/create-trigger-transact-sql.md +++ b/docs/t-sql/statements/create-trigger-transact-sql.md @@ -405,7 +405,7 @@ To disable nested triggers, set the nested triggers option of sp_configure to 0 The first AFTER trigger nested inside an INSTEAD OF trigger fires even if the **nested triggers** server configuration option is 0. But, under this setting, the later AFTER triggers don't fire. Review your applications for nested triggers to determine if the applications follow your business rules when the **nested triggers** server configuration option is set to 0. If not, make the appropriate modifications. ### Deferred Name Resolution -[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] allows for [!INCLUDE[tsql](../../includes/tsql-md.md)] stored procedures, triggers, and batches to refer to tables that don't exist at compile time. This ability is called deferred name resolution. +[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] allows for [!INCLUDE[tsql](../../includes/tsql-md.md)] stored procedures, triggers, and functions to refer to tables that don't exist at compile time. This ability is called deferred name resolution. ## Permissions To create a DML trigger, it requires ALTER permission on the table or view on which the trigger is being created.