sql server replication: Hopefully someone could lend me a hand or point me in the right
direction.

Current System Configuration:

Publisher: Windows 2000 Server SP4 & SQL Server 2000 SP3
Subscriber: Windows XP SP1

Due to a system crash, I now have a subscriber table with more rows in
it than the publisher table. Replication was corrupted due to the
system crash and it needed to be re-enabled at the publisher.
However, when the new subscription is initialized at the subscriber
all rows added since July 12th (Day of the crash and day of last sync)
are removed at the subscriber. Is there anyway to get these rows to
remain and be merged to the Publisher? I've tried every option in the
Name conflicts section of the Table Article Properties.

Thank you.

Paul,

Thank you for your reply.

I'm using merge replication and the subscriber is an anonymous one.
Also, the subscriber is running MSDE and using the Windows Sync
Manager.

However, I've done basically what you've suggested by manually syncing
the data. I had just hoped there was any easier way to do it.

Do you know if what you suggested about reinitializing is possible

Joshua,

what type of replication are you using? If it is merge and you select to
reinitialize, there will be a dialog box which appears asking if you want to
upload changes from the subscriber. If you don't reinitialize, then just
running the merge agent should synchronize the data.

Presumably your case is not so simple and in some cases you have to do this
manually using linked servers and binary checksums to determine the
differing rows. The extra rows are added to the publisher then you can set
up the publication as usual. If the binary checksums are used to make the
publisher and subscriber articles identical then you can do a nosync
initialization.

HTH,

Paul Ibison

Joshua,
yes - exactly the same option appears in WSM.
Regards,
Paul Ibison