If the servers can't see each other, then you need to either find an intermediate server that can see both, or figure out some way of moving files between the two. If you have an intermediate, then you could run an SSIS task from there, pumping data between the other two servers. Of course, this won't be as quick as a direct connection... How do you access the data on the remote system now? (or is this a new thing?)
Depending upon how much data you are wanting to move around you have a few options (in the order I would go for): 1. Backup & Restore (either the entire database where the data resides, or push the data you want moving into a second "temporary" database) 2. BCP / SSIS (dump the data you want to move to flat files, then copy them to the new system and import using BCP/SSIS) 3. Replication (replicating only the tables you want using snapshot replication)
Import/Export from a second network? Assuming that the two servers can see each other, and it's not a huge amount of data you want to shift, you have a few more options over those that @WilliamD has suggested: - Linked Server - set up a direct link between the two servers, so you can issue queries from one against the other - [OpenRowset] - create an ad-hoc connection within a SQL Server query Otherwise, I would look at going with those options of @WilliamD's, with the following extra twist: - Reduce the size of the backup before transferring it - or, indeed, while backing it up. Look at Quest Software's SQL Litespeed for example (other products exist from Redgate, Idera and others) And if your network is slow, remember that it can sometimes be quicker to copy data using a USB hard disk... :
Based on your updated information I would use a linked server with SQL accounts and issue a few queries to fresh the information in your destination tables. The first query would likely be an insert of all the records you need, then going forward use a WHERE clause to just get the updated records.