sql server replication: Darin,
your best bet is to stop the subscriber or work out of hours. Use the
subscriber's data as a starting point - backup the database and restore on
the publisher. Then do a nosync initialization.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

2 machines both running Windows 2003 w/ SQL 2000 SP4. One machine is
publisher & distributor, the other is the subscriber.

Last night, somehow the SQL Server program on the distributor got
corrupt and won't start (get the error that a file is missing). So, I
believe our only hope is to re-install the SQL Server program on the
distributor.

But, my problem is the subscriber is still running. Once the SQL is
re-loaded and the publisher's database loaded, it will say it is
replicated but all of the system tables won't know it.

What process do I need to go through to get the publisher database
reconnected and replicating AND to make sure all data on the subscriber
that is being modified during this time will get replicated when the
publisher comes back online.

TIA

Darin

If i dont' stop the subscriber (nor do a sp_removedbreplication) and
then setup the publisher again and Push the subscription to the
subscriber - will that create 2 "pushes" on the subscriber end?

Darin

No - by default it'll overwrite the subscriber's data using the publisher's
data. That's why I'd get the data synchronized (using Redgate or
backup/restore) then remove replication, then do a nosync initialization.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com