Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 Check BIOS Name - (not @@SERVER)

Author  Topic 

Analyzer
Posting Yak Master

115 Posts

Posted - 2007-08-08 : 11:34:53
I support numerous cluster SQL boxes and as part of my daily DBA Check regime I need to know whether the instances have faulted and switched the to other side of the cluster.

Since not all fault's which are recorded in the event logs result in the instance failing over to the other side of the cluster, and the SQL instance thinks it exists on the virtual name, this can make it difficult to indentify which server SQL resides on using just SSMS.

Does anyone know a T-SQL command to discover the BIOS name -alternatively and recommendations how I check this parameter?

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-08-08 : 13:36:24
Tried xp_cmdshell 'hostname'?
Go to Top of Page

eyechart
Master Smack Fu Yak Hacker

3575 Posts

Posted - 2007-08-08 : 14:28:57
failovers are recorded in the event log though. If you have a means of monitoring the event log then you should be able to pick that up.

There was a thread along these same lines a couple weeks back that you might want to take a look at with suggestions for how to alert when a failover occurs. I'll see if I can locate it.



-ec
Go to Top of Page

eyechart
Master Smack Fu Yak Hacker

3575 Posts

Posted - 2007-08-08 : 14:30:13
here is the other thread I referred to http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=86965

that might be another approach to take instead of checking the BIOS name of the server an instance is running on.



-ec
Go to Top of Page

Analyzer
Posting Yak Master

115 Posts

Posted - 2007-08-09 : 04:38:15
Thanks guys - xp_cmdshell 'hostname' is a good idea, however on our system when tested in SSMS it still returns the virtual name and not the bios?

We do monitor the event logs however a caveat with this solution is we use Symantec VCS cluster software which can fault when under great stress, stop the SS service which drops the stressed resource. i.e CPU, then poles for the next available instance which can be the same server the starts the SS service. So faults, service start-up events can be monitored and notifications setup, I'll test to see whether notifications contain the virtual or bios name.
Go to Top of Page

Analyzer
Posting Yak Master

115 Posts

Posted - 2007-08-09 : 09:47:12
xp_cmdshell 'ping <virtual_name>' works!
Go to Top of Page
   

- Advertisement -