Loss of Server

I'm not sure if this is a Windows issue or a SQL Server in a cluster issue,
but it's strange.
We have a Windows 2003 Server Enterprise w/SP2 Running in a cluster. The
only thing on these servers is SQL Server. It's behind a firewall with only
the SQL ports open.
The problem we are running into is that from time to time, the primary node
in the SQL Cluster become unresponsive to the public NIC and the heartbeat
NIC and it doesn't failover. You can't RDP to it and the Cluster
administrator doesn't pick it up. You can't even ping the primary or
heartbeat from the passive node. It's like it is just not there.
There is a monitor NIC on this server as well, and they are throwing NO
alarms.
After about 20 minutes, it comes back.
Should this go to the Cluster group? Any suggestions?I would suggest taking it to the Windows Cluster group. I believe SQL runs
on top of the Cluster service, so.
"Kevin A" <kevina@.cqlcorp.com> wrote in message
news:Oo9HQ5FiIHA.4468@.TK2MSFTNGP03.phx.gbl...
> I'm not sure if this is a Windows issue or a SQL Server in a cluster
> issue, but it's strange.
> We have a Windows 2003 Server Enterprise w/SP2 Running in a cluster. The
> only thing on these servers is SQL Server. It's behind a firewall with
> only the SQL ports open.
> The problem we are running into is that from time to time, the primary
> node in the SQL Cluster become unresponsive to the public NIC and the
> heartbeat NIC and it doesn't failover. You can't RDP to it and the
> Cluster administrator doesn't pick it up. You can't even ping the primary
> or heartbeat from the passive node. It's like it is just not there.
> There is a monitor NIC on this server as well, and they are throwing NO
> alarms.
> After about 20 minutes, it comes back.
> Should this go to the Cluster group? Any suggestions?
>

Loopback adapter

I am running Windows XP and have SQL Server 2005 Enterprise Edition that I use for testing on my notebook. I want to install Oralce 11g on it as well and use VS 2005 as a front end programming. For me to install Oracle I need to install a loopback adapter. If I do this will it mess up SQL Server 2005 or will it not affect SQL Server 2005? Please advise

Hi,

Do you mean you want to install Microsoft Loopback Adapter on your Windows XP machine?

The Microsoft Loopback adapter is a testing tool for a virtual network environment where network access is not available. It will not affect the Microsoft SQLServer2005.

For more information on installation, see:
http://support.microsoft.com/kb/839013/en-us

Thanks.

Looooong Delays Connecting with Enterprise Mgr

Ever since upgrading to SQL Server 2000, connecting to the DB servers with
Enterprise Manager results in multi-minute delays while the database list
populates.
Is there something that can be done to make the connection process faster?Hi,
I think this will be the problem with one machine. Can you try with a
diffrent PC incase if it is faster then you can,
1. backup the OS login profile you are using
2. Delete the profile
3. Restore the profile back.
I had the same problem before and got solved after performing the above
steps.
Thanks
Hari
MCDBA
"R.MacLean" <zzz@.nospam.com> wrote in message
news:WSq2c.29720$aZ3.25484@.fed1read04...
> Ever since upgrading to SQL Server 2000, connecting to the DB servers with
> Enterprise Manager results in multi-minute delays while the database list
> populates.
> Is there something that can be done to make the connection process faster?
>|||Check the version of SQL 2000 that you are running. Verify that the
problem still occurs with SQL sp3a installed.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||I have two machines here that connect to 8 different SQL Server machines.
No real difference between them -- looong delays after clicking to open the
Databases folder after connecting, regardless of which client machine or
which server I'm connecting to.
(I think I was able to reduce the delay connecting to one of the local
servers by taking most of the DBs offline.)
I suspect that SQL Server 2000 returns the stats for ALL of the DBs upon
opening the Databases folder, where SQL Server 7 didn't return the stats for
ANY of the DBs until you attempted to open the DB. 2000 lets you click
around between DBs more quickly after the DB info is returned, but this is
far inferior to the older system.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:OBrnvP$AEHA.212@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I think this will be the problem with one machine. Can you try with a
> diffrent PC incase if it is faster then you can,
> 1. backup the OS login profile you are using
> 2. Delete the profile
> 3. Restore the profile back.
> I had the same problem before and got solved after performing the above
> steps.
> Thanks
> Hari
> MCDBA
>
> "R.MacLean" <zzz@.nospam.com> wrote in message
> news:WSq2c.29720$aZ3.25484@.fed1read04...
with
list
faster?
>