I'm running Merge replication on a SQL Server 2008 topology. I have run into a situation where the sysmergesubscriptions on the publisher looks like it is not being updated. The max sentgen is over 2 days old. However, I am certain that replication is still running as data is getting across the topology. The MSmerge_genhistory tables are processing rows and latency seems to be minimal.
Over the past week we had some problems with the publisher and had to move the distribution database log file as it was continually filling up and the disk it was located on was not large enough. As a result we needed to stop and start the publisher sql server instance.
Is there anyway to 'kick start' sql server to refresh the sysmergesubscriptions
Thanks,
Tom