Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: ADO MaxRows property and Oracle 7.3.4

Re: ADO MaxRows property and Oracle 7.3.4

From: John Hurrell <John.Hurrell_at_Westgroup.com>
Date: Thu, 22 Jul 1999 15:14:01 GMT
Message-ID: <37973213.154989833@news.westpub.com>


On Tue, 20 Jul 1999 08:01:14 -0400, Jeff Ashley <jeffashley_at_worldnet.att.net> wrote:

>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 . . .

A primary key is merely a field that is guaranteed to be unique, not fast. An INDEX is a set of information about the physical location of data and therefore WILL speed performance.

The bad news is, in either case using an ORDER BY clause will incur a performance hit because Oracle has to sort the recordset before it can return the first X number of records you request. Received on Thu Jul 22 1999 - 10:14:01 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US