If you have SQL Server 2005 Enterprise Edition you can use "Web Replication" to replicate over port 443.

If you do not have access to Enterprise Edition you have to open port 1433 (for sql server) and 21 (for ftp) to drive the traffic. This is not safe if you have to go over a public network, so it is better to set up a manual system to move the replication files over the non trusted part of the network (via sftp or something.)

i'm creating the publication and i would like to save the files to the other server. so i setup ftp replication. there are no errors when i setup that info, and on the tab for where to put the files, i put in folder and there are no problems there. but when i invoke the agent it says that it can't copy the files. no other error. i put port 21?? no clue if that is what i'm suppose to be using or not.

Featured Post

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

Recently we ran in to an issue while running some SQL jobs where we were trying to process the cubes. We got an error saying failure stating 'NT SERVICE\SQLSERVERAGENT does not have access to Analysis Services. So this is a way to automate that wit…

Viewers will learn how to use the UPDATE and DELETE statements to change or remove existing data from their tables.
Make a table:
Update a specific column given a specific row using the UPDATE statement:
Remove a set of values using the DELETE s…