Monitoring query Execution in Progress 8

[sulimo]

Hi There.
We have a particular Job which is taking more than usual, and we want to *monitor* it's execution. Hence, and being our progress version 8, I would like to know, if you please:

1) Is there a way to get query explain plan?
2) How would I update statistics for tables and indexes?
3) How can I trace a job execution?

Any other ti/advice would be really appreciated.

TIA

 

[Casper]

1) Is there a way to get query explain plan?

I don't know exactly what you mean but you can look if the right indexes are used with XREF:

compile [I]source.p[/I] XREF path_to_save_output\output.xref.

2) How would I update statistics for tables and indexes?

Reading this I'm beginning to wonder weather your query is SQL or 4GL (ABL) but read this KB entry for update statistics: http://tinyurl.com/lczvf

Syntax: UPDATE STATISTICS for pub.tablename


AFAIK update index statistics is only possible since version 9.1D.

3) How can I trace a job execution?

Since you have version 8 there is no profiler or -yx parameter, so the best way I can think of (but I could be wrong) is to use etime function to trace job execution.

Another way of looking at preformance is by using promon and look at the record read in activity screen and see if then numbers are reasonable compared to the result you get. (If you for instance expect 1000 records and there are many more reads then you have a problem with indexes).

HTH,

Casper.

 

[sulimo]

Thanks Casper. I have this new doubt now. (I'm still on Progress 8)
We had to rebuild all indexes on database and we got some warnings about lost chains on tables. AFIK lost chains are fixed on the fly as blocks are accessed. Is that so? Problem is than after index rebuilt queries now run slower. Since you mentioned statistics update is not possible on version 8, I was wondering if there is anything I could do to recompute statistics and or make queries resolve as they did before index rebuilt.

regards,
jm