"markeboy" <top.gun@airforce.nz> wrote in message
news:EF1B8FF1-B663-4EC8-A802-49EDFC302B8D@microsoft.com...
>I have had an instance where certain rows have disappeared from the main
> server following a replication session.
>
> We are using Merge (pull) subscriptions using SQL2K standard as publisher
> and MSDE as the subscriber.
>
> The records that went messing are all in the tombstone with a reason of
> "system delete".
>
> I have eliminated the application that sits over this data from causing
> this, and based on the timing of the replication merge session, and based
> on
> when the data disappeared, replication seems to be the cultprit.
>
> Not all associated records were lost, only from 4 from 11 tables. The
> date
> range of records affected appear to be records entered immediately before
> the
> very frist replication sesssion and the next one (16 days later). The
> subscriptions are set to never expire.
>
> What in the pull merge replication model could cause a catastrophy like
> this
> to occur? How can I prevent this from occurring again?