Re: Peer to peer replication on SQL 2000?

Consider three servers. Server A, Server B, and Server C. Server A is the
publisher, Server B and Server C are subscribers to Server A.

Server A - the publisher goes offline. Changes occurring on Server B and
Server C remain there until Server A comes back online.

What the op was asking about was peer to peer replication, where if the
publisher (Server A) goes offline, Server B and Server C continue to
synchronize. Let me quote him for you "Hello, reading about peer-to-peer
transactional replication in SQL 2005
(http://msdn2.microsoft.com/ms152536.aspx), I would like to do the same
thing with 3 SQL 2000 servers."

Bi-directional Transactional replication cannot do this, and I have been
unable to get it to work with more than two nodes even with filtering and
partitioning.

--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

"Michael Hotek" <mike@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:uP$CIQUEGHA.1120@xxxxxxxxxxxxxxxxxxxxxxx
> HUH??????????????????????????????????????????????????????
>
> How are the "other two nodes out of luck"? The only replication
> implementation that requires the publisher to be online in order to
> process changes against a subscriber is immediate updating. With merge,
> if the publisher goes down, you can continue to process changes against
> any subscriber. When the publisher comes back online, everything
> automatically resynchronizes itself. Don't tell me that it can't be done,
> because I have this type of environment running with both merge AND
> transactional with queued updating subscribers and hundreds of customers.
>
> --
> Mike
> Mentor
> Solid Quality Learning
> http://www.solidqualitylearning.com
>
>
> "Hilary Cotter" <hilary.cotter@xxxxxxxxx> wrote in message
> news:%23P67ZKSEGHA.828@xxxxxxxxxxxxxxxxxxxxxxx
>> Bi directional transactional replication only works between 2 nodes. The
>> closest you can get is merge, but this would require your publisher to be
>> always accessible. If it goes down, the other two nodes are out of luck.
>>
>> --
>> Hilary Cotter
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602.html
>>
>> Looking for a FAQ on Indexing Services/SQL FTS
>> http://www.indexserverfaq.com
>>
>> "Paul Ibison" <Paul.Ibison@xxxxxxxxxxxxx> wrote in message
>> news:%23AE7C%23REGHA.3984@xxxxxxxxxxxxxxxxxxxxxxx
>>> AL,
>>> the nearest thing is probably bi-directional transactional replication:
>>> http://support.microsoft.com/default.aspx?scid=kb;en-us;820675
>>> Cheers,
>>> Paul Ibison SQL Server MVP, www.replicationanswers.com
>>> (recommended sql server 2000 replication book:
>>> http://www.nwsu.com/0974973602p.html)
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: Merge versus Two Way, Bidirectional Transactional Replication
    ... ranges are blown and transactions are kicked back and lost. ... Looking for a SQL Server replication book? ... You can restore a publisher or subscriber without ...
    (microsoft.public.sqlserver.replication)
  • Re: filename is too long or contains illegal caracters
    ... server because I can publish the same web site over the same connection using ... past told me they don't know anything about Publisher). ... When I ADD NETWORK LOCATION, I get "folder ... Per you suggestion, I tried to Add a Network Location in "Computer", ...
    (microsoft.public.publisher.webdesign)
  • Re: User Defined Functions - Replication
    ... You can also apply them on all subscribers deployed via unc by using ... Looking for a SQL Server replication book? ... My user defined functions have permissions setup on a primary server. ...
    (microsoft.public.sqlserver.replication)
  • Is complete control over subscriber-to-publisher inserts/updates possible?
    ... we are using merge replication from our server to what ... will soon be hundreds of subscribers. ... a scenario very similar to what we need (Custom Change Handling -> Apply ...
    (microsoft.public.sqlserver.replication)
  • Re: Best replication architecture?
    ... deprecated for SQL Server 2005 without any alternative having been provided ... So if it is subscribing to Publisher 1, ... Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)