![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have 2 web server in load balancing configuration (NLB) and one database. We are going to add another web server. The problem is simple: too many connections on the database. It is a bottleneck. I know that microsoft did not create Real Application Cluster (like oracle ;-)) ), and I was testing 2 instance (one for each web server) with the peer to peer transactional replication splitting connections and replicating data to align databases. There are many problems with peer to peer replications (conflicts, identity iussues, ecc.), and I have so many tables. Do you have any other idea/solution to split/balance connections ? Thanx Massimo (Mastino) |
#3
| |||
| |||
|
|
I have 2 web server in load balancing configuration (NLB) and one database. We are going to add another web server. The problem is simple: too many connections on the database. It is a bottleneck. |
|
Do you have any other idea/solution to split/balance connections ? |
#4
| |||
| |||
|
|
"mastiff" <golan (AT) trevize (DOT) com> wrote in message news:4a16f32a$0$1108$4fafbaef (AT) reader4 (DOT) news.tin.it... I have 2 web server in load balancing configuration (NLB) and one database. We are going to add another web server. The problem is simple: too many connections on the database. It is a bottleneck. How many connections? What is the SQL hardware? What version of SQL? Do you have direct connectivity from the Web servers to the SQL using GigE or better? What devices are in between? What are the perfmon counters telling you are the bottle necks on the SQL? Do you have any other idea/solution to split/balance connections ? This sounds like a matter of scaling up, not scaling out. -- Russ Kaufmann, MVP, MCSE: Messaging and Security, MCT, MCITP, MCTS and other stuff ClusterHelp.com, a Microsoft Certified Gold Partner Web http://www.clusterhelp.com Blog http://msmvps.com/clusterhelp |
#5
| |||
| |||
|
|
There are many ways to scale SQl server instance. it's up to you to choose one of them or continues with ongoing configuration Some of them are 1).u can use database mirroring and then redirect all read requests to mirror server (by creating snapshot ). This configuration will scale your system as it reduce the shared locks on main SQL server table . But this workaround needs some application level changes 2). You can use two node active/active cluster and divide the database into two database and then install them on each cluster node . e.g install the first half of database to default instance on first node and other half on named server on second node , now if one of the node goes done it will fail over to other . In this way you will get scalability and high availability. But this approach need database level changes. 3).u can implement transactional replication of important table and then redirect all read statement to that server. 4).use distributed partitioned views Manpreet Singh http://crazysql.co.nr http://crazysql.wordpress.com MCITP - DB Admin, DB Dev SQL Server 2005 MCTS - MOSS 2007, SQL server 2005 "mastiff" wrote: I have 2 web server in load balancing configuration (NLB) and one database. We are going to add another web server. The problem is simple: too many connections on the database. It is a bottleneck. I know that microsoft did not create Real Application Cluster (like oracle ;-)) ), and I was testing 2 instance (one for each web server) with the peer to peer transactional replication splitting connections and replicating data to align databases. There are many problems with peer to peer replications (conflicts, identity iussues, ecc.), and I have so many tables. Do you have any other idea/solution to split/balance connections ? Thanx Massimo (Mastino) |
![]() |
| Thread Tools | |
| Display Modes | |
| |