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.

 All Forums
 SQL Server 2005 Forums
 Replication (2005)
 who is distributor, publisher and subscriber ?

Author  Topic 

Pherkad
Starting Member

23 Posts

Posted - 2007-03-28 : 09:58:44
hi,

I'm reading the MS online docs about replication. there's something not so clear until so far.

I have one central server and 7 client servers.
Sometimes new data is entered at one client server. This should be replicated (when client comes online) to the Central Server (merge replication).

Also, the other way, once the central server gets new data (that was replicated from a client), it should be again replicated to all 6 other clients (from the central server).

now, who should i configure as the distributor, publisher and subscriber?

Pherkad
Starting Member

23 Posts

Posted - 2007-03-28 : 11:25:28
now i think i understand.
we will use the merge replication.

my central server will be the publisher and also contain the distribution database.

my client servers will be the subscribers, keeping in mind that they will also be able to publish their new data back to the central server. is this correct and possible?
Go to Top of Page

dinakar
Master Smack Fu Yak Hacker

2507 Posts

Posted - 2007-03-28 : 11:46:11
You might also want to look at Peer-Peer Replication that is a new type of Rep in 2005. Each DB is a publisher and the other DB's are subscribers. I havent worked on Merge Rep so you might want to compare the features and performance. With 8 Db's participating any kind of replication could be slow, something to be aware of.

************************
Life is short. Enjoy it.
************************
Go to Top of Page

MohammedU
Posting Yak Master

145 Posts

Posted - 2007-03-28 : 14:44:24
Peer-to-peer replication is only available in EE where merge is in all editions...
You can use bi-directional transactional replication also...
If you are expecting the network failure and low bandwidth merge is the way to go...


MohammedU
Go to Top of Page
   

- Advertisement -