"Nury SWORD" <nurysword@hotmail.com> wrote in message
news:16342dc6.0409141237.7b96b2c3@posting.google.com...
> Hi All,
>
> We know that, "NOT FOR REPLICATION" option makes it possible for
> replication agents ,let's say, to insert rows without being
> constrained by IDENTITY restriction or check constraints. That means,
> being a replication agent is like having a PASS CARD that allows them
> to get rid of constraint checks.
>
> But, during conflict resolution coding, I need to INSERT some data to
> some tables (related tables), but I am facing CONSTRAINTS that merge
> agent does not face.
>
> Is there any way of pretending to be like merge_agent for constraint
> overcoming?
>
> To be more specific, is there any way of setting sessionproperty for
> replication_agent? That is: when you execute the following query in a
> normal connection;
>
> select sessionproperty('replication_agent')
>
> you get "0".
>
> but for replication_agent that function returns "1". Microsoft guys
> somehow set connection property for agent, and how they do it is
> scritly undocumented.
>
> I tried setting context_info in sysprocesses table to "8" but it did
> not work.
>
> Please help, if any way of pretending to be merge agent.
>
> PS:I event wrote an application with ReplMerg.exe process name
> guessing that SQL may know agent from its process name.
>
> Thanks alot in advance,
> Nury SWORD
> Toronto