replication triggers

Hi all:
Cannot insert duplicate key row in object 'MSmerge_tombstone' with unique
index 'uc1MSmerge_tombstone'.
The statement has been terminated.
that is the error i got when i try to delet a record from table which has
merge replication on.
i had a check that this error actually is from the trigger generated by
replication..
so any helps will be appreciated.
Thanks
Nick
"nick" schrieb:
> Hi all:
> Cannot insert duplicate key row in object 'MSmerge_tombstone' with unique
> index 'uc1MSmerge_tombstone'.
> The statement has been terminated.
> that is the error i got when i try to delet a record from table which has
> merge replication on.
> i had a check that this error actually is from the trigger generated by
> replication..
> so any helps will be appreciated.
> Thanks
> Nick
Run the merge agent and try again ...

Replication object changes

Does replication allow object changes? I read that in SQL server 2000 it will
update new columns on the Publisher and push them to the subscriber, but does
that mean if create a new stored proc on the publisher it will push that as
well to the subscriber? Thanks!
Anita,
for a new stored proc, you could add it to an existing publication, snapshot
and distribute, or create a new publication. A new Stored Proc won't be
picked up automatically. Also, sp_addscriptexec can be used to propagate to
all subscribersif you just want to get it there. Remember that changes to
the stored proc tsql are not picked up and propagated - we need sql 2005 for
this.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks Paul!
"Paul Ibison" wrote:

> Anita,
> for a new stored proc, you could add it to an existing publication, snapshot
> and distribute, or create a new publication. A new Stored Proc won't be
> picked up automatically. Also, sp_addscriptexec can be used to propagate to
> all subscribersif you just want to get it there. Remember that changes to
> the stored proc tsql are not picked up and propagated - we need sql 2005 for
> this.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>