SQLServerCentral / General / SQL Server 7,2000 / SQLH2 Performance Collector / Latest Posts

RE: SQLH2 Performance Collector

kirill — Mon, 29 Nov 2004 22:52:00 GMT

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

RE: SQLH2 Performance Collector

Grigory Pogulsky — Mon, 29 Nov 2004 10:48:00 GMT

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

RE: SQLH2 Performance Collector

andoi — Fri, 05 Nov 2004 01:52:00 GMT

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

RE: SQLH2 Performance Collector

Grigory Pogulsky — Thu, 04 Nov 2004 15:07:00 GMT

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.

RE: SQLH2 Performance Collector

andoi — Mon, 01 Nov 2004 02:12:00 GMT

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.

Regards

Andy

RE: SQLH2 Performance Collector

philcart — Sun, 31 Oct 2004 14:55:00 GMT

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?

RE: SQLH2 Performance Collector

andoi — Thu, 28 Oct 2004 03:36:00 GMT

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:29 28/10/2004 10:03:29 Opening Log 28/10/2004 10:03:29 SQLH2 ver. V2 2.0.024.0 9/30/04 17:5828/10/2004 10:03:29 INFO: The following command line arguments were supplied: /DDMY28/10/2004 10:03:29 Status: Init28/10/2004 10:03:29 Status: Initializing repository: (local)28/10/2004 10:03:30 Status: Repository Database: SQLH2Repository28/10/2004 10:03:30 INFO: host_id = 328/10/2004 10:03:30 Status: Starting RUN 28/10/2004 10:03:30 Status: Registering Run28/10/2004 10:03:30 INFO: run_id = 1428/10/2004 10:03:30 Status: Starting Targets processing 28/10/2004 10:03:30 Status: Initializing Target: DEV-SQL28/10/2004 10:03:30 Status: registering Server28/10/2004 10:03:30 INFO: srv_id = 1; signature = 9b0d433d-4169-44ec-9340-181606c9323228/10/2004 10:03:30 Status: Scanning Registry on DEV-SQL28/10/2004 10:03:30 Status: registering instance DEV-SQL28/10/2004 10:03:30 INFO: inst_id = 128/10/2004 10:03:30 INFO: version: 8.00.76028/10/2004 10:03:30 Status: RUN 28/10/2004 10:03:30 Status: Initializing collector: WMI28/10/2004 10:03:30 Status: Running WMI collector28/10/2004 10:03:30 Status: Opening Unit 1 (OS/CS)28/10/2004 10:03:30 Status: Collecting Win32_OperatingSystem28/10/2004 10:03:32 Status: Collecting Win32_ComputerSystem28/10/2004 10:03:33 Status: Collecting Win32_Processor28/10/2004 10:03:35 Status: Closing Unit 128/10/2004 10:03:35 Status: Opening Unit 2 (NIC)28/10/2004 10:03:35 Status: Collecting Win32_NetworkAdapter28/10/2004 10:03:36 Status: Collecting Win32_NetworkAdapterConfiguration28/10/2004 10:03:36 Status: Closing Unit 228/10/2004 10:03:36 Status: Opening Unit 3 (Disk)28/10/2004 10:03:36 Status: Collecting Win32_DiskDrive28/10/2004 10:03:36 Status: Closing Unit 328/10/2004 10:03:36 Status: Opening Unit 4 (QFEs)28/10/2004 10:03:36 Status: Collecting QFE registry28/10/2004 10:03:36 Status: Closing Unit 428/10/2004 10:03:36 Status: Opening Unit 5 (EventLog files)28/10/2004 10:03:36 Status: Collecting Win32_NTEventlogFile28/10/2004 10:03:37 Status: Closing Unit 528/10/2004 10:03:37 Status: Opening Unit 6 (Processes)28/10/2004 10:03:37 Status: Collecting Win32_Process28/10/2004 10:03:37 Status: Closing Unit 628/10/2004 10:03:37 Status: Opening Unit 7 (Products)28/10/2004 10:03:37 Status: Collecting Win32_Product28/10/2004 10:03:40 Status: Closing Unit 728/10/2004 10:03:40 Status: Opening Unit 8 (Services)28/10/2004 10:03:40 Status: Collecting Win32_Service28/10/2004 10:03:42 Status: Closing Unit 828/10/2004 10:03:42 Status: Initializing collector: EventLog28/10/2004 10:03:42 Status: Initializing collector: SQL28/10/2004 10:03:42 Status: Running SQL collector on DEV-SQL28/10/2004 10:03:42 Status: Opening Unit 5 (Server Properties)28/10/2004 10:03:42 Status: Closing Unit 528/10/2004 10:03:42 Status: Opening Unit 1 (Databases)28/10/2004 10:03:48 Status: Closing Unit 128/10/2004 10:03:48 Status: Opening Unit 2 (Current Configuration)28/10/2004 10:03:48 Status: Closing Unit 228/10/2004 10:03:48 Status: Opening Unit 3 (Running traces)28/10/2004 10:03:48 Status: Closing Unit 328/10/2004 10:03:48 Status: Opening Unit 4 (Registry)28/10/2004 10:03:48 Status: Collecting Watson settings from Registry28/10/2004 10:03:48 Status: Collecting dumps info28/10/2004 10:03:48 Status: Closing Unit 428/10/2004 10:03:48 Status: Running EventLog collector on DEV-SQL28/10/2004 10:03:48 Status: Opening Unit 128/10/2004 10:03:48 Status: Opening System EventLog on DEV-SQL28/10/2004 10:03:48 Status: 13170 events in the log28/10/2004 10:03:48 Status: 13132 (99%) rolled forward28/10/2004 10:03:48 Status: 13170 (100%) events processed28/10/2004 10:03:48 INFO: 13170 events processed28/10/2004 10:03:48 Status: Analyzing OS outages28/10/2004 10:03:48 Status: Closing Unit 128/10/2004 10:03:48 Status: Opening Unit 228/10/2004 10:03:48 Status: Opening Application EventLog on DEV-SQL28/10/2004 10:03:48 Status: 42691 events in the log28/10/2004 10:03:48 Status: 42508 (99%) rolled forward28/10/2004 10:03:48 Status: 42691 (100%) events processed28/10/2004 10:03:48 INFO: 42691 events processed28/10/2004 10:03:48 Status: Instance: MSSQLSERVER28/10/2004 10:03:48 Status: Analyzing SQL outages28/10/2004 10:03:48 Status: Analyzing trace history28/10/2004 10:03:48 Status: Analyzing AV/assertion history28/10/2004 10:03:48 Status: Analyzing Watson history28/10/2004 10:03:49 Status: Closing Unit 228/10/2004 10:03:49 Status: DEV-SQL: Collection finished28/10/2004 10:03:49 Status: Targets processing finished28/10/2004 10:03:49 Status: Starting Perf Loader28/10/2004 10:03:49 INFO: Perf host_id = 328/10/2004 10:03:49 INFO: Lock aquired: pid = 128/10/2004 10:03:49 INFO: D:\SQLH2\PerfCollector\Data\pfc102604161919.txt: fid = 4, state = 0, retry = 028/10/2004 10:03:49 Status: Perf records loaded: 028/10/2004 10:03:49 INFO: Lock released: pid = 128/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 Repository28/10/2004 10:03:49 Status: Data Exporter finished 28/10/2004 10:03:49 SQLH2 is shutting down28/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

RE: SQLH2 Performance Collector

snikpoh — Thu, 28 Oct 2004 02:30:00 GMT

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

RE: SQLH2 Performance Collector

philcart — Thu, 28 Oct 2004 02:17:00 GMT

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.

SQLH2 Performance Collector

andoi — Wed, 27 Oct 2004 01:54:00 GMT

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