Please help.

Dear Friends
I am facing a strange problem. I am using the merge
replication from two offices for my database and the
current changes are showing perfectly on both the end but
for last two days change the database if diffrent some
information is in the Site one database which is updated
locally and some information is in site two which was
updated locally at site two.
Please suggest how the same data will be refelected in
both the database.
Your earlier reply would be a great help.
Best regard
Sharad
Sharad,
not sure I follow you completely, but it seems what you are talking about is
conflict resolution, where two computers involved in merge replication
change the same data before synchronizing. By default the publisher will win
conflicts with the subscriber, and if you have more than one subscriber the
first one to synchronize takes on the priority of the publisher. If such a
conflict has occurred then you can see it in the system conflict tables -
"conflict_..." and "....conflicts" or in the related graphical interface -
conflict viewer (right-click on the publication and select view
conflicts).There are more advanced setups involving priority numbers,
conflict resolution routines and custom resolvers - details in BOL.
HTH,
Paul Ibison
|||Dear Pual
Thanks for your reply. but it is not a conflict as i do
not see anything in the option of view conflict but the
data in the two database is diffrent. to give you clear
idea.
I have a table Sales which is having fields one two three
and four
The one and two is feeded and updated by Server1
The Three and four is updated by Server2
Now in both the server i can see that the updation done
by the local user is showing in respective server but not
in the replicated server like the infromation of one and
two is not there in the server2
I hope i have put the query right now.
Please help
Best regards
Sharad

>--Original Message--
>Sharad,
>not sure I follow you completely, but it seems what you
are talking about is
>conflict resolution, where two computers involved in
merge replication
>change the same data before synchronizing. By default
the publisher will win
>conflicts with the subscriber, and if you have more than
one subscriber the
>first one to synchronize takes on the priority of the
publisher. If such a
>conflict has occurred then you can see it in the system
conflict tables -
>"conflict_..." and "....conflicts" or in the related
graphical interface -
>conflict viewer (right-click on the publication and
select view
>conflicts).There are more advanced setups involving
priority numbers,
>conflict resolution routines and custom resolvers -
details in BOL.
>HTH,
>Paul Ibison
>
>.
>