Monday February 8th

Friday February 5th

0 Kicks

Creating a generic CLR audit trigger

There’s an interesting article at SqlJunkies about how to create a generic CLR audit trigger. But there is just one small problem with this trigger code. The PerformedBy column of the Audit table in the sample code is set to the UserID of the connection string which in most applications would be the same UserID for all connections because of connection pooling. This means the trigger will log all operations performed by the application but it will not log the real user (application user) who made the change.


Commenting on Stories is limited for now and will open up to those recommended by the community. Learn how
Loading DotNetKicks...
brought to you by the Kicks Network