We routinely work with tables on Sybase servers with 250,000 records and up.
I have found that ND delivers the results about as fast as the server can
spit them out with one caveat. ND doesn't seem to render any HTML until the
entire result set is returned.
1. Make sure the table is thoroughly indexed.
2. Check the size of the result set. A big one will kill your ND server.
3. Try your query on some generic SQL front end and time it to see if it is
ND or your database that is the laggard.
4. I have never been able to kill a request. If I fire off a query and
then get tired of waiting and close my browser, that query is still out
there chugging away until it completes or fails. Don't hit the search
button twice when things are running slow.
In any case, 13,000 records is just a baby table in our world. I would
expect sub-one second response time from our server and a response back to
the browser in less than 3 seconds for the first request (shorter after the
project has loaded).
Good luck,
Roger Feeley
Bridge Information
Gregory Bohmer <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Hi all,
>
> We have a very large table in our Oracle database that we are
> trying to hook up a DataObject to. The table (actually it's a view)
> has 34 columns and 13,000 rows. The execution of the
> DataObject takes around 3 minutes - regardless of the dynamic
> criteria added. Has anyone seen this type of poor performance?
> What are other people's experience working with tables
> approaching this size?
>
> Thanks for all input...
>
> -Gregory, HHMI
>
>
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
