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 |
|
mboobalan
Starting Member
1 Post |
 Posted - 2009-08-11 : 08:23:58
|
| HiI would like to have some suggestions on the kind of "Replication" which would be apt for the following scenario:The DB Servers are SQL server 2005. We have few DB servers for different regions and a common DB server. When the user wants to Sync the data, he can connect his DB server with the common server and do the same. The process can be done automatically or manually. The sync should be bi-directional. It can be done from any of the DB servers. The ultimate aim is to share all the DB server data via the common DB server.Thanks in advance.Regards,Boobalan |
|
|
paulo.tolosa
Starting Member
6 Posts |
Posted - 2009-08-11 : 09:09:32
|
| I think that all types of replication in SQL Server 2005 can be properly configured in the scenario that you told.But I think that you should expose the real necessity that you have in a way that we could try to suggest you one of the following solutions:# Snapshot replication acts in the manner its name implies. The publisher simply takes a snapshot of the entire replicated database and shares it with the subscribers. Of course, this is a very time and resource-intensive process. For this reason, most administrators don’t use snapshot replication on a recurring basis for databases that change frequently. There are two scenarios where snapshot replication is commonly used. First, it is used for databases that rarely change. Second, it is used to set a baseline to establish replication between systems while future updates are propagated using transactional or merge replication.# Transactional replication offers a more flexible solution for databases that change on a regular basis. With transactional replication, the replication agent monitors the publisher for changes to the database and transmits those changes to the subscribers. This transmission can take place immediately or on a periodic basis.# Merge replication allows the publisher and subscriber to independently make changes to the database. Both entities can work without an active network connection. When they are reconnected, the merge replication agent checks for changes on both sets of data and modifies each database accordingly. If changes conflict with each other, it uses a predefined conflict resolution algorithm to determine the appropriate data. Merge replication is commonly used by laptop users and others who can not be constantly connected to the publisher.Data from http://databases.about.com/cs/sqlserver/a/aa041303a.htm |
 |
|
|
|
|
|
Suggest a "Replication" type