What about using an INSTEADOF trigger. Within it you can query the sysprocess table looking for a flag in the context_info section. You can use SET CONTEXT_INFO to put a value in there.

As another thought, if there are situations where the behavior needs to be circumvented, maybe a trigger is the wrong tool.

-Mike


>Hi,
>
>is there a way to do a update command without firing the update trigger for a session?
>
>we can't use the "alter table table1 disable trigger UpdTrig1" because it will affect all session.
>
>
>I was thinking of using the not for replication option of the trigger.
>Is there a way to "fool" the trigger to believe that i'm in a replication update?
>
>Alain