Can a User Update a Table That Is Being Merge Replicated?

I would like to know if a user can update a table that is in the
process of being merge-replicated. What will happen to his update?
Some of the tables in our database are replicated between branch
offices using merge-replication. We are currently only do
merge-replication in the evening when no one is using the database.
Now, we may need to replicate more often in order to refresh the data
in a timely manner.
By our database design, the data from each branch office will not
conflict with each other. I say this just in case this has any bearing
to the question that I am asking.
Thanks in advance for any info.
Jay Chan
He/she can update away. If you are not using column level tracking, his/her
update may be overwritten by the publisher's update, or a subscriber with a
higher priority if you are updating a row that is updated on the Publisher
or another subscriber. This overwrite will be logged in a conflict table.
If you are using column level tracking, different columns updated in the
same row will be merged together. The same columns updated will be
overwritten by the publisher's update, or a subscriber with a higher
priority. This overwrite will be logged in a conflict table.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Jay Chan" <jaykchan@.hotmail.com> wrote in message
news:c7e5acb2.0407200753.1d24b1fe@.posting.google.c om...
> I would like to know if a user can update a table that is in the
> process of being merge-replicated. What will happen to his update?
> Some of the tables in our database are replicated between branch
> offices using merge-replication. We are currently only do
> merge-replication in the evening when no one is using the database.
> Now, we may need to replicate more often in order to refresh the data
> in a timely manner.
> By our database design, the data from each branch office will not
> conflict with each other. I say this just in case this has any bearing
> to the question that I am asking.
> Thanks in advance for any info.
> Jay Chan
|||> He/she can update away.
I assume you mean he/she can update the table when the table is right
in the middle of being merge-replicated. This means I can do
merge-replication more often than what I am doing now. Good to know
this. Thanks.

> If you are not using column level tracking, his/her
> update may be overwritten by the publisher's update, or a subscriber with a
> higher priority if you are updating a row that is updated on the Publisher
> or another subscriber. This overwrite will be logged in a conflict table.
> If you are using column level tracking, different columns updated in the
> same row will be merged together. The same columns updated will be
> overwritten by the publisher's update, or a subscriber with a higher
> priority. This overwrite will be logged in a conflict table.
Thanks for the explanation of how column leveling tracking can allow
different columns in the same record to be changed between
merge-replications. I appreciate your help.
Jay Chan