> SQL is not designed to do active/dynamic load balancing.
>
[quoted text clipped - 16 lines]
>
> - Mostra testo citato
Whether to use peer-to-peer replication for load balancing is a rather
application specific question. In other words, for some apps, it may be a
good soultion. But for other apps, it's a terrible solution. If we are to
look for an infrastructure solution where different layers are cleanly
separated, I don't think you want to consider a peer-to-peer setup (unless
you like support headache).
Linchi
> Instead of a cluster solution you can obtain load balancing with peer
> to peer replication. Peer to peer replication is an high avalability
[quoted text clipped - 31 lines]
> >
> > - Mostra testo citato
Riccardone - 02 Jul 2008 14:25 GMT
If your service level require only high avalaibility, then cluster is
good. But if you need performance also, an high avalability solution
is peer to peer without headache. For example, there are not conflicts
because replication is transactional. Setup is not so difficult and
hardware is not certified required like cluster.
Peer to peer replication like all other high avalability solutions
other than failover cluster, is at database level and not at instance
level.
Another high avalability solution to obtain a load "read" balancing is
log shipping. With a log shipping solution, you can configure a read
only standby (or more readonly standby servers) and clients can
connect to it for reports and so on. In this case, you can mix a
failover cluster instance with a log shipping solution to obtain load
balance.
regards
Riccardo di Nuzzo
On 1 Lug, 21:34, Linchi Shea <LinchiS...@discussions.microsoft.com>
wrote:
> Whether to use peer-to-peer replication for load balancing is a rather
> application specific question. In other words, for some apps, it may be a
[quoted text clipped - 46 lines]
>
> - Mostra testo citato