Re: SQL 2005 Peer-To-Peer - How to configure failover (If possible)
- From: "Rubén Garrigós" <rgarrigos@xxxxxxxxxx>
- Date: Mon, 31 Mar 2008 17:56:29 +0200
Paul, maybe Dave will be confused with your answer. .In a p2p replication in
SQL Server 2005 each node has a full copy of the database so data is not
physically partitioned. Partitioning writes is a good idea to avoid
conflicts and problems when reading last written data but it doesn't mean
that the data is partitioned.You can also balance the writes (preventing
conflicts) with a p2p replication, not only the reads.
My two cents
--
Rubén Garrigós
Solid Quality Mentors
"Paul Ibison" <Paul.Ibison@xxxxxxxxxxxxx> wrote in message
news:ur%23h2lFkIHA.536@xxxxxxxxxxxxxxxxxxxxxxx
Dave,
no doubt you already know this but just to clarify that in peer-to-peer
the data is partitioned, so going from one server to another for load
balancing only really refers to reads.
Anyway, there's no out-of-the box technique for swapping the connection
and establishing a heartbeat between the nodes, so it'll always be
proprietrary.
Rgds,
Paul Ibison
(www.replicationanswers.com)
.
- Follow-Ups:
- Re: SQL 2005 Peer-To-Peer - How to configure failover (If possible)
- From: Paul Ibison
- Re: SQL 2005 Peer-To-Peer - How to configure failover (If possible)
- References:
- Prev by Date: LINQ to SQL and Merge Replication
- Next by Date: Re: SQL 2005 Peer-To-Peer - How to configure failover (If possible)
- Previous by thread: Re: SQL 2005 Peer-To-Peer - How to configure failover (If possible
- Next by thread: Re: SQL 2005 Peer-To-Peer - How to configure failover (If possible)
- Index(es):
Relevant Pages
|
