Maxrows filters at the CF level and should be avoided.  Filtering at the
database level is far more efficient.

Returning 250,000 rows from a database to an app server is something you
should never do.  Even if the database can handle it properly, when CF
creates it's in-memory static representation in a QueryTable it will take a
lot of time.

Sam

----------------------------------------------
Blog:  http://www.rewindlife.com
Chart: http://www.blinex.com/products/charting
----------------------------------------------

-----Original Message-----
From: Thomas Chiverton [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 15, 2003 8:38 AM
To: CF-Talk
Subject: Re: Top n in Oracle

On Wednesday 15 Oct 2003 13:27 pm, Heald, Tim wrote:
> The table has something like 250,000 records.  The performance would make
> that impossible.

Have you looked at the docs for cfquery ?
In particular maxRows ?

If you query can't return 250K rows in something like stright away, you need
to look at your hardware/indexes urgently :-)

--
Tom Chiverton

[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to