This T-SQL errors and reactions demo follows episode #002 with queries you can run. It shows what a CATCH block can read, how severity is stored, how to log a failure and keep going, and why THROW keeps the original error while RAISERROR replaces it.
Stopping a Trigger From Firing Itself With TRIGGER_NESTLEVEL
A timestamp trigger that updates its own table can loop until SQL Server gives up. Here is the small guard that stops it, with a demo you can run.
Leap Year in SQL Server: SQL in Sixty Seconds #004
To find a leap year in SQL Server, ask EOMONTH for the last day of February. I tested the method against the divisibility rule for every year from 1 to 9999 and found no disagreement. The post also shows an inline function, the errors for invalid years and a one-line TRY_CONVERT test.
Detect a Leap Year in T-SQL: Four Simple Ways
Detecting a Leap Year in T-SQL takes one rule or one date trick. This post tests four ways on SQL Server 2025: the calendar rule, EOMONTH, TRY_CONVERT and DATEDIFF. It shows that all four agree on 209 years, explains the century years that trip people up, and answers how leap years affect date math.
SQL SERVER – Identifying Guest User using Policy Based Management
Can a policy catch a guest user left enabled in user databases? Here is a quick tutorial on identifying guest user access with Policy Based Management.
Declare and Initialize Variables in SQL Server: SQL in Sixty Seconds #003
To declare and initialize variables in one statement, give each variable a type and a starting value in the same DECLARE. The tests here show the NULL default, a loop that does not reset an uninitialized variable, and the one character varchar trap on SQL Server 2025.






