A way to check who made a change to item

No, there's no audit trail for property changes.

We are looking in to setting up our own database triggers to log changes to the item table into our own audit table. Tests seem to work okay, and we even wrote an active report to allow reports of the changes within HQ Manager. However we're a bit nervous about adding triggers to 'package software' databases. Also, we have't yet figured out how to capture the 'HQ Manager' User - which is kind of essential in an audit log!.

Any thoughts on risks of setting up our own triggers or capturing the HQ User in the trigger would be appreciated.

Thanks

Dave

"Glenn Adams [MVP - Retail Mgmt]" wrote:

Trigger Dangers: Triggers have overhead. Make sure you test before adding triggers to a production database to ensure that you don't negatively impact perfomance. RMS 'touches' it's tables pretty frequently, and an UPDATE trigger is going to get called a lot. Again, you may see performance problems... In the event that a future upgrade to RMS alters a table where you have added a custom trigger, you can bet that your trigger will get blown away in the upgrade. Not that big a deal - just keep the create script around...

Getting the HQ User: HQ is not open to customization in the way the Store Operations is. I don't believe there is a way to capture the user, especially if you are trying to do it from the trigger; however, you set up unique SQL users, and set up each persons workstation to connect using their own credentials rather than a common SQL username. You CAN Get the SQL username for the current user (I think is @@USER, but Check Books Online), however, in the case of a Trigger, this may end up being the user who created the trigger, or the table owner...

Glenn Adams Tiber Creek C> We are looking in to setting up our own database triggers to log changes to

Thanks Glenn.

I had come to the conclusion that the SQL user was the only way we could identify people. Of course setting a PC up to be multi-user and have user specific SQL log-in is a bit tricky.... but we have it sorted.

Cheers,

Dave

"Glenn Adams [MVP - Retail Mgmt]" wrote: