Before I go set up some test machines I thought I would ask a few questions here. We're going to replicate data over the internet (transactional replication) and using UNC paths for replication will not be allowed since it requires 135,445 etc through the firewalls. I want, if possible, send all data over the SQL port (say 1433). So I'm looking at some options. Publisher and distributor are on the same server. Subscriber is on another. 1. I noticed that if I select a local path like D:MSSQLREPLDATA for my snapshot folder SQL Server will say "Note that you can only use push subscriptions with a local snapshot folder". Does this mean that you can actually push the snapshot over the SQL port just like you do with the transactions? That the publisher will write the snapshot files on local disk and then read them again and push to the subscriber. Or how does that work? Maybe you need disk access via UNC to the subscriber instead of to the publisher as when you do a pull subscription? Would be cool if no UNC was needed. 2. I looked at the FTP option but the publisher still has to have UNC path access to the root folder of the FTP. Only the subscriber can connect to an external FTP and download the snapshot folders. That means that if we are replication some tables in one direction and others in the other direction we need to have a FTP running in both locations. Also the ftp client used by SQL seem to use active mode and not passive making firewall rules a bit complicated. 3. I heard something about using merge replication even if you're only replicating the specific tables in one direction and that this type of replication would go over the SQL port only. But how do you resync a merge replication that is out of sync? Isn't there some snapshot option here too?