Hi Ted, Are you using the "Limit to" and "Start retrieval at row number" properties of the Search Action to manage your output in chucks of 100 records?
If so, you should know that these settings are for communicating with your ODBC Database Driver, and not with the Database directly. If there is a slow down in performance, it's likely because your particular ODBC Driver is not filtering the output very efficiently. Check for the latest version of your Driver, or see if your Database supports this kind of filtering natively - in which case you'll probably need to pass any special SQL Statement syntax via a Direct DBMS Action. In addition, table "indexing" can also speed up queries. In many cases ODBC Drivers can build their own indexes (in memory) - but implementing indexes in your table design (on the key fields being queried) can be very beneficial. Hope this helps. Cheers.... Scott Cadillac, Witango.org - http://witango.org 403-281-6090 - [EMAIL PROTECTED] -- Information for the Witango Developer Community --------------------- XML-Extranet - http://xml-extra.net 403-281-6090 - [EMAIL PROTECTED] -- Well-formed Development (for hire) --------------------- > -----Original Message----- > From: Ted Wolfley [mailto:[EMAIL PROTECTED] > Sent: Monday, July 28, 2003 12:10 PM > To: '[EMAIL PROTECTED]' > Subject: Witango-Talk: Search reterivial > > > Hi, > > In a search action, I am retrieving 1949 records in > alphabetical order, 100 > records at a time. The first 1000 records (10 web pages) are returned > quickly. It is after the 1000 record that performance goes > down hill with > each sequential page taking longer. Does any one know why > this would be > happening and how to improve performance? > > Ted > ______________________________________________________________ > __________ > TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
