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,768 reads
From bloated error logs to risky logon triggers, a guide to auditing connections without killing performance.
2026-07-29
2,768 reads
2024-02-21
483 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,203 reads
2019-08-29
645 reads
2019-08-22
836 reads
2016-10-28
925 reads
2010-07-30
2,798 reads
2010-07-23
2,653 reads
This month’s blogging party is hosted by Jeff Ianucci – his challenge is to...
As for me, I'll keep writing whenever time permits. I don't expect every post...
By Steve Jones
This is an interesting invitation this month. Jeff Ianucci is a new host, and...
Comments posted to this topic are about the item Pay for Performance, which is...
Comments posted to this topic are about the item Switching Schemas I
Comments posted to this topic are about the item Enforcing Unique Customer Emails When...
I run this query:
SELECT s.name AS schemaname , o.name AS objectname FROM sys.objects o INNER JOIN sys.schemas s ON s.schema_id = o.schema_id WHERE o.name = 'Beer'I get one row back for an object named dbo.beer. There is an ETL schema and both of these are nonpartitioned tables. I run this code:
ALTER TABLE dbo.beer switch TO etl.beerWhat happens? See possible answers