Our hosting provider would like restart the SQL Server that a publisher in a merge replication topology.
I'm not able to clearly understand best practice for doing this from the Microsoft docs.
Our topology consists of ~40 Pull subscribers. The synchronisation is executed on a schedule ever 5 minutes via a Windows Scheduled task that runs an App that calls RMO.
Some of my concerns include: Will transactions be safely cued on the Subscribers - I imagine this will potentially cause transaction log growth? What is a reasonable time period for the Publisher to be offline - do I need to worry about expiry?
If someone could outline what steps would be involved in safely shutting down the Publisher that would be a great help.