|Subject:||Re: Load balance|
|Posted by:||Hilary Cotter (hilary.cott…@gmail.com)|
|Date:||Sun, 27 Aug 2006|
Have a look at peer-to-peer replication. It will give you the scale out
performance you need. However it will not do the failover you are looking
for. For this you need clustering, or data mirroring. If you need to have
some processing done on one node, and then farm out other processing to
different nodes, you might be able to use DPVs, service broker, or merge
replication for this.
It really depends on your requirements.
Looking for a SQL Server replication book?
Looking for a FAQ on Indexing Services/SQL FTS
"Casper Hornstrup" <…@eudicon.com> wrote in message
> My application is based on ASP.NET 2.0 and SQL Server 2005. Most of my
> data-processing happen on the SQL Server (in two stored procedures written
> in C#) - the webserver don't do much in this setup. I'm investigating ways
> to have load balancing of the data-processing accross multiple (physical)
> SQL Servers in addition to having failover support in case one SQL Server
> does fail. Do I need to design my application specifically to support
> distributed processing or can SQL Server 2005 do this transparently? What
> options do I have?
Load balance posted by Casper Hornstrup on Sun, 27 Aug 2006