November 4, 2008 at 9:54 am
I have a production server - 'A' that I want to replicate its databases to a DRP server - 'D'. I also have a need to replicate some of the databases on 'A' to a test server 'C'. Can I set up a central replication server - 'B' that would act as a gateway from 'A' to the rest of the world? If so, can it be done without having to put copies of the databases on 'A' onto server 'B'? I understand having servers 'C' and 'D' in sync to start with, but trying to figure out a gateway type of solution. I'm looking to do transaction replication. Anyone able to give me an answer will be greatly appreciated.
November 4, 2008 at 11:24 am
Yes, you can. Enable replication at the server you are going to use as central processing. Your publications will be created in the servers with the databases to be replicated, the subscribers will be the destination for the replicated data, bubt all the processing will be done at the central replication server.
I hope the little drwaing is clear when you get it. I used this architecture quite a lot. One thing you need to have in mind is that the distributor may be a single point of failure, so I recommend to have this server covered by a fail over plan.
||||||
| |<--- Publisher2
| |
| |
||||||
- Transactional Replication 2
------------>
||||||
| |
| |<--- Publisher 1
| |
|||||| - ||||||
- Transactional Replication 1 | |
------------> | |<--- Distributor
| |
||||||
|
<------------------------------
Transactions to write 1
||||||
| |
| |<--- Subscriber 1
| |
||||||
|
<------------------------------
Transactions to write 2
||||||
| |
| |<--- Subscriber 2
| |
||||||
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply