On Fri, 26 Mar 2004 15:23:13 -0500, casey wrote:
> By far, the highest I/O are report queries.
>
If those are 4GL reports, look for ORDER BY sections in the report function
that are not REPORT BY ... EXTERNAL. If you can put the ORDER BY criteria
into the query supplying the data and make the report's ORDER BY be EXTERNAL
that will reduce IO's not reported by the engine hugely.
Art S. Kagel
↪ replying to Art S. Kagel
"Art S. Kagel" <kagel@bloomberg.net> wrote in message
news:pan.2004.03.29.09.54.49.151658.1445@bloomberg.net...
> On Fri, 26 Mar 2004 15:23:13 -0500, casey wrote:
>
> > By far, the highest I/O are report queries.
> >
> If those are 4GL reports, look for ORDER BY sections in
the report function
> that are not REPORT BY ... EXTERNAL. If you can put the
ORDER BY criteria
> into the query supplying the data and make the report's
ORDER BY be EXTERNAL
> that will reduce IO's not reported by the engine hugely.
>
> Art S. Kagel
Art, thanks, great suggestion!