John,

I'd prefer to do it another way.

First, find all tables with largest 'bufreads' and 'pagreads'.
You should only concern about sequential scan around these
tables.

Then, find those among them with large 'seqscans'.
These are real candidates for re-indexing or SQL re-writing

----------------------------
Alexey Sonkin

-----Original Message-----
From: John Hardin [mailto:johnh@aproposretail.com]

On Wed, 19 May 2004 01:26:42 -0700, malcolm wrote:

> I found that the best way to tackle this is to find all tables with a
> large number of sequential scans (sysptprof linked to systabinfo) and
> then discard the squential scans where the table has only a few rows.
> That way you can identify the most common tables. Next find the user
> doing the most sequential scans (syssesprof, syssessions). It gives a
> lead into who and what is causing the problem.

Great suggestions, thanks!

--
John Hardin KA7OHZ <johnh@aproposretail.com>
Internal Systems Administrator voice: (425) 672-1304
Apropos Retail Management Systems, Inc. fax: (425) 672-0192
-----------------------------------------------------------------------
Failure to plan ahead on someone else's part does not constitute an
emergency on my part.
- David W. Barts in a.s.r
sending to informix-list