Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Replication vs log shipping
Message
From
11/12/2006 08:57:46
Keith Payne
Technical Marketing Solutions
Florida, United States
 
 
To
08/12/2006 19:12:58
General information
Forum:
Microsoft SQL Server
Category:
Replication
Miscellaneous
Thread ID:
01176308
Message ID:
01176512
Views:
14
This message has been marked as the solution to the initial question of the thread.
>There are three servers, not co-located.
>
>There are several large databases to be kept in sync on all servers.
>
>There are periodic needs to replace all of the data in any given database, about 30 GB.
>
>What would be the most efficient method to update the other servers, replicaiton, log shipping, or soem other??

Rollin,

We need a little more information before recommending one solution over another:

1. Will all three servers have CRUD transactions that need to be integrated with the other two?
2. What is the minimum acceptable lag time between the databases being syncronized?
3. Do you already have scheduled nightly maintenance processes and the infrastructure to support them?
4. When you say that the servers are not co-located, do you mean that they are all local and on the same network or that they are spread out geographically and on separate (slower) networks?
5. Do you need to encrypt the data as it travels across external networks?
6. What is the normal load on the servers - is there enough power in reserve to support replication?

A quick bit of advice that I can give is that if you want to completely replace a database periodically, then log shipping by itself is not enough. You would have to send a database backup to the 'new' server to re-initialize it.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform