Adding 3rd server to bi-directional replication configurat..

I have 2 servers that fully replicate a large database -- it comprises
of a number of publications (each with a few articles). This works
perfectly.

I want to introduce a third server. This server will subscribe to a
few of the publications, publish/subscribe to 1-2 publications, and do
nothing with a bunch of publications.

How do I set this up?

1. Do you call "sp_addsubscription" for the publications i want to
subscribe to? I assume, i just pick 1 of the 2 existing servers for
@subscriber, right? this basically creates like a "chain". Is this
the way everyone does it? i feel if i sp_addsubscription to both
existing databases, i will get twice the inserts and double the
updates, so i am confused.
2. Do I sp_addpublication and sp_addarticle ONLY for the publications
i will participate bi-directionally ? I guess I am confused what SPs
are required for publish, subscribe, and both. I have only set it up
one way.

My current method is:
sp_replicationdboption 'mydb', 'publish', 'true'
go
sp_addpublication 'mypub', @status='active'
go
sp_addarticle 'mypub', 'tableA', 'tableA'
go
sp_addsubscription @publication='mypub', @article='all',
@subscriber='otherDB', @destination_db='mydb', @sync_type='none',
@loopback_detection='true'


This is what I do for BI-DIRECTIONAL. But if I bring in a third
server and he will be bi-directional for 1 publication and subscriber
only for 3 publications, how do I do this? any help appreciated.
This is in production and company does not have resources of a decent
test environment.

Basically set server A up to replicate to server B and server C.
Set server B to replicate to Server A and C.
Set Server C up to replicate to server B and A.

You will need to set up identity increments of 3 and seeds of 1 on A, 2 on
B, and 3 on C.

Make sure the next assigned identity value will agree with the location
seeds.

<stevehunter_1.TakeThisOut@hotmail.com> wrote in message
news:78e55f7a-a776-4423-b6d6-7f55faa45e8b@w8g2000prd.googlegroups.com...
>I have 2 servers that fully replicate a large database -- it comprises
> of a number of publications (each with a few articles). This works
> perfectly.
>
> I want to introduce a third server. This server will subscribe to a
> few of the publications, publish/subscribe to 1-2 publications, and do
> nothing with a bunch of publications.
>
> How do I set this up?
>
> 1. Do you call "sp_addsubscription" for the publications i want to
> subscribe to? I assume, i just pick 1 of the 2 existing servers for
> @subscriber, right? this basically creates like a "chain". Is this
> the way everyone does it? i feel if i sp_addsubscription to both
> existing databases, i will get twice the inserts and double the
> updates, so i am confused.
> 2. Do I sp_addpublication and sp_addarticle ONLY for the publications
> i will participate bi-directionally ? I guess I am confused what SPs
> are required for publish, subscribe, and both. I have only set it up
> one way.
>
> My current method is:
> sp_replicationdboption 'mydb', 'publish', 'true'
> go
> sp_addpublication 'mypub', @status='active'
> go
> sp_addarticle 'mypub', 'tableA', 'tableA'
> go
> sp_addsubscription @publication='mypub', @article='all',
> @subscriber='otherDB', @destination_db='mydb', @sync_type='none',
> @loopback_detection='true'
>
>
> This is what I do for BI-DIRECTIONAL. But if I bring in a third
> server and he will be bi-directional for 1 publication and subscriber
> only for 3 publications, how do I do this? any help appreciated.
> This is in production and company does not have resources of a decent
> test environment.