Re: Performance hit with trigger program

<Alan>
Use a named activation group for best performance and assuming all this
program is going to do is write to data queue.
</Alan>

... more important than performance is correctness and this approach (named Activationgroup and asynchronous work for a trigger making writes/updates to other tables) is not transaction safe.

<Dan>
Oh, and for those who will inevitably ask, I was told that we cannot turn
on journaling. This is my second week here, and I don't have enough clout
to delve into the why
</Dan)

There is never ever a valid reason not turning on journal!!!

D*B