Re: Want to load balance and cluster 3 SQL 2005 servers

So how could I load balance the servers? Is there anything in SQL 2005 to do
that? Or am I going to need some sort of layer 7 load balancer?

"Ryan Sokolowski [MVP]" wrote:

Sorta' :) NLB isn't going to do anything for you w/r/t SQL. Clustering the
SQL instance (with MSCS) is the right approach. NLB is much better suited
for IIS-type front-end services.

A note here: SQL 2005 Standard edition will only support 2 Failover
Clustering nodes, not 3 as you've mentioned.

As for "everything just picking back up again", this is primarily dependent
on your client app. So long as you've properly configured your back-end
cluster, the ability and speed of client reconnects depends on the
application and how it's been written.

Hope this helps,
--Ryan

--
Ryan Sokolowski
MVP - Windows Server - Clustering
MCSE, CCNA, CCDA, BCFP


This posting is provided "AS IS" with no warranties, and confers no rights.
"MValpreda" <MValpreda@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D9F2FB9D-E174-46DE-B12E-553275EFFE5E@xxxxxxxxxxxxxxxx
Currently we have a single SQL server. It went down and the higher ups
were
none to happy. Lots of money lost, down time, unhappy customers....the
whole
nine yards. They want to throw all sorts of money at the problem and want
a
solution that is high availability and provides load balancing. I think I
came up with a solution.

3x Windows 2003 Enterprise Edition servers running SQL 2005 Standard in a
cluster all connected to a SAN.

I'm guessing I need to set up Network Load Balancing in order to load
balance the SQL database. What we would love to have happen is if one of
the
servers goes down, everything else just picks up. That coupled with our
database that is increasing in size and transactions gets load balanced.

Am I going down the right path? Something else I should look at? Or that I
am missing?

Thanks!



.

Relevant Pages

  • Re: SQL 2005 servers with multiple instances
    ... Have you checked out the latest possible hardware configurations for SQL ... I have built two-node clusters with dual-proc dual core brand name servers ... Clustering is no ... controller is being shared for the Live data and the Redundant data/logs. ...
    (microsoft.public.sqlserver.setup)
  • Re: Want to load balance and cluster 3 SQL 2005 servers
    ... Sorta':) NLB isn't going to do anything for you w/r/t SQL. ... Clustering nodes, ... I'm guessing I need to set up Network Load Balancing in order to load ...
    (microsoft.public.windows.server.clustering)
  • Want to load balance and cluster 3 SQL 2005 servers
    ... Currently we have a single SQL server. ... Lots of money lost, down time, unhappy ... 3x Windows 2003 Enterprise Edition servers running SQL 2005 Standard ... I'm guessing I need to set up Network Load Balancing in order to load ...
    (microsoft.public.windows.server.clustering)
  • Re: Transition from Stand-ALone SQL Server to Cluster
    ... Make sure your hardware is on the Windows HCL for clustering, ... Mike Epprecht, Microsoft SQL Server MVP ... > setting up something to distribute the workload between more servers. ... > storage design if necessary. ...
    (microsoft.public.sqlserver.clustering)
  • Re: BizTalk Clusters
    ... This suggests that FTP requires clustering, but that a File adapter can be ... scaled out in a BizTalk Group with no mention of possible issues. ... you were talking about two BizTalk servers that were not in the same BizTalk ... Services lend themselves very well to load balancing, ...
    (microsoft.public.biztalk.general)