"Wrap" replication files

Is there a way to distribute merge and transactional replication commands/files such that a slight hiccup in the connection does not cause replication to fail? Maybe like wrapping them in a zip or other type of file?No, nothing built in, but even if that were the case that won't prevent problems, what if the connection failed during the transfer of the zip file? There's built-in retry logic in the agents for network failures, is this not working correctly for you?|||What do you mean by built-in? Is this supposed to be automatic? Are there settings or distributor properties/parameters I have to set for this? I am not talking about a total loss of connection - just a slight hiccup in communications. Maybe the files could be buffered somehow during the transfer. Is there a way for a custom application to interact with this process?|||distribution agent should retry 10 times before completely stopping, you can increase this interval. For merge agent, since it's scheduled it should just pick up again where it left off on the next sync, or if you're using rmo, you can always check for a disconnect and resubmit a sync.