Re: Load Balancing.



Hello Noor,

First of all, there is no a "Load Balancing" like Oracle' s Real Application Cluster (RAC) in SQL Server. There' s a pseudo Active\Active Clustering in SQL Server.

Also, clustering is not a load balancing method actually because it's a High Availibility solution. I just can be used as a part of a load balancing solution. If you set up more than one active nodes in a cluster, you can have more servers that you can move your SQL Server services in case of a hardware problem. However, you can use the other nodes to balance the load using Replication as I have done in my current project. For instance, in my project there are two node-clustered servers in every location and the first one is being used for OLTP purposes and the second one is being used as a reporting server. However, in my situation 4-5 second delays are not problem for my client.

Database Mirroring or Replication can be used to spread the workload between nodes. However Database Mirroring may not be useful for your situation because it won't let you to query the mirror database directly, you can achieve this only using Database Snapshots (in case your SQL Server instances are Enterprise Edition) but it won't give you a real time updated database because a database snapshot is a static view of a database.

If you want your replication to work faster, you should ask a question about this in the Replication newsgroup and I think Hilary or Paul may assist you there.

--
Ekrem Önsoy



"Noor" <naissani@xxxxxxxxxxx> wrote in message news:%23FTeYaxfJHA.5844@xxxxxxxxxxxxxxxxxxxxxxx
Hello Professional.

I am working in Trading Firm and you can imagine how many transactions would be in place per second, I was thinking to implement Peer To Peer Replication b/w two of our production Servers and we can implement load balancing as well but the only issue Peer to Peer replication takes almost 4 seconds to replicate the data bi directional, we also increase the bandwidth but didn't see improvements, we can't lose 1 second of data. I was more concern about if client place a trade on one server and through some reason we redirect him to another server and he can't see his transaction [becauase replication takes 4 seconds to replicate].

I would appreicate if anyone guide me or provide me any link through which I can fulfuil 100% load balancing configuration.We were also thinking to go with Clustering but Clustering is a hardware solution and I think Database Mirroring is better than clustering but we are looking for Active / Active connection b/w two Servers so both the Sql Server should be Active Active.

Thanks for your help

Regards



.



Relevant Pages

  • Re: sql clustering vs load balancing
    ... ALso, i would love to move away from replication, but how could you then ... For example if i have serves in cali, and a server in kentucky for backup. ... > Clustering Actice/Active is not load balancing, it means an instance of SQL ... >> machines also host our web sites. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Replication with failover clustering??
    ... Microsoft SQL Server clustering is not a good fit for geospatial clustering ... Both clustering and database mirroring do do automatic failover, ... Replication can have a greater ... Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)
  • Re: TS disaster recovery / split site scenario
    ... Here is another good link on load balancing TS... ... paragraph you say load balanced clustering with one server in the data ... If active/passive geographically disperse clustering ... I'm currently implementing a full disaster recovery solution for a client. ...
    (microsoft.public.windows.terminal_services)
  • Re: TS disaster recovery / split site scenario
    ... In one paragraph you say active/passive clustering and then in the next ... paragraph you say load balanced clustering with one server in the data ... If load balancing is what you are looking to do, ...
    (microsoft.public.windows.terminal_services)
  • Re: How to setup a second Exchange server with data replication (as a backup server)
    ... The High Availability model is based on MSCS (Clustering Svc), which stores Exchange data on shared storage (no replication). ... replicate Storage Groups from one Exchange server - the SCR source - to one or more Exchange servers - known as SCR targets. ...
    (microsoft.public.exchange.admin)

Loading