SQL Server Performance

SQL Server Health and History Tool

Discussion in 'Forum Announcements' started by bradmcgehee, Aug 3, 2004.

  1. bradmcgehee New Member

    Free download at:

    http://www.microsoft.com/downloads/...763-86de-d2347b8b5f89&displaylang=en#filelist


    The Microsoft SQL Server Health and History Tool (SQLH2) allows you to collect information from instances of SQL Server, store this information, and run reports against the data in order to determine how SQL Server is being used.

    -----------------------------
    Brad M. McGehee, MVP
    Webmaster
    SQL-Server-Performance.Com
  2. Argyle New Member

    Now this is a nice tool. It seems to top any custom scripts I currently run, time to test. To bad it doesn't support clustered instances though.
  3. satya Moderator

    It crashed when try to deploy on one of the production server, so back to old drawing board. And until it has been tested on the development platform I cannot deploy on the live services.

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  4. Argyle New Member

    Same here on my testbox. Got this in the log:


    2004-08-03 17:10:47 Opening Log
    2004-08-03 17:10:47 SQLH2 ver. V2 2.0.023.0 7/09/04 10:49
    2004-08-03 17:10:47 Status: Init
    2004-08-03 17:10:48 WARNING: There are no PerfProviders in the config file
    2004-08-03 17:10:48 Status: Initializing repository: (local)
    2004-08-03 17:10:48 Status: Repository Database: SQLH2Repository
    2004-08-03 17:10:48 INFO: host_id = 1
    2004-08-03 17:10:48 Status: Starting RUN
    2004-08-03 17:10:48 Status: Registering Run
    2004-08-03 17:10:48 INFO: run_id = 1
    2004-08-03 17:10:48 Status: Starting Targets processing
    2004-08-03 17:10:48 Status: Initializing Target: TEST01
    2004-08-03 17:10:48 Status: registering Server
    2004-08-03 17:10:48 INFO: srv_id = 1; signature = d86ac94e-e741-4fbf-a473-48474c2c5ab7
    2004-08-03 17:10:48 Status: Scanning Registry on TEST01
    2004-08-03 17:10:48 Status: registering instance TEST01
    2004-08-03 17:10:48 INFO: inst_id = 1
    2004-08-03 17:10:48 INFO: version: 8.00.818
    2004-08-03 17:10:48 Status: RUN
    2004-08-03 17:10:48 Status: Initializing collector: WMI
    2004-08-03 17:10:48 Status: Running WMI collector
    2004-08-03 17:10:48 Status: Opening Unit 1 (OS/CS)
    2004-08-03 17:10:48 Status: Collecting Win32_OperatingSystem
    2004-08-03 17:10:49 Status: Collecting Win32_ComputerSystem
    2004-08-03 17:10:49 Status: Collecting Win32_Processor
    2004-08-03 17:10:50 ERROR: Line 1: Incorrect syntax near 'd'.
    2004-08-03 17:10:51 Status: Closing Unit 1
    ...
    2004-08-03 17:10:51 WARNING: WMI Collector encountered critical error. Abandoning Collector.
    ...
    2004-08-03 17:10:51 ERROR: TEST01: Collection failed; Error:104; Provider Error: 170
    2004-08-03 17:10:51 ERROR: Critical Repository Failure
    2004-08-03 17:10:51 SQLH2 is shutting down
    2004-08-03 17:10:51 Closing Log

    Too bad, looked like a nice tool otherwise.
  5. satya Moderator

    Seems similar set of events in our log too, I referred the case to local MS Support for resolution.
    I will post once I've the details.

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  6. grigoryp New Member

  7. satya Moderator

    I missed to post the update fix, thanks for your addup Grigoryp.

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  8. ykchakri New Member

    I've downloaded and installed it. Now, how to start collecting information ? I've tried by executing sqlh2.exe and it fails with an error "Application has generated an exception that could not be handled".

    Also, how to view the collected data. Do we have to have reporting services installed ?
  9. satya Moderator

    Try to uninstall and reinstall freshly, it looks like mismatch of few DLLs.
    On the above provided link, it refer:
    Note that SQLH2 requires you to create a SQL Server repository database. You should also download the SQLH2 reports to view the data SQLH2 collects. If you are interested in performance data, download and install the SQLH2 Performance Collector at the link provided on this page.

    If you have questions or comments on the tool, email sqlh2@microsoft.com.

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  10. ykchakri New Member

    Well, I finally had to run the collector from the same machine as the repository is on. For some reason I can't run collector from a different machine (may be an authentication issue).

    And it looks like I have to have reporting services installed to view SQLH2 reports.
  11. Oliwa19 New Member

    quote:Originally posted by ykchakri

    Well, I finally had to run the collector from the same machine as the repository is on. For some reason I can't run collector from a different machine (may be an authentication issue).

    And it looks like I have to have reporting services installed to view SQLH2 reports.

    I was running into an issue collecting QFE events from a remote server and discovered the field lengths are too short. I did a trace and found the culprits. I changed the schema to a bigger datatype and I can now capture remote data.
  12. grigoryp New Member

    Justr curious what was the QFE that caused the error?
    Was it for Shavlik component?
  13. tapmrp1 New Member

    Currently I am running Pref collector on three servers. Looks like it is collecting the perf data in text files on all servers. When I am tring to run SQLH2 so that it will put perf data into repository, but I am getting following error on Perf counter loader

    12/20/2004 11:19:50 AM Status: Starting Perf Loader
    12/20/2004 11:19:50 AM INFO: Perf host_id = 2
    12/20/2004 11:19:50 AM INFO: Lock aquired: pid = 1
    12/20/2004 11:19:50 AM INFO: Lock released: pid = 1
    12/20/2004 11:19:50 AM INFO: Perf host_id = 3
    12/20/2004 11:19:50 AM INFO: Lock aquired: pid = 1
    12/20/2004 11:19:51 AM ERROR: The network path was not found.

    12/20/2004 11:19:51 AM INFO: Perf host_id = 4
    12/20/2004 11:19:51 AM INFO: Lock aquired: pid = 1
    12/20/2004 11:19:51 AM ERROR: The network path was not found.

    12/20/2004 11:19:51 AM WARNING: Errors were encountered processing PerfProviders
    12/20/2004 11:19:51 AM Status: Perf Loader finished

    How I can fix the above error.

    Thanks for your help in advance.
  14. satya Moderator

    Try to unload and load the PERFMON counters using LODCTR program.

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  15. nanonull New Member


    I am having the same issue with the perfprovider name. Does it take an UNC path? \serversql$ ? I keep getting the same network error

    1/13/2005 2:42:28 PM Status: Targets processing finished
    1/13/2005 2:42:28 PM Status: Starting Perf Loader
    1/13/2005 2:42:28 PM ERROR: The network path was not found.

    1/13/2005 2:42:28 PM WARNING: Errors were encountered processing PerfProviders
    1/13/2005 2:42:28 PM Status: Perf Loader finished


    please help
  16. satya Moderator

    May be the health history tool cannot access the network files.

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  17. grigoryp New Member

    <blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by nanonull</i><br /><br /><br />I am having the same issue with the perfprovider name. Does it take an UNC path? \serversql$ ? I keep getting the same network error<br /><br />1/13/2005 2:42:28 PM ERROR: The network path was not found.<br /><br /><hr height="1" noshade id="quote"></font id="quote"></blockquote id="quote"><br /><br />PerfProvider name is the name of the machine where PerfCollector is running. It is not the name of the machine you are collecting perfdata from. Let's say you have PErfCollector running on "server_A", collecting from "server_B" and "server_C". Names server_B and server_C will only be mentioned in H2PerfConfigFile.xml (which is PerfCollector configuration file).<br />In your SQLH2 configuration file (H2Config.xml) you will have the following<br /> &lt<img src='/community/emoticons/emotion-4.gif' alt=';P' />ERF_PROVIDERS&gt;&lt<img src='/community/emoticons/emotion-4.gif' alt=';P' />ERF_COLLECTOR Name="server_A" /&gt;&lt;/PERF_PROVIDERS&gt;<br />If SQLH2 is running on the different machine (let's say "server_X") you have to create a share SQLH2PerfCollectorData$ according to "SQLH2 V2 Performance Collector Deployment Guide". <br />Please write to sqlh2@microsoft.com if you need help configuring/troubleshooting you Perf collection.<br />

Share This Page