Re: ADO MaxRows property and Oracle 7.3.4

From: Jeff Ashley <jeffashley_at_worldnet.att.net>
Date: Tue, 20 Jul 1999 08:01:14 -0400
Message-ID: <3794650A.AC8A4E78@worldnet.att.net>

Yeah, but if you are ordering by primary key, there should be _zero_ difference! I don't work with Oracle, but there must be something getting missed here . . .

Joe Spanicek wrote:

> Hi,
>
> An ORDER BY clause tells the ORACLE database engine to order the rows
> returned using
> the field specified. ORACLE will first order the 500,000 rows it has in
> the table,
> it will then send all the rows selected back to VB which will then
> display 250 rows.
>
> The 70sec is the ordering been performed, removing the ORDER BY clause
> tells ORACLE
> to just return the selected rows which is quite quik.
>
> Thats how it works and the time difference is what you would expect.
>
> But if you just want to return 250 rows, not fussed with the order of
> results,
> use the following
>
> setTable1.Open "SELECT Field1, Field2 FROM Owner.Table1 WHERE rownum
> <251"
>
> Hope this helps
>
> Joe
Received on Tue Jul 20 1999 - 07:01:14 CDT