>-----Original Message-----
>Thanks for the reply. The merge agent seemed to have
>caught all of the transactions the last time I ran the
>snapshot so I wasn't sure if that was the norm or not.
>Thanks again.
>
>>-----Original Message-----
>>My understanding is that before the snapshot is done a
>row
>>tracking column is added to the table. This row
tracking
>>column will write updates to some metadata tables -
>>msmerge_contents, etc. Then the snapshot is done or the
>>tables you are replicating through merge replication,
and
>>the snapshot is also done of the msmerge_contents tables
>>and other tables. So if a transaction is added to a
>table
>>which is being replicated, it is "caught" in the
>>msmerge_contents table and will be applied if not during
>>the intial application of the underlying tables, but
then
>>in the application of the msmerge_contents table on the
>>subscriber.
>>
>>It does appear that a window does exist where
>transactions
>>could be missed, but while trying to repro this I have
>>been able to do it.
>>
>>>-----Original Message-----
>>>Hi everyone,
>>>I'm currently running merge replication between two
sql2k
>>>(sp3) and win2k(sp4) servers. My question is with the
>>>snapshot. Other than the snapshot agent blocking users
>>>while it bulk-copies the data out, will the merge agent
>>>continue to replicate transcations that come through
>>>during the snapshot process? Thanks.
>>>
>>>Leon
>>>.
>>>
>>.
>>
>.