Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We need to use the BCP utility to port database (>1GB) to a remote database server across the internet. We can use the BCP utility to connect to the remote SQL Server, or we can copy over the BCP files across the internet into the "intranet" of the remote SQL Server, and then run the BCP utility from there.

Can someone comment on the feasibility, and performance differences?


share|improve this question

migrated from Oct 2 '10 at 8:22

This question came from our site for professional and enthusiast programmers.

1 GB is a trivial amount of data if you're only going to do it once. If you're going to do it every day/week/month, then it's worth measuring time taken/bandwidth used for both approaches and picking based on those results. – tc. Oct 2 '10 at 2:25
up vote 1 down vote accepted

It will be slower, but BCP out on the source server, then copying the files to the remote server's file system to BCP in is likely to be the most robust option.

If you try and BCP directly from the source to the target servers over the internet, you leave yourself open to the risk of an interruption to the connection which would stop the copy and leave the target server in an inconsistent state.

Far better to give yourself the chance to validate that the files have copied correctly - you can check MD5 sums and so on - before attempting the BCP in.

share|improve this answer
You might also consider running gzip or bzip2 on the BCP output file before sending it over the Internet. – jftuga Oct 2 '10 at 13:23

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.