Any experience with v.2.2.001?

May 4, 2010 at 6:41 PM

I'm looking for feedback on this version.

If nobody is hitting any issues, we would like to promote it to be the 'default' version (probably in June).

Jun 1, 2010 at 10:14 PM

I just started it on my evaluation box and it is not finding x64 based SQL Server 2005 instances.

It returns the error "No SQL Server instances registered on the box"

So, it is no different than the 32-bit version (available) by MS.

Do you have a software prerequisite listing.

The server I am running this on is 32-bit and some sources of data are 32-bit, but most are x64.

I only have 4 SQL Server 2000 instances (all 32bit) the rest are 32bit and x64 bit SQL Server 2005. I have not tried any version of SQL 2008 yet.

Jul 14, 2010 at 7:46 PM

Just a final update.

For those of you who need to monitor 32-bit and 64-bit versions of SQL Server, you will need 2 clients (1 for each). When you reference the repository, you can reference the same one and they will poll against the instances just fine.

As long as everyone that uses this version is aware of this minor limitation, I recommend that this be made the 'default' version.

Disclaimer: This does not impact my recommendation, however, you need to know that policies at my employer does not permit me to push this version into our production world with it being in beta-status.  So we will not be fully deploying this until it is available as the 'default' version.


Oct 8, 2010 at 1:06 AM

v.2.2.001 now is a recommended release

Dec 22, 2010 at 8:26 PM

I have been using SQLH2 since first release and now try to run it against SQL 2008 servers. I am running v.2.2.001 and have strange issue with SQL Servers 2008 R2 (64 bit). I downloaded debug version and an error is below. Note, that it collects SQL Server information, but not OS or Hardware information. The strange part of it that it runs perfect against identical server (OS, SQL Server) which is on VM server and gives me this error when I run the tool for the physical servers:

12/22/2010 12:54:32 PM   
12/22/2010 12:54:32 PM   Opening Log
12/22/2010 12:54:32 PM   SQLH2  ver. 4/12/2010 9:47:06 AM
12/22/2010 12:54:32 PM  Status:  Init
12/22/2010 12:54:32 PM  WARNING:  There are no PerfProviders in the config file
12/22/2010 12:54:32 PM  Status:   Initializing repository: xxxxx
12/22/2010 12:54:32 PM  Status:   Repository Database: SQLH2Repository
 DEBUG:  The .Net SqlClient Data Provider has received a severity 0, state 1 message 5701 on server xxxxx: Changed database context to 'SQLH2Repository'.
12/22/2010 12:54:32 PM  INFO:  host_id = 5
12/22/2010 12:54:32 PM  Status:  Starting RUN 
12/22/2010 12:54:32 PM  Status:  Registering Run
12/22/2010 12:54:32 PM  INFO:  run_id = 26
12/22/2010 12:54:32 PM  Status:  Starting Targets processing 
12/22/2010 12:54:32 PM  Status:  Initializing Target: xxxxx1
12/22/2010 12:54:32 PM  Status:    registering Server
12/22/2010 12:54:32 PM  INFO:  srv_id = 11; signature = a7af3d15-8c84-456e-89c5-f2c8b4173198
12/22/2010 12:54:32 PM  Status:  Scanning Registry on xxxxx1
12/22/2010 12:54:32 PM  Status:    registering instance xxxxx1
12/22/2010 12:54:32 PM  INFO:  inst_id = 1
12/22/2010 12:54:32 PM  INFO:  version: 10.50.1746.0
12/22/2010 12:54:33 PM  Status:    RUN 
12/22/2010 12:54:33 PM  Status:   Initializing collector: WMI
12/22/2010 12:54:33 PM  Status:  Running WMI collector
12/22/2010 12:54:33 PM  Status:   Opening Unit 1 (OS/CS)
12/22/2010 12:54:33 PM  Status:    Collecting Win32_OperatingSystem
12/22/2010 12:54:33 PM  Status:    Collecting Win32_ComputerSystem
12/22/2010 12:54:33 PM  Status:    Collecting Win32_Processor
   at H2V2.Collector.CollectorWmi.StoreProcessor(ManagementObject a_mo) in D:\Documents\Development\SQLH2\H2Collector\Collector_WMI.cs:line 635
   at H2V2.Collector.CollectorWmi.StoreWmi(UInt32 a_type, ManagementObject a_mo) in D:\Documents\Development\SQLH2\H2Collector\Collector_WMI.cs:line 429
   at H2V2.Collector.CollectorBase.CollectWmi(String a_scope, String a_query, UInt32 a_type) in D:\Documents\Development\SQLH2\H2Collector\Collector.cs:line 213
12/22/2010 12:54:35 PM  Status:   Closing Unit 1
12/22/2010 12:54:35 PM  ERROR:    Object reference not set to an instance of an object.
12/22/2010 12:54:35 PM  WARNING:    WMI Collector encountered critical error. Abandoning Collector.

Not sure if this matters, but I don't have D:\Documents\Development\SQLH2\H2Collector directory.

Dec 22, 2010 at 8:47 PM

This looks like an unexpected data with the WMI. I would verify that the account doing the calls to WMI have full rights (i.e. member of the Local Administrator group) or allowed privleges setup in security to make sure you are not having a security issue.  My opinion is that the version of SQL Server should not be an issue since the error you provide is a WMI call.

However, we are not running againts SQL 2008 R2 (Don't ask why, it will take a lot of medication to understand). We have been running in a testing mode for sometime. We are running SQL Server 2005 SP3 with CU9 and SQL Server 2008 SP1 without any problems.

We expect to deploy to production by the end of January.

Sorry I could not advise much further than that


Jun 26, 2011 at 10:33 AM

It seems that the *_qfe tables are not populated.

The related section in the log is not stating an error:

25.06.2011 19:34:56     Status:      Opening Unit 4 (Hotfixes)
25.06.2011 19:34:56     Status:       Collecting Hotfix Registry
25.06.2011 19:34:56     Status:      Closing Unit 4

I am running Windows 7 x64 english and SQL 2008 R2 x64 english with default german locale settings.