Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
Mark Worsnop
Starting Member
1 Post |
Posted - 2008-09-16 : 13:51:13
|
I am trying to build a system (Farm) where we can load balance RDP users that in turn use an application that accesses SQL 2008. The RDP part is set up well and is good. But now I am trying to figure out a way to have SQL Server on each machine, but have a common database on the SAN iSCSI box. I don't think there is a way to do this, is there?The only option I can see at this time is to have SQL Server installed on both servers, but have one of them the active and the 2nd SQL stopped.This keeps more load on the 1st server obviously. Then it will have to be a manual process to start the 2nd SQL if the 1st server fails.Does clustering do load balancing or only fail over? I am wondering if I should make these servers into a cluster and SQL into a cluster too? I looked at clustering a long time ago, and I seem to remember that one machine did the work, and the 2nd one took over if the 1st one failed.Any ideas? |
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-09-16 : 13:57:34
|
Clustering does not do load balancing.You can "load balance" SQL Server by using partitioned views across servers, known as federated servers. I don't know what SQL Server 2008 has to offer in this department though, but partitioned views is what was used in the past. Partitioned tables are available in SQL Server 2005, however you can't achieve load balancing as you can't spread across servers. Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
|
|
saurabhsrivastava
Posting Yak Master
216 Posts |
Posted - 2008-09-28 : 17:48:36
|
Clustering does not offer load balancing. Faliover happens when one node in cluster stops working. |
|
|
|
|
|