Skip to content

Update create-trigger-transact-sql.md #10022

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: live
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/t-sql/statements/create-trigger-transact-sql.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down