up vote 0 down vote favorite
share [g+] share [fb]

We have a database (source) located at a place, where data transfers are expensive. We need to have a duplicate of this DB (target) locally, and make sure it gets updated with recent data once a day. The source DB is large, and require that we setup the local (target) DB from a backup from the source DB first, because it would be very expensive to transfer all data over the net first.

Should I like into MS SQL Service Broker or DB mirroring?

link|improve this question
How big is "large"? Can you not just backup source and restore to target once / day? – squillman Jan 16 at 15:17
DB is approx. 65GB and is located in another country. The price for datatransfers from there are enormous, so I need to figure out how to keep a consistent copy of it and only update changes. Perhaps I could look into how to setup a replication, if it's possible to first setup the target db from a backup. – joeb Jan 16 at 15:26
Ah right, sorry. I was thinking "local" = local to the source db. (Monday morning for ya). Any stats for how much data is modified daily? – squillman Jan 16 at 15:28
probably no more than 100MB daily. – joeb Jan 16 at 15:33
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.