Post reply

load balancing solution in SQL Server 2008?

  • April 17, 2012 at 5:38 am

    #259611

    Hi,

    Which is the best load balancing solution in SQL Server 2008? High availability options:

    Load balancing access same database for different server.

    1. Log shipping

    2. Replication (merge type)

    3. Cluster?

    4. Mirroring

    Thanks

    ananda

  • April 17, 2012 at 5:43 am

    #1474645

    SQL Server doesn't have any load balancing solutions.

    High Availability != Load Balancing

    ______________________________________________________________________________________________
    Forum posting etiquette.[/url] Get your answers faster.

  • April 17, 2012 at 5:47 am

    #1474648

    Scale-out can be done with peer-to-peer replication, but it has to be designed carefully and it's not a trivial thing to set up.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • April 17, 2012 at 9:15 am

    #1474801

    Traditional load balancing can't be done on servers with SQL Server (data gets out of sync as soon as a write is made to one of them). However, you can scale out and maintain synchronization if you build load balancing into the database itself--similar to Oracle 9i's Real Application Cluster--or through a middleware transaction server.

    Also, I'd recommend that you avoid Mirroring as it's deprecated (and thereby unsupported) with SQL Server 2012. An alternative to Mirroring is [AlwaysOn] Availability Groups.

  • April 17, 2012 at 9:44 am

    #1474830

    Felicia Coons (4/17/2012)

    Traditional load balancing can't be done on servers with SQL Server (data gets out of sync as soon as a write is made to one of them). However, you can scale out and maintain synchronization if you build load balancing into the database itself--similar to Oracle 9i's Real Application Cluster--or through a middleware transaction server.

    Also, I'd recommend that you avoid Mirroring as it's deprecated (and thereby unsupported) with SQL Server 2012. An alternative to Mirroring is [AlwaysOn] Availability Groups.

    Depreciated does not mean unsupported. If you are moving to SQL Server 2012, then look at using AlwaysOn instead of mirroring. If you are still working with SQL Server 2005/2008/2008R2 and need the HA capabilities provided by Database Mirroring, then use it.

  • April 17, 2012 at 10:20 am

    #1474866

    SQL Server can be scaled-out by leveraging Service Broker but it requires a home-grown solution that would be very labor-intensive to implement in terms of the amount of development required. None of the technologies mentioned in your original post are load-balancing per se, and there is no easy path to load balancing in SQL Server. One way to ease the burden on your primary database, the one that accepts updates from data clients, is to use one of the HA options to create a near-real-time, but read-only copy, of your primary database on a different instance and have any read-only applications read from the copy.

    What problem are you trying to solve?

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • April 17, 2012 at 1:26 pm

    #1474993

    We do it via transactional replication and Citrix netscalar.

    This is only readonly so you would have to do your homework on making it work as a read/write solution. It could work with peer to peer with minimal latency

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply