wrote:
> We have a server set up using mergereplicationwith 20 client subscriptions.
> The publication is filtered with a very simple hostname filter. We are
> experiencing some reliability issues that I would appreciate some feedback on.
>
> Occasionally when synchronising the clients appears to lose connection or
> timeout (not everytime- it is often when the client has a poor) the clientdatabasecan then be left completelyempty. I have personally seen this occur
> on two systems - at thetimeI witnessed it the wireless network had gone
> down meaning the two subscribers were disconnected mid sync, both systems
> were left with adatabasethat had previously had thousands of rows of data
> being completelyempty. At this point the system was not applying a new
> snapshot neither the client of the server was set to reanalyze it was a
> normal straight forward sync. We have also seen this occur on systems when
> the publication has been reinitialized.
>
> We are using a custom application to synchronise the subscribers and the
> process involves
> 1) Shrinking thedatabase
> 2) backing up thedatabase
> 3) syncing (using RMO)
>
> However, I have seen this occur when using windows synchronisation utility
> on one occasion.
>
> Can anyone explain why this might occur and how we can avoid it?
>
> --
> Best Regards
> ----------------
>
> Dave Abraham