Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
basicconfiguration
Constraint Violating Yak Guru
358 Posts |
 Posted - 2012-01-27 : 03:06:00
|
| I have a production database in the East Coast. I wanna copy the database to the West Coast using the fastest way to do it. The way I did it it's I backed up the database (27 GB) and copied to my local computer. It took 7 hours!!! Id appreciated it if you know of a faster way. I wanna reduce to less than an hour if it's possible. |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2012-01-27 : 07:48:37
|
| If you're using SQL 2008 Enterprise or SQL 2008 R2 Standard or Enterprise, they have built-in backup compression. It should reduce your backup to 9 GB, possibly less. There are also 3rd party backup tools for SQL Server from Quest (LiteSpeed) and Redgate (SQL Backup).If you want even better compression, you can try WinZip, WinRar or 7-Zip. Do not use these on an already compressed backup file, they won't make it smaller. 7-zip is completely free, and at the highest settings produces very small files (your backup could be 1 GB or smaller) but it's the slowest of the three. |
 |
|
|
dsf74
Starting Member
1 Post |
Posted - 2012-02-06 : 17:14:50
|
| Send with Binfer. Make sure you configure your firewall manually(see their Help) to utilize full speed of your Internet. Ultimately your internet speed determines the time it will take to send such large files. I use it regularly to send data backups to home office. |
|
|
|
|
|
|
Transfer large file from coast to coast