On Mon, 15 Apr 2002 09:56:18 -0400, tellef wrote: >This is a VERY LARGE client database that I have never >reloaded on my computer
Karen, This is a big, big clue. R:Base's "query optimizer" is very sophisticated at guessing the fastest way to retrieve a result set. However, it bases its guess on the statistics created when a database is reloaded. In the worst case, if a table had zero rows in in the last time it was reloaded or packed or indexed, R:Base would have no idea how big the table was or how unique the indexes were or how contiguous the rows from the table were in the data file, and would almost certainly guess wrong. Don't reload, just rebuild the indexes on the indexed columns in the tables you are querying. To find the names of the indexes, type: LIST INDEX FOR tablename and see the result in the first column. Then type: PACK INDEX indexname for each index. Run your queries again, and see if that doesn't improve things. The file RSTRHELP.HTM, that is installed with RSTRUC, describes the "duplicate factor" and "adjacency factor" that are stored in the sys_indexes tables. (Read the section about Indexes.) Bill ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
