>I am using a merge replication with a push subscription from one SQL2000 Server to a second one. The replication at the subscriber seems to have hanged. That is, the monitor says it is running but nothing is being replicated. I have deleted the subscription from the pushing distributor but the subscriber still shows the merge running. I even deleted the publication on the publisher but the subscriber still shows the merge running. I cannot recreate the publication and push subscription because I get the error that a table cannot be dropped due to its use in replication.
>
>How can I get the subscriber database to realize it is no longer a replication subscriber and stop all the rep things it thinks it is doing but isn't?
>
>Paul

Paul,

It is a common occurence for SQL Server 2000 to leave some tables/columns flagged as participating in replication when the replication has actually been removed. To fix it, run

UPDATE sysobjects SET replinfo = 0 WHERE replinfo <> 0

If you have more than one replication set up, you should tighten up the WHERE clause to hit only the tables/columns that were in the deleted replication.