Collecting data from clustered servers

Nov 7, 2008 at 8:15 PM
We are having some difficulties with collecting data from our clustered environments.  Does SQLH2 support collecting data from clustered SQL instances?

For example, say we have a 2 node cluster (nodeA and nodeB).  And we have 3 SQL instances installed on this cluster under 3 different virtual hosts (SQL1, SQL2, SQL3 are the virtualhosts, \A, \B, \C are the named instances).  When we point the SQLH2 at the physical nodes, it finds that we have SQL instances named nodeA\A, nodeA\B, nodeA\C instead of SQL1\A, SQL2\B, SQL3\C.  Since the nodeA\A instance doesn't really exist we get errors.  Is there a way around this issue?   Thanks.


-js
Coordinator
Nov 12, 2008 at 6:12 AM
SQLH2 doesn't support clusters.
This is one of the reasons. It doesn't look up virtual names.
This one actually would be easy to add. There are other issues with clusters that are much harder.

Grigory




From: notifications@codeplex.com
To: gpogulsky@msn.com
Date: Fri, 7 Nov 2008 13:15:20 -0800
Subject: Collecting data from clustered servers [sqlh2:39461]


.ExternalClass {font-family:Verdana;font-size:0.75em;} .ExternalClass #EC_ThreadNotificationFooter {border-top:1px solid #ccc;color:gray;} .ExternalClass #EC_ThreadNotificationPostBody {margin-bottom:2em;} .ExternalClass {font-family:Verdana;font-size:0.75em;} .ExternalClass #EC_ThreadNotificationFooter {color:gray;border-top:1px solid #ccc;} .ExternalClass #EC_ThreadNotificationPostBody {margin-bottom:2em;} From: qcjamess
We are having some difficulties with collecting data from our clustered environments. Does SQLH2 support collecting data from clustered SQL instances?

For example, say we have a 2 node cluster (nodeA and nodeB). And we have 3 SQL instances installed on this cluster under 3 different virtual hosts (SQL1, SQL2, SQL3 are the virtualhosts, \A, \B, \C are the named instances). When we point the SQLH2 at the physical nodes, it finds that we have SQL instances named nodeA\A, nodeA\B, nodeA\C instead of SQL1\A, SQL2\B, SQL3\C. Since the nodeA\A instance doesn't really exist we get errors. Is there a way around this issue? Thanks.


-js
Read the full discussion online.
To add a post to this discussion, reply to this email (sqlh2@discussions.codeplex.com)
To start a new discussion for this project, email sqlh2@discussions.codeplex.com
You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.
Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com


See how Windows® connects the people, information, and fun that are part of your life Click here
Nov 13, 2008 at 2:37 AM
Edited Nov 13, 2008 at 2:41 AM
Is adding cluster support something that is being or will be worked on?  If we had basic support for SQL clusters (just the basic SQLand database info, not the hardware info) we would be very happy.

Also, what are the other cluster issues that you refer to?  Thanks.



-js
Coordinator
Nov 19, 2008 at 11:13 PM
The other issues with Clusters are basically related to the ability to understand that data collected from different machines belong to the same clustered instance.
It affect runtime data, for example. Whatever information you collect from logs, files, etc is unreliable. There is also duplication of data if you point to different nodes of the same cluster.
However collecting just SQL instance data should be ok.
Nobody is working on this at the moment. If there are volunteers here that would be a great improvement to add.
Dec 8, 2008 at 11:33 PM
we are testing some changes to make SQLH2 work with cluster environments and we are pretty close to getting this working. However, we are also running into the 64bit problem mentioned in the other discussion thread here. 

Once we fully test our cluster fix I will provide a diff.
Sep 29, 2009 at 11:01 AM

any news on SQLH2 working in a cluster environments?