May 12, 2008 at 6:31 pm
We have a database application that we want to run on two (and possibly more) different servers that will not be able to be connected. Is there a way to use (and set up) replication in SQL Server 2005 to periodically synchronise the data between these two databases?
Thanks,
David
May 14, 2008 at 7:31 am
I'm no expert here, but it seems to me that using a Pull subscription from your target machines will be the most effective way to 'replicate' the databases, since they are not constantly connected. It depends on how your systems are not 'connected'. Can you offer us some more detail as to how they can, and cannot, share data between them, and what the latency (or perhaps lag is more appropriate?) is expected to be?
Obviously, you do NOT expect them to be synchronized 24/7 or you would insist on having them connected.
May 14, 2008 at 4:51 pm
The servers will be on networks that will never be able to be connected. I figured that this could be set up by replicating from server 1 to a database then detaching the database and putting it on server 2. I just want to find out if there is any way to use replication to synchronise the two systems (there won't be a high volume of transactions).
Thanks,
David
May 23, 2008 at 9:30 am
Generally, replication requires one server to 'reach out' to the other server and connect. If they are 'never' connected, how are you porting the databases from one system to another? Also, if you are detaching to carry over, and then reattaching on the second server, then you are doing 'snapshot' replication in a 'brute force' kind of way.
when you are up to your *** in alligators, it's difficult to remember that your original objective was to drain the swamp. So, what is it that you expect replication to do for you that is not being accomplished now? More frequent synchronization? Have you considered a log-shipping type process?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply