Resonate's product 'sounds' interesting. But the OP was about setting up
load balancing with a SQL Server Active/Active cluster. Resonate's product
does not do that.
And even with Resonate's product, there still is the issue of keeping the
databases synchronized. It has specialized uses, but clearly not for high
performance/highly reliable situations.

Signature
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
> There is, however a 3rd party tool that will allow you to do this:
> http://www.resonate.com/prod_db_disp.html
10001110101 - 26 Jul 2006 20:52 GMT
It was "documentation" that was relevant to the OP's question. I did
not get the impression that the original poster wanted opinion on what
was most appropriate for his/her implementation, but rather directional
documentation/ideas that could be perused to make an educated decision
regarding the deployment --and that is what I contributed. Offering
the details of what MSSQL can and cannot do is relevant, but more
importantly adding suggestions for alternatives could help engineer an
appropriate solution. Engineering the best solution is not always
black and white.
> Resonate's product 'sounds' interesting. But the OP was about setting up
> load balancing with a SQL Server Active/Active cluster. Resonate's product
[quoted text clipped - 14 lines]
> > There is, however a 3rd party tool that will allow you to do this:
> > http://www.resonate.com/prod_db_disp.html