Trigger updating inserting
However, you can define views on views where each view has its own INSTEAD OF trigger.
Triggers can be created directly from Transact-SQL statements or from methods of assemblies that are created in the Microsoft .
NET Framework common language runtime (CLR) and uploaded to an instance of SQL Server.
This option is required for triggers on memory-optimized tables.
For more information, see EXECUTE AS Clause (Transact-SQL).
INSTEAD OF cannot be specified for DDL or logon triggers.
At most, one INSTEAD OF trigger per INSERT, UPDATE, or DELETE statement can be defined on a table or view.This option is required for triggers on memory-optimized tables and is not supported for triggers on traditional tables.FOR | AFTER AFTER specifies that the DML trigger is fired only when all operations specified in the triggering SQL statement have executed successfully.These events primarily correspond to Transact-SQL CREATE, ALTER, and DROP statements, and certain system stored procedures that perform DDL-like operations.Logon triggers fire in response to the LOGON event that is raised when a user's session is being established.Using WITH ENCRYPTION prevents the trigger from being published as part of SQL Server replication.WITH ENCRYPTION cannot be specified for CLR triggers.NATIVE_COMPILATION Indicates that the trigger is natively compiled.SCHEMABINDING Ensures that tables that are referenced by a trigger cannot be dropped or altered.Specifying the fully qualified name of the table or view is optional.A view can be referenced only by an INSTEAD OF trigger.