First of all, thank all of you all for all your hard work that give us
folks light and guidance in what seems like a real dark room sometimes.
I have a single SQL server that I am looking to put into an
Active/Passive cluster. Unfortuantly, I have a truckload of

I need to design an architecture to support what will become a heavily
hit web site.  We have a UNIX guy looking after the web servers and it
is my job to sort out the SQL side.
The ratio of reads to writes in the database will probably be 75:25.

Can I setup two SQL 2005 clusters on a single Windows 2003 (4 nodes)
cluster? Or I need to setup 2 windows 2003 clusters? one for each SQL 2005
cluster

trying to resolve n MSDTC issue, on a clustered server, and I enabled
network access by
DCOMCNFG->MSDTC->Security configuration->network access ...
now I want to turn network access off, but the "security configuration"

I have 2 HP proliant DL 360's with G4P's running SQL 2000 in an active
passive configuration. My problem is that I also have 2 network load balanced
font end servers running on apache web server which are supposed to access
the SQL cluster but when they cant access the active node ...

This is what is happening:
Cluster service is running "Is Alive" check every 1 minute on SQL server
I validate this by profiling the SQL server and see that "select
@@servername" command being executed by cluster service every minute

Guys first of all I am lost I need some serious HELP>
What I want to do is create and Active/Active Clustering environment.
Using Windows 2003 and SQL2000
For Hard Ware I am using two DELL PowerEdge 2850 servers and a PowerVault

I have two SQL servers configured in a cluster and when the first server goes
down it wont fail over. For some reason the cluster believes that the first
server is still up and running and nothing is loged in the event viewer. Any
suggestions would be helpful at this point.

I have a SQL cluster consisting of the following:
   2 ea Dell PE-2850 servers, dual 3.2 GHz CPU, 4 GB RAM, 2-36 GB/RAID-1
for C:, same for D:, all drives U320/15K. running Win2K3EntSP1 and
SQL2K5SP1.  Connected to cluster with Dell PERC4/DC in each server

I am trying to convince "the powers that be" that we must cluster our test
environment if we are definitely clustering our production environment. The
question I need the community’s help with is: WHY?
Can you give me some hard facts as to why it is not recommend to cluster one

I nee to configure sending alerts thru email in SQL Server 2000.  This is a
clustered server which is not part of the domain.  Any hints on how to do it?
I've only done it in a non-clustered, Exchange-based scenario.

Is adding DTC as a resource to my cluster necessary or it is used for
particular purpose? My database does not perform any distributed query/xact.
Do I have to add DTC resource to the cluster?
Thanks in advance,

I setup the clustering test environment by the following specifications:
OS: Windows 2003 SP1 for both nodes
Hardware: Not in HCL
Storage: DAS, consisting of two SCSI disks, no RAID, one disk for Quorum,

I'm trying to set up an SQL Server 2000 cluster. I've set up two Windows 2003
Server's in cluster mode (with external storage device and this is working.
I've been working through MS Articles Q817604 and Q301600 which explains the
preperation steps before installing SQL Server ...

I have a clustered SQL Server 2000 running on Win2K3 and SAN.  We are
planning to move this to a new SAN.  Any step-by-step procedures to guide me?
Do I just copy the MSCS and MSDTC folders to the new SAN?