I have a 70 GB merge-replicated production database on which I need to
perform some maintenance.  This maintenance will require the removal of my
subscription.  I am trying to minimize downtime, obviously, and wonder about
the ramifications, if any, of setting up a no-sync subscription after my
maintenance is complete.  The subscription exists off-site, and I want to
avoid a new subscription push across the WAN.  Also, I see a snapshot option
to "Keep the existing table unchanged."  Would that be better than a no-sync?
In the past, we have always dropped and recreated objects during replication
setup.

Thanks!
Stephanie Williams