Multi select queries against performance counters in WMI?

Other wise, you could use a UNION query as follows:

Set fmtProcColItems = objWMIService.ExecQuery( _
"SELECT IDProcess, PercentProcessorTime, PrivateBytes, HandleCount, NULL AS Win32_PerfFormattedData_PerfProc_Process FROM Win32_PerfFormattedData_PerfProc_Process
UNION
NULL AS IDProcess, NULL AS PercentProcessorTime,  NULL AS PrivateBytes, NULL AS HandleCount, NumberBytesinallHeaps FROM Win32_PerfFormattedData_NETFramework_NETCLRMemory WHERE Win32_PerfFormattedData_PerfProc_Process.Name LIKE 'Vertical.Wave.ViewPoint%' " &_
    "ANDWin32_PerfFormattedData_NETFramework_NETCLRMemory.Name LIKE 'Vertical.Wave.ViewPoint%'",,48)

Typo, my first post should read:


If IDProcess is a field common to the data for both performance counters, then it should just be a matter of changing the SQL query to join both queries (assuming that IDProcess is (1) common to both; and (2) the unique identifying key for the data);

e.g.


Set fmtProcColItems = objWMIService.ExecQuery( _
"SELECT WPP.IDProcess, WPP.PercentProcessorTime, WPP.PrivateBytes, WPP.HandleCount, WNC.NumberBytesinallHeaps FROM Win32_PerfFormattedData_PerfProc_Process AS WPP INNER JOIN Win32_PerfFormattedData_NETFramework_NETCLRMemory AS WNC ON WPP.IDProcess = WNC.IDProcess WHERE WPP.Name LIKE 'Vertical.Wave.ViewPoint%' " &_
    "AND WNC.Name LIKE 'Vertical.Wave.ViewPoint%'",,48)

Thanks, I'll try those out when I get back to work next week.

If possible, the first solution would be better; which relies on the common field IDProcess being available to both data sources.

Doesn't seem to work right. Or at least, I'm not processing the return data correctly. If you see from my original post, I posted a code sample of how I process the return data by iterating through the collection.

If I use the same iterating code from my original post with your suggested WMI queries, the output is an exception of:

(null): 0x80041017

and the error is found on the line that begins the iteration of the collection.

That kind of sounds like the query returned nothing?

Also I tried checking the return value, and it is an object, which I assume is a collection and trying to access the "Count" property fails as that isn't recognized. Just for the heck of it, I tried using UBound as if it was an array, and tried IsNull and IsEmpty. It fails with UBound, and is not null and not empty. So a side question is how to validate the returned data and/or how to dump its contents in this case since Count doesn't work and I can't iterate through the collection.

Did a search online for that type of error and results from search didn't help.

I wonder if WMI actually allows you to perform SQL queries that involve joins and unions? Or only basic SQL queries.

I found some basic code to do generic or any type of SQL queries for WMI content for .NET here:
http://www.gettingclever.com/2008/06/simple-wmi-client.html

I used that code as a starting point and modified it to also allow SQL injection of the parameters or data we want to retrieve rather than "select *" and thus perform the queiries suggested by fredthered.

The result from execution threw an exception of this type:

Unhandled Exception: System.Management.ManagementException: Invalid query
   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStat
us errorCode)
   at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.Mo
veNext()
   at DisplayInfo.Main(String[] args)

Basic SQL queries using that .NET code worked and did not return an exception. So it looks like somehow WMI doesn't like SQL joins and unions right?

Interesting that VBScript didn't return such an error, so instead you end up with a null object that is returned and when you iterate through that object you get the exception I mentioned in my earlier post.

Thanks for following up. I also posted to MS Scripting Guy's forum and someone responded that my assumption is correct that WMI does not support complex SQL queries. It only supports a subset, as defined by MS on this page:

WQL (SQL for WMI)
http://msdn.microsoft.com/en-us/library/aa394606(VS.85).aspx

So looks like I'll just have to do additional results processing to merge the data over two SQL queries as a result of this.

Thanks for your help.