Triggers come in two kinds, Instead of and After. Here is how an Instead of Trigger can intercept an insert, update or delete on a table, with an example.
CONTEXT_INFO: Passing a Value Through a Session
CONTEXT_INFO lets you attach a small value to a session and read it anywhere in that session, even inside a trigger. This post tests SET CONTEXT_INFO on SQL Server 2025, uses it to log who changed a price, and compares it with SESSION_CONTEXT.
Audit Columns From Day One: CreatedAt, UpdatedAt and Who Changed It
Add audit columns with UTC timestamps and trusted change identities, maintain updates in procedures, and know when history is needed.
Types of Triggers Quiz: Which Trigger Can Fire on a View?
This Types of Triggers Quiz asks which trigger you can put on a view that joins two tables. The answer is INSTEAD OF INSERT. A tested script shows the error an AFTER trigger gives and how the working trigger splits one insert into two tables.
WITH CHECK OPTION in SQL Server: Stop Rows Leaving a View
WITH CHECK OPTION stops a change made through a view from pushing a row out of that view. This post builds a view of large invoices, shows an update and an insert that make rows vanish, adds the option to block both with Msg 550, and compares it with a trigger. Every result comes from SQL Server 2025.
Summary Tables: Keeping Pre-Aggregated Totals Current
Keep summary tables current with changed-day rebuilds, handle late arrivals and deletes, and reconcile stored totals against detail.
MERGE Statement Pitfalls
MERGE statement pitfalls include duplicate source keys, concurrency races, trigger surprises, and complex actions that deserve testing.