You are right Eddie and I agree with you

But let's all think about the following scenario (Note: I didn't test yet)

There is another solution called "Network Load Balancing" that comes with Windows servers 2000 Advanced server and next later versions of windows so I believe that the way we can make Active - Active solutions is to merge both techniques together.

what I want to say is in case we have enough resources and servers we can do the following:

Windows Clusters Configuration:

Cluster A (SQL Node 1, SQL Node 2) ----> Shared disk Drives (ABCD) , Cluster A IP Address: 192.168.0.110

Cluster B (SQL Node 3, SQL Node 4) ----> Shared disk Drives (ABCD) , Cluster B IP Address: 192.168.0.120

Cluster C (SQL Node 5, SQL Node 6) ----> Shared disk Drives (ABCD) , Cluster C IP Address: 192.168.0.130

Network Balancing must be configured for the following clusters:

Cluster A , Cluster B, Cluster C

The Public IP Address of Network Load Balance Service is: 192.168.0.140

Now,

1- The Users will connect to the servers using NBL of IP: 192.168.0.140

2- The load on each server could be balanced because of NBL Balance.

3- NBL will handle redirecting user's requests to the Clusters.

4- All Clusters are using same Shared Disks that means all are using same databases location.

5- We'll have only one problem or doubt which is does SQL Server installer overwrite the configuration of other clusters?

This is a question.

Does anyone has faced same scenario? or has any correction ?

I am just thinking and would like to share my thoughts