And the plan is not to dump the entire recordset to the client, but to build a "Next n" interface that will allow them to filter/sort the results and then scroll through the records 50 or so at a time. We plan to cache the recordset returned by the SP using QofQ. The main problem is that the SP is slow (and out of my control to change or optimize!) and we need a way to hit it once and then display/filter/sort the records in various ways.
We could save ourselves a lot of headaches if there was a way to cache the SP recordset directly, but I don't see a way to do that.
Any better ideas are certainly welcome!
Thanks,
Chris
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, October 20, 2003 2:36 PM
To: CF-Talk
Subject: RE: CF5: Oracle recordset via StoredProc and QofQ questions
small recordsets perhaps, but the set you described will cause issues. Think about how much time it takes to run the SP and return all data to CF then down to the client. Also, the browser ain't gonna handle 100MB of data very well now, eh? Now, your DB call will take up a thread for a long time, if the user cancels a request this thread stays active. Non patient users will cause havoc here.
Doug
-----Original Message-----
From: Lofback, Chris [mailto:[EMAIL PROTECTED]
Sent: Monday, October 20, 2003 2:24 PM
To: CF-Talk
Subject: RE: CF5: Oracle recordset via StoredProc and QofQ questions
So it's really just a question of RAM? No other serious performance concerns for retrieving record sets via SP?
Thanks,
Chris
-----Original Message-----
From: Jochem van Dieten [mailto:[EMAIL PROTECTED]
Sent: Monday, October 20, 2003 12:08 PM
To: CF-Talk
Subject: Re: CF5: Oracle recordset via StoredProc and QofQ questions
Lofback, Chris wrote:
>
> 1) Are there any limitations/issues when retrieving large (say 250,000 rows of 10 varchar2(50) columns) recordsets from Oracle 8 using a stored procedure? Is it slow? Unstable/flaky?
250,000 * 10 * 50 = 125 MB minimum
It needs to be stored in RAM.
> 2) Can QofQ handle a recordset that large?
If you have the RAM. Remember that with every QoQ you create a
new recordset that needs to be stored in RAM. Plus the output
page needs to be stored in RAM.
I would rethink and try to do more in the DB.
Jochem
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
