One Database - two distributors, possible?

Last Post 28 Jun 2004 01:27 AM by sbsedo. 1 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
New Member
New Member

24 Jun 2004 06:38 AM

I have a production system: Transactional Replication
Server A (Publisher)
Server B (Distributor, Subscriber)

everything fine!

Now I got a new Server C
Server C should also subscribe the publication to server A
But the distribution Database is on Server B.

I want that every subscriber has it's own distribution database.

I made a 2nd publication on server A and made a distribution on server c,
But Server A talks only to distribution on server B. and I think that could be a performance and
availability problem, because everything goes over server B

Have you any ideas?
My wish configuration:

Server A: Publication for Server B
Publication for Server C

Server B: distribution B, Subscriber

Server C: distribution C, Subscriber

Please Help ME
New Member
New Member

28 Jun 2004 01:27 AM

Thank you for the time you spent!
I have now a solution that is for me acceptable.

I made one distribution db on the publisher.
Every subscriber is configured as Remote Distribution Agent, so the CPU time should be at the subscriber. That should be a compromise.


You are not authorized to post a reply.

Acceptable Use Policy