<echcom@gmail.com> wrote in message
news:1127186175.042590.208830@g44g2000cwa.googlegroups.com...
> My Scenario:
> I have two database for Merging Replicate: "db_AAA" (publisher) and
> "db_BBB" (subscriber).
> Both "db_AAA" and "db_BBB" contain a "tbl_KKK" table. "tbl_KKK" are the
> same structure in both "db_AAA" and "db_BBB" but not the same records
> number.
> So, when I update a record in "db_AAA" that not existed in "db_BBB" -->
> Conflict ocurred, and the resolver deleted it out from "db_AAA". :(
>
> My Question:
> How to prevent resolver to delete record in Publisher or Subscriber
> when conflicts occur? That mean, when I edit record in "db_AAA" or
> "db_BBB" and conflicts occurr --> I want the conflict record in
> "db_AAA" (or "db_BBB") not be deleted.
>
> Anybody help me?
>

> have a look at the @compensate_for_errors parameter on sp_addmergearticle
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> <echcom@gmail.com> wrote in message
> news:1127186175.042590.208830@g44g2000cwa.googlegroups.com...
> > My Scenario:
> > I have two database for Merging Replicate: "db_AAA" (publisher) and
> > "db_BBB" (subscriber).
> > Both "db_AAA" and "db_BBB" contain a "tbl_KKK" table. "tbl_KKK" are the
> > same structure in both "db_AAA" and "db_BBB" but not the same records
> > number.
> > So, when I update a record in "db_AAA" that not existed in "db_BBB" -->
> > Conflict ocurred, and the resolver deleted it out from "db_AAA". :(
> >
> > My Question:
> > How to prevent resolver to delete record in Publisher or Subscriber
> > when conflicts occur? That mean, when I edit record in "db_AAA" or
> > "db_BBB" and conflicts occurr --> I want the conflict record in
> > "db_AAA" (or "db_BBB") not be deleted.
> >
> > Anybody help me?
> >