GetIsClustered() returns FALSE for Veritas Cluster Server

With both SQL Server 2000 and SQL Server 2005 when running in a Veritas Cluster, the GetIsClustered() API returns FALSE.

Does anyone know if this is working as designed?

Does GetIsClustered() really only mean MSCS clustered or should Veritas be setting that server property?

Thanks

Del Hoobler

Posting the last email thread that we had on the topic.

From: Michiel Wories
Sent: Monday, January 09, 2006 10:34 PM
To: 'Del Hoobler'
Cc: Mark Wistrom
Subject: RE: SQL Server 2005 - "IsClustered" - Is it just for MSCS?

Hi Del, as it seems Veritas clusters do not express their ‘cluster-ness’ through this serverproperty, so you would need to check with them how this is done. This is specific to their implementation so I am afraid I cannot help you with that.

Thanks,

Michiel

From: Del Hoobler
Sent: Monday, January 09, 2006 6:52 PM
To: Michiel Wories
Cc: Mark Wistrom
Subject: RE: SQL Server 2005 - "IsClustered" - Is it just for MSCS?

Hi Michiel,
Yes... this is what gets called for GetIsClustered(): (Here is the profile snippet):
14:29.9 select convert(int, serverproperty(N'isclustered'))
14:29.9 select convert(int, serverproperty(N'isclustered'))
14:29.9 select convert(int, serverproperty(N'isclustered'))
But... it sounds like what Mark is saying is that this field only pertains to MSCS... and we need
another way to determine if the server is clustered. Do you agree?

Thanks,
Del

Get server\instance name(s) using Physical node name

All:
Short of breaking out the cluster administator tool (GUI), given a
serversnetbios or DNS name, how can I deduce the SQL server names (and
instances) that may be present on that server. Ideally, I could pass
something into a VBSCRIPT function, and get the desired information,
but at this point, even just passing something at the command line that
is parsable would be useful.
Long version of the story is I have a list of 250 servers, but the
physical server name does not always map well to the SQL name,
especailly when instances are involved.
Does this make sense?
thanks,
d.
Look up the SQM-DMO method ListAvailableSQLServers in BOL. You can take
that and filter by InstanceName and ServiceName properties.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<google@.dcbarry.com> wrote in message
news:1141177148.783918.95800@.v46g2000cwv.googlegro ups.com...
> All:
> Short of breaking out the cluster administator tool (GUI), given a
> serversnetbios or DNS name, how can I deduce the SQL server names (and
> instances) that may be present on that server. Ideally, I could pass
> something into a VBSCRIPT function, and get the desired information,
> but at this point, even just passing something at the command line that
> is parsable would be useful.
>
> Long version of the story is I have a list of 250 servers, but the
> physical server name does not always map well to the SQL name,
> especailly when instances are involved.
>
> Does this make sense?
> thanks,
> d.
>
|||You may find SQLPing.exe by Chip Andrews perfect for this. It talks to UDP
1434 or SQL Browser, but you only need to supply a NetBIOS name, a DNS name,
or even an IP address. It'll return all the SQL Server instance names along
with a few other things. This is a very simple program with C# source code
you can compile yourself.
Google SQLPing.exe, and you'll find it.
Linchi
"google@.dcbarry.com" wrote:

> All:
> Short of breaking out the cluster administator tool (GUI), given a
> serversnetbios or DNS name, how can I deduce the SQL server names (and
> instances) that may be present on that server. Ideally, I could pass
> something into a VBSCRIPT function, and get the desired information,
> but at this point, even just passing something at the command line that
> is parsable would be useful.
>
> Long version of the story is I have a list of 250 servers, but the
> physical server name does not always map well to the SQL name,
> especailly when instances are involved.
>
> Does this make sense?
> thanks,
> d.
>