April 4, 2014 at 5:32 pm
Hello all,
Have a question about replication and if a database can be both a publisher and subscriber at the same time?
Here is a generic layout.
publisher A publishes to
subscriber b,
subscriber c,
subscriber d,
subscriber e and,
subscriber f who is a publisher to
subscriber g,
subscriber h,
subscriber I and,
subscriber j
I want to know if this is possible. All transaction publications
Thank you
April 6, 2014 at 11:48 pm
Are you planning to publish same articles across the all subscribers databases/servers?
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
April 7, 2014 at 8:43 am
Yes, you can use replication to "double hop" articles. This will add some additional complexities when modifying the topology but nothing too complicated.
Update-able subscriptions don't fully support this. The update will only propagate one level.
What kind of replication do you intend to implement?
April 7, 2014 at 9:05 am
It will be straight transaction read-only for the subscribers. The replication is already setup in our old domain, and we are moving to a new domain. Instead of ripping out all of the replication, I figure use the old replication that is working, and build out the new world
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply