SQLH2 Performance Collector
-
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 ?
Regards
Andy
-
Yes, the scheduled task should include the /D option.
You'll need to run the PerformanceCollector service under an account that is setup for US dates (MS are working on fixing this). To get the performance data into the database, add the name of the machine that the service is runnign on into the PerfProviders box using the Config Utility.
--------------------
Colt 45 - the original point and click interface
-
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).
Elaine
-
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
28/10/2004 10:03:2928/10/2004 10:03:29 Opening Log
28/10/2004 10:03:29 SQLH2 ver. V2 2.0.024.0 9/30/04 17:58
28/10/2004 10:03:29 INFO: The following command line arguments were supplied: /DDMY
28/10/2004 10:03:29 Status: Init
28/10/2004 10:03:29 Status: Initializing repository: (local)
28/10/2004 10:03:30 Status: Repository Database: SQLH2Repository
28/10/2004 10:03:30 INFO: host_id = 3
28/10/2004 10:03:30 Status: Starting RUN
28/10/2004 10:03:30 Status: Registering Run
28/10/2004 10:03:30 INFO: run_id = 14
28/10/2004 10:03:30 Status: Starting Targets processing
28/10/2004 10:03:30 Status: Initializing Target: DEV-SQL
28/10/2004 10:03:30 Status: registering Server
28/10/2004 10:03:30 INFO: srv_id = 1; signature = 9b0d433d-4169-44ec-9340-181606c93232
28/10/2004 10:03:30 Status: Scanning Registry on DEV-SQL
28/10/2004 10:03:30 Status: registering instance DEV-SQL
28/10/2004 10:03:30 INFO: inst_id = 1
28/10/2004 10:03:30 INFO: version: 8.00.760
28/10/2004 10:03:30 Status: RUN
28/10/2004 10:03:30 Status: Initializing collector: WMI
28/10/2004 10:03:30 Status: Running WMI collector
28/10/2004 10:03:30 Status: Opening Unit 1 (OS/CS)
28/10/2004 10:03:30 Status: Collecting Win32_OperatingSystem
28/10/2004 10:03:32 Status: Collecting Win32_ComputerSystem
28/10/2004 10:03:33 Status: Collecting Win32_Processor
28/10/2004 10:03:35 Status: Closing Unit 1
28/10/2004 10:03:35 Status: Opening Unit 2 (NIC)
28/10/2004 10:03:35 Status: Collecting Win32_NetworkAdapter
28/10/2004 10:03:36 Status: Collecting Win32_NetworkAdapterConfiguration
28/10/2004 10:03:36 Status: Closing Unit 2
28/10/2004 10:03:36 Status: Opening Unit 3 (Disk)
28/10/2004 10:03:36 Status: Collecting Win32_DiskDrive
28/10/2004 10:03:36 Status: Closing Unit 3
28/10/2004 10:03:36 Status: Opening Unit 4 (QFEs)
28/10/2004 10:03:36 Status: Collecting QFE registry
28/10/2004 10:03:36 Status: Closing Unit 4
28/10/2004 10:03:36 Status: Opening Unit 5 (EventLog files)
28/10/2004 10:03:36 Status: Collecting Win32_NTEventlogFile
28/10/2004 10:03:37 Status: Closing Unit 5
28/10/2004 10:03:37 Status: Opening Unit 6 (Processes)
28/10/2004 10:03:37 Status: Collecting Win32_Process
28/10/2004 10:03:37 Status: Closing Unit 6
28/10/2004 10:03:37 Status: Opening Unit 7 (Products)
28/10/2004 10:03:37 Status: Collecting Win32_Product
28/10/2004 10:03:40 Status: Closing Unit 7
28/10/2004 10:03:40 Status: Opening Unit 8 (Services)
28/10/2004 10:03:40 Status: Collecting Win32_Service
28/10/2004 10:03:42 Status: Closing Unit 8
28/10/2004 10:03:42 Status: Initializing collector: EventLog
28/10/2004 10:03:42 Status: Initializing collector: SQL
28/10/2004 10:03:42 Status: Running SQL collector on DEV-SQL
28/10/2004 10:03:42 Status: Opening Unit 5 (Server Properties)
28/10/2004 10:03:42 Status: Closing Unit 5
28/10/2004 10:03:42 Status: Opening Unit 1 (Databases)
28/10/2004 10:03:48 Status: Closing Unit 1
28/10/2004 10:03:48 Status: Opening Unit 2 (Current Configuration)
28/10/2004 10:03:48 Status: Closing Unit 2
28/10/2004 10:03:48 Status: Opening Unit 3 (Running traces)
28/10/2004 10:03:48 Status: Closing Unit 3
28/10/2004 10:03:48 Status: Opening Unit 4 (Registry)
28/10/2004 10:03:48 Status: Collecting Watson settings from Registry
28/10/2004 10:03:48 Status: Collecting dumps info
28/10/2004 10:03:48 Status: Closing Unit 4
28/10/2004 10:03:48 Status: Running EventLog collector on DEV-SQL
28/10/2004 10:03:48 Status: Opening Unit 1
28/10/2004 10:03:48 Status: Opening System EventLog on DEV-SQL
28/10/2004 10:03:48 Status: 13170 events in the log
28/10/2004 10:03:48 Status: 13132 (99%) rolled forward
28/10/2004 10:03:48 Status: 13170 (100%) events processed
28/10/2004 10:03:48 INFO: 13170 events processed
28/10/2004 10:03:48 Status: Analyzing OS outages
28/10/2004 10:03:48 Status: Closing Unit 1
28/10/2004 10:03:48 Status: Opening Unit 2
28/10/2004 10:03:48 Status: Opening Application EventLog on DEV-SQL
28/10/2004 10:03:48 Status: 42691 events in the log
28/10/2004 10:03:48 Status: 42508 (99%) rolled forward
28/10/2004 10:03:48 Status: 42691 (100%) events processed
28/10/2004 10:03:48 INFO: 42691 events processed
28/10/2004 10:03:48 Status: Instance: MSSQLSERVER
28/10/2004 10:03:48 Status: Analyzing SQL outages
28/10/2004 10:03:48 Status: Analyzing trace history
28/10/2004 10:03:48 Status: Analyzing AV/assertion history
28/10/2004 10:03:48 Status: Analyzing Watson history
28/10/2004 10:03:49 Status: Closing Unit 2
28/10/2004 10:03:49 Status: DEV-SQL: Collection finished
28/10/2004 10:03:49 Status: Targets processing finished
28/10/2004 10:03:49 Status: Starting Perf Loader
28/10/2004 10:03:49 INFO: Perf host_id = 3
28/10/2004 10:03:49 INFO: Lock aquired: pid = 1
28/10/2004 10:03:49 INFO: D:\SQLH2\PerfCollector\Data\pfc102604161919.txt: fid = 4, state = 0, retry = 0
28/10/2004 10:03:49 Status: Perf records loaded: 0
28/10/2004 10:03:49 INFO: Lock released: pid = 1
28/10/2004 10:03:49 Status: Perf Loader finished
28/10/2004 10:03:49 Status: Starting Data Exporter
28/10/2004 10:03:49 Status: Data Export is not allowed for this Repository
28/10/2004 10:03:49 Status: Data Exporter finished
28/10/2004 10:03:49 SQLH2 is shutting down
28/10/2004 10:03:49 Closing Log
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
Regards
Andy
-
The performance collector needs to run under a profile setup for US dates.
"28/10/2004 10:03:49 Status: Perf records loaded: 0"
This line indicates that no records were loaded, that would be why you can't find any
Have you opened the file itself and checked the contents?
--------------------
Colt 45 - the original point and click interface -
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:15
1,6,5.213032E+09,3149,31/10/2004 01:19:15
1,7,0,3149,31/10/2004 01:19:15
1,8,761.5919,3149,31/10/2004 01:19:15
1,9,0,3149,31/10/2004 01:19:15
1,10,0,3149,31/10/2004 01:19:15
1,11,0.01346138,3149,31/10/2004 01:19:15
1,12,0,3149,31/10/2004 01:19:15
1,13,1.207687,3149,31/10/2004 01:19:15
1,14,0,3149,31/10/2004 01:19:15
1,15,5663.087,3149,31/10/2004 01:19:15
1,16,0.7548152,3149,31/10/2004 01:19:15
1,17,99.89107,3149,31/10/2004 01:19:15
1,18,0,3149,31/10/2004 01:19:15
1,19,226642,3149,31/10/2004 01:19:15
1,20,904008,3149,31/10/2004 01:19:15
1,21,988896,3149,31/10/2004 01:19:15
1,22,0.4330941,3149,31/10/2004 01:19:15
1,23,0.04997224,3149,31/10/2004 01:19:15
1,24,0,3149,31/10/2004 01:19:15
1,25,0.8994992,3149,31/10/2004 01:19:15
1,26,4701120,3149,31/10/2004 01:19:15
1,27,10,3149,31/10/2004 01:19:15
It looks as though the Data Is Being Collected.
Regards
Andy
-
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.
-
Cheers
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?
Regards
Andy
-
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
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply