"maxzsim via SQLMonster.com" <u14644@uwe> wrote in message
news:60f37c24dfe8c@uwe...
> Hi All ,
>
>
> I read from BOL abt this NOT FOR REPLICATION is uses primarily for
> identity
> values.
>
> I have the following situation
>
> I am creating a trigger that actually updates/insert records into tblA in
> DB_A but this tblA is involved in replication to tblA in DB_B so should
> the
> "NOT FOR REPLICATION" be used in the trigger ?
>
> appreciate ur advice
>
> tks & rdgs
>
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-replication/200605/1

Hilary Cotter wrote:
>Yes, it should be used if
>
>1) the table the trigger is writing to is not published.
>2) you need the trigger to be enforced on the subscriber for DML originating
>on the Subscriber from non-replication processes
>
>> Hi All ,
>>
>[quoted text clipped - 12 lines]
>>
>> tks & rdgs