Merge replication question

We are using merge replication with 600 users over a nationwide wan/lan
network. For the most part it works, but occasionally some changes will not
be merged to the agent. All changes make it to the server, but when users
sync the changes do not come down to them. Someitmes if they do multiple
syncs in succession they will make it but other times not. We do a snapshot
of the database nightly that is used by new users to get the initial
database. We have noticed on one user where they installed the snapshot but
did not immediately sync afterwards (we instruct them to so so that they
will get any changes since the snapsot was created). They sync'ed the next
day after a new snapshot was created.. Changes in the database from the
snapshot downloaded one day to the creation of the new sanpshot will not
sync to the database. Changes after the second snapsot is created will
sync. It appears the the client DB thinks it has the records and does not
need to get them. Any thoughts?
Can you run validation on a couple of your subscribers and let us know the
results? Are you using filtering or does each subscriber receive the same
set of data? What build of SQL Server are your subscribers and publishers
on?
Philip Vaughn
This posting is provided "AS IS" with no warranties, and confers no rights.
"Fast Eddie" <e@.bellsouth.net> wrote in message
news:VjA_d.35353$6g7.31842@.bignews1.bellsouth.net. ..
> We are using merge replication with 600 users over a nationwide wan/lan
> network. For the most part it works, but occasionally some changes will
> not be merged to the agent. All changes make it to the server, but when
> users sync the changes do not come down to them. Someitmes if they do
> multiple syncs in succession they will make it but other times not. We do
> a snapshot of the database nightly that is used by new users to get the
> initial database. We have noticed on one user where they installed the
> snapshot but did not immediately sync afterwards (we instruct them to so
> so that they will get any changes since the snapsot was created). They
> sync'ed the next day after a new snapshot was created.. Changes in the
> database from the snapshot downloaded one day to the creation of the new
> sanpshot will not sync to the database. Changes after the second snapsot
> is created will sync. It appears the the client DB thinks it has the
> records and does not need to get them. Any thoughts?
>
|||There is no filtering, all users get all data. We are using SQLServer 2000.
We confirmed today that the issue is the data lost between the creation of
the snapshots. When a new snapshot is created, data that is the new
snapshot but not in the snapshot downloaded will not syncronize if a sync
was not performed immediately after the snapshot is loaded. Any settings
that would cause this behavior?
lip Vaughn" <philipv@.microsoft.com> wrote in message
news:OSAMikALFHA.3552@.TK2MSFTNGP12.phx.gbl...
> Can you run validation on a couple of your subscribers and let us know the
> results? Are you using filtering or does each subscriber receive the same
> set of data? What build of SQL Server are your subscribers and publishers
> on?
> Philip Vaughn
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Fast Eddie" <e@.bellsouth.net> wrote in message
> news:VjA_d.35353$6g7.31842@.bignews1.bellsouth.net. ..
>
|||Can you respond back with the version of your publisher and subscriber(s)?
Philip Vaughn
This posting is provided "as is" with no warranties and confers no rights.
"Fast Eddie" <e@.bellsouth.net> wrote in message
news:X5K_d.38774$c72.11001@.bignews3.bellsouth.net. ..
> There is no filtering, all users get all data. We are using SQLServer
> 2000. We confirmed today that the issue is the data lost between the
> creation of the snapshots. When a new snapshot is created, data that is
> the new snapshot but not in the snapshot downloaded will not syncronize if
> a sync was not performed immediately after the snapshot is loaded. Any
> settings that would cause this behavior?
>
> lip Vaughn" <philipv@.microsoft.com> wrote in message
> news:OSAMikALFHA.3552@.TK2MSFTNGP12.phx.gbl...
>