SQLServerCentral / Discuss Content Posted by Robert Marda / Article Discussions / Article Discussions by Author / Auditing Through Triggers / Latest Posts

RE: Auditing Through Triggers

depafeo — Thu, 22 Jan 2004 07:51:00 GMT

I'm currently building a security administrator app and I have a process where when a user's info is updated, the permissions table is also updated. I send in the UserID that is doing the update into the stored procedure. My question is can the trigger read the "Updated By UserID" param or would I have to have a column in the UserInfo table get updated by the UserID param and then the trigger would get the UserInfo:Updated By UserID column?

Thanks, Lucas

RE: Auditing Through Triggers

bozo7 — Fri, 16 Jan 2004 06:31:00 GMT

The only issue I have with this approach is it makes one assumption. Each user in the organization has a network sign on. Where I currently work (today is my last day) the network admin refuses to give everyone network signons. He knows at some point we have to have auditing of changes and I have told him this is the best approach. But he refuses to do so. Since the application we developed has unique signons for each user we could do something with that but it makes it harder.

Having network signons is usually a good assumption to make but not always.

Ross

RE: Auditing Through Triggers

Robert W Marda — Thu, 24 Jan 2002 15:54:00 GMT

I never had a problem with the identity columns. I think this is because we didn't use them a lot where I used to work (Telos Corporation).Robert Marda

RE: Auditing Through Triggers

ckempste — Mon, 14 Jan 2002 17:15:00 GMT

Hi AndyThanks Andy, also found an article on it and will give it a burl. Ill have to be more thorough in reading up on the new features.CheersChris

RE: Auditing Through Triggers

Andy Warren — Mon, 14 Jan 2002 05:28:00 GMT

With SQL2K Scope_Identity() solves those issues - I agree it was a pain and a MAJOR source of bugs if someone added a trigger that inserted to another table with identity column after the fact. Another option is to use a unique identifier for the audit primary key if you prefer/like a contrived key.On text cols...guess it depends how important it is! I use instead of triggers in some places, in others it is non-critical data and I just don't audit.Andy

RE: Auditing Through Triggers

ckempste — Sun, 13 Jan 2002 20:14:00 GMT

HiOnly problem we had is where programmers with retrieving the identity of the inserted row, but they kept retrieving the audit tables identity column instead, so we had to remove this identity column from the audit table and rely on date/time and user combination (no p-key on the audit table). Have you experienced this before?Also, TEXT columns can not be audited unless you use INSTEAD-OF triggers which is a right pain in the you know what.CheersChris

Auditing Through Triggers

Robert W Marda — Fri, 11 Jan 2002 00:00:00 GMT

Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/rmarda/auditingtriggers.asp