Our failover SQL cluster is a two-node single instance environment - SQL 2000
Enterprise SP4 on Windows Server 2003 Enterprise.  We're currently using NIC
teaming to give us some hardware redundancy since the blade has two Broadcom
NICs on it: one for the hearbeat private network ...

I'm trying to register the server in Management Studio and I can't
connect to the 2nd instance on the cluster.  I'm using the virtual IP of the
instance and even throwing in the instance name.
Tried:

We have updated multiple instances of sql server 2k5 EE to SP1 and oddly
enough some of them still show that they are at
RTM version 9.00.1399.06 instead of 9.00.2156.00. when checking through ssms
and select @@version

I seem to be at loggerheards with a member of our TA community. We have a 2
node cluster that doesn't have exact hardware. I've quoted the MS stance (see
below) but he seems adament it's not an issue.
Both servers will form a 2 node SQL cluster, both same spec but the 2nd node

We had a system that ran very well as an individual server.  With a
need to ensure uptime, though, we moved to an active-passive
clustering solution.  Now, we've noticed that the SQL Server instance
running on the cluster is slower than the old, single server.  How

Quick question.
Running Windows 2003 Enterprise SP1 and SQL Server 2000 Enterprise Sp4+.
Using clustering, I have my SAN drives for the Data and log and those
transfer just fine.  However, on each NODE, i have another 240GB that I want

I am new to MS SQL and would like to break a SQL Server 2000 cluster and leave the database in tact.  I have 2 HP DL380's with an HP StorageWorks SAS device.  I need to use one of the servers and the SAS device for High Availability with VMWare.  Can some one tell me what is the ...

In a nutshell, all I want to know is:
On an active/passive cluster (2003 enterprise)
Should I install one SQL 2000 enterprise as a virtual and the 2nd as an
Instance, or can I install both as Virtuals?  (Each having it's own name and

I created a single node SQL 2000 cluster for testing purposes on
Windows 2003 SP1 box.   In time, the application folks wanted to test
failover and requested a failover node.  I added the failover node to
the cluster group and to the SQL cluster.  I verified failover to the

I have a question concerning clustering SQL 2005. Let's say that you
installed SQL Server 2005 on a machine with no clustering and you want to
enable clustering do you have to reinstalled SQL server completely?
Thanks

We have a two-node active/active sql cluster (sql 2005 and windows 2003 EE
64bit), and we configured MSDTC in one resource group running on one node. It
seems that only the SQL instance that is running on the same node which MSDTC
is running can use distributed transactions. Is ...

If I change cluster failover/failback settings will that affect any current
running services?  Specifically I want to change the resource setting to "Do
not Restart".  If I change that will it affect the currently running SQL
services?  I don't want to initiate the restart of any ...

Just about to set up SQL 2005 cluster. Do I need to set up Windows cluster
environment, then set up SQL 2005 cluster?
Thank you

I have a few shares setup on my SQL 2005 Cluster and when a user tries to
connect to a share I get an error message. Has anyone seen this I have
changed the registry setting to 15 but I am still getting the error message.  
The KB225782 says this fix applies to NT 4.0 not Windows ...

Microsoft said that not recommend that the Integration Services service be
configured as a cluster resource.
(http://msdn2.microsoft.com/en-us/library/ms345193.aspx)
What is the recomended configuration to have Integration Services in a high