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,727 reads
From bloated error logs to risky logon triggers, a guide to auditing connections without killing performance.
2026-07-29
2,727 reads
2024-02-21
480 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,199 reads
2019-08-29
643 reads
2019-08-22
836 reads
2016-10-28
924 reads
2010-07-30
2,797 reads
2010-07-23
2,652 reads
By Brian Kelley
During COVID, I attended training on software/enterprise architecture given by Mark Richards. One of...
For me, the objective is straightforward: have a backup strategy that is reliable, understandable,...
By DesertDBA
Note: This post is the invitation for T-SQL Tuesday #204 on November 3rd, 2026....
Comments posted to this topic are about the item The ##MS_DatabaseConnector## User
Comments posted to this topic are about the item Planning for Change
Comments posted to this topic are about the item Importing Excel files into SQL...
On SQL Server 2025, I run this code as a sysadmin:
CREATE LOGIN Demo WITH PASSWORD = 'Demo1234567' GO ALTER SERVER ROLE ##MS_DatabaseConnector## ADD MEMBER Demo GOI then login as Demo and run this:
USE sandbox go SELECT CURRENT_USERWhat is returned? See possible answers