--- In ib-support@yahoogroups.com, Helen Borrie <helebor@t...> wrote:
Helen,
I have one more field in the query called CUST.Cust_no.And this
field is having a index on CUST table.If i give order by CUST_NO, now
it takes 3 minutes 2 seconds for fetching the same 27019 records,

If i remove the order by clause, then it takes 2 minutes 55 seconds
for fetching 27019 records.

Regards,

Sivaraman

> Aage,
>
> At 02:33 PM 8/06/2003 +0200, you wrote:
> >On Sun, 8 Jun 2003 12:24:44 +0000 (UTC), Helen Borrie wrote:
> >
> > >> ...
> > >
> > > No. You must have an index on an ORDER BY field.
> >
> >Helen, quite often an index on a ORDER BY field is not a good
thing -
> >sorting is usually fast. Unless I only need the first record, I
use
> >indexes for the WHERE clause, not for the ORDER BY. YMMV.
>
> With 27,000 records ordered on a varchar column, it aint going
anywhere
> fast with no index. YMMV.
>
> heLen