The “Successful Login” Dilemma: Why Your Login Auditing Strategy Might Be Hurting Your Server
From bloated error logs to risky logon triggers, a guide to auditing connections without killing performance.
2026-07-29
2,628 reads
From bloated error logs to risky logon triggers, a guide to auditing connections without killing performance.
2026-07-29
2,628 reads
2024-02-21
471 reads
This trigger will work even if you don't have the primary key on any table. Mechanism to configure the primary key in config table has been provided. This can be very helpful to solve the system audit requirements without much efforts.
Disclaimer : Audit Log trigger has performance overhead. It’s meant for table which is not frequently updated, deleted or inserted. Please take precaution when creating the trigger on the table having too many columns.
2019-10-15 (first published: 2019-10-10)
3,190 reads
2019-08-29
639 reads
2019-08-22
828 reads
2016-10-28
920 reads
2010-07-30
2,792 reads
2010-07-23
2,647 reads
By Steve Jones
This is timely, as I’m currently on a boat in the Adriatic taking a...
You can find the slides and SQL scripts for my session “Spice up your...
By SQLPals
How to Clear the SSMS Cache (SSMS 21 and Later) Updated...
Comments posted to this topic are about the item Risk Vs Reward, The never...
Hi, I have a trigger, that works fine elsewhere but is not working at...
In Azure SQL Database Hyperscale Edition, how many geo-replicas can be created?
See possible answers