Whilst Installing "SQL Server Health and History Tool" the Installation failed when trying to create the scheduled job
I have run SQLH2 /DDMY (as I am in the UK) and the entries are entered into the database (I think that this is the job that should be scheduled ???)
I then installed the Performance Collector and started the service.....
The text file is being added to every 120 seconds..
The Questions are
1) Am I correct that the scheduled task should be SQLH2 /DDMY ?
2) How do I get the data from the Performance collector into the Database ?
I can't get performance collector to work and am hoping that microsoft are going to send me a beta release which fixes the locale problem.
Additionally the sqlh2 /DDMY will only collect the performance files once a file is closed. A file is closed either when the performance collector is restarted or a file becomes full (1 mb).
OK Now things are becoming clearer
SQLH2 is not real time monitoring as the performance files are not added to the database. (not a problem)
D:\SQLH2\Sqlh2 /DDMY is scheduled to upload the Perf files (How often is this scheduled??) ... does this also collect the other server data? (H/W, NIC, Disk e.t.c)
I ran SQLH2 and the Perf File was Removed...
The Following log entry was created
I Cannot Find any entries for the perf Data but it looks as though the data has been transfered into the database... Where should I look to Check?
Thanks for the help
I will post this now as I have lost My train of thought
Strange that the Performance Collector needs to run under a profile set up for US Dates.... I will try this when I get A Moment
This is an extract from the file
</COUNTERS>,,,,1,5,1.362784E+09,3149,31/10/2004 01:19:151,6,5.213032E+09,3149,31/10/2004 01:19:151,7,0,3149,31/10/2004 01:19:151,8,761.5919,3149,31/10/2004 01:19:151,9,0,3149,31/10/2004 01:19:151,10,0,3149,31/10/2004 01:19:151,11,0.01346138,3149,31/10/2004 01:19:151,12,0,3149,31/10/2004 01:19:151,13,1.207687,3149,31/10/2004 01:19:151,14,0,3149,31/10/2004 01:19:151,15,5663.087,3149,31/10/2004 01:19:151,16,0.7548152,3149,31/10/2004 01:19:151,17,99.89107,3149,31/10/2004 01:19:151,18,0,3149,31/10/2004 01:19:151,19,226642,3149,31/10/2004 01:19:151,20,904008,3149,31/10/2004 01:19:151,21,988896,3149,31/10/2004 01:19:151,22,0.4330941,3149,31/10/2004 01:19:151,23,0.04997224,3149,31/10/2004 01:19:151,24,0,3149,31/10/2004 01:19:151,25,0.8994992,3149,31/10/2004 01:19:151,26,4701120,3149,31/10/2004 01:19:151,27,10,3149,31/10/2004 01:19:15
It looks as though the Data Is Being Collected.
The problem you are seeing is stemming from different date format settings.
On you PerfCollector machine it's DMY.
SQLH2 loads perf data using bcp. My guess is that default language for the SQLH2 account has different format. So loading fails.
You should either change default language for the account or wait for the next update, which may help to resolve the issue.
I have not tried anything for a few days. I will look at the issue in some more detail...
The question still remains as to how often the application is scheduled to run?
By default it's scheduled to run 2 times a week.
You can check it if you look at SQLH2 task using Cotrol Panel | Scheduled tasks
To work around this issue we have a perl script which changes data format from dd/mm/yyyy to mm/dd/yyyy in source file before upload to the database