A reader used HOST_NAME() in a logon trigger to limit access. Here is why that is risky, and why Logon Triggers can lock everyone out if you are not careful.
SQL SERVER – Nested Triggers – Trigger Calling Another Trigger Error
A reader asked what happens when one trigger calls another. Here is a simple example with two AFTER INSERT triggers that shows how nested triggers behave.
Triggers That Assume One Row: Fixing Them for Multi-Row Updates
Fix triggers for multi-row updates by joining inserted and deleted, testing complete audit coverage, and keeping transaction work small.
Oracle to SQL SERVER Migration – Triggers Used While Migration
Moving from Oracle to SQL Server is like switching phones: old habits come along. A client tuning case about the triggers used during the migration.
SQL SERVER – How to Avoid Triggers for Multiple Row Operations in a Table
A late-night mail from an old customer about an application error led to this lesson: how to avoid triggers causing trouble with multiple row operations.
SQL SERVER – How to Enable or Disable All the Triggers on a Table and Database?
One line commands to enable or disable all the triggers on a table, a database or the whole server using ENABLE TRIGGER ALL and DISABLE TRIGGER ALL.
Who Changed This Row? Auditing Data Changes
Auditing data changes requires choosing whether you need old values, new values, actor identity, or a change feed, then testing the cost.