I am a little confused on what is exactly needed to cluster SQL 2000 on a
windows 2003 cluster.  Does anyone have a link or a doc to the actual
step-by-step instructions for this procedure?
Thanks in advance

I have a Windows 2003 Enterprise Ed. server running SQL 2000 Enterprise Ed.
with  SCSI attached storage.  I have a new server (identical hardware), HP
fiber switches, etc to build a SAN config with the existing storage.  I can
build the SAN portion fine, but I don't know how to ...

I have an active/passive SQL 2000 SP3 cluster with a default instance
attached to a SAN. The SAN data is replicated to a contingency site. On the
contingency site I have a single node cluster. I intend to create a virtual
server on the contingency site with the same name as the ...

I have installed 16 gigs of ram in 2 servers that each house a virtual
server\instance of SQL.
I have the /3gb sw and the /pae switch in the boot.ini and before
failing over the group i ran the following script:

In Rodney R. Fournier's blog it states:
"If MSDTC is used with SQL, you should ensure it is in it's own group,
on it's own disk resource. Lastly, Microsoft recommends to run the
MSDTC & SQL group on the same node, and that the MSDTC is brought

I have a 2 node SQL 2000 clister running on Windows Server 2003. SQL is
patched to SP 3a.
Both the cluster service and SQL service use domain account to start up. The
domain accounts as members of the local admin group on both cluster nodes.

Did anyone implement  Active/Active cluster configuration in MS
Virtual Server 2005 env? I successfully completed it for
Active/Passive configuration.

I was hoping to clear up a few points of confusion regarding share-nothing
clustering...
My experience with clustering is that it is meant to address high
availability needs.  However, with share-nothing clustering you seem to be

We are going down the road of configuring our server per:
KB: "You receive error messages when you perform a distributed
transaction when you have a SQL Server 2000 virtual server in a Windows
Server 2003 clustered environment"

Please Help
I have spent 2 full days trying to install SQL Server 2000 Failover
Clustering on a MS Windows 2003 Enterprise Edition Server, but the
installation will not start the SQL cluster resources and complete.

Necesito montar la infraestructura para un portal, que estará
desarrollado con ASP contra SQL Server. El sistema ha de ser
redundante y a poder ser escalable.
Para ello habia pensado en el siguiente esquema :

What is the best way to set up a 2 node cluster for SQL server? We are
just beginning and a couple of the apps. One that used DFS and one
that mapped a drive were complaining about the clustered environment.

Normally, clustering is setup as a 1-to-1 relationship between active and
passive nodes, at least that is my understanding. We have a situation where
we are being asked to setup a 2 active node, 1 passive node environment.
Here's the question - if one of the active nodes fails, it ...

Is it possible to set up a 4 node cluster with 3 sql instances using
SQL2005 Standard edition.
I understand that SQL 2005 will only support two node clustering
(failover) under standard edition so what I plan to do is:

All,
We're currently running Veritas Storage Foundation HA 4.1 for Windows with
Veritas Cluster Server Enterprise Agent for SQL.
This is a 2 node cluster running 2 SQL instances