Steve You are right- this should not be!
I suspect database corruption. 1. Check with AUTOCHK dbname FULL 2. If all is OK, back it up and PACK KEYS See if you can track it down and fix it! David Blocker ----- Original Message ----- From: <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> Sent: Thursday, January 09, 2003 8:02 AM Subject: [RBASE-L] - WHERE/ORDER BY On Indexed Column of Small Table SLOW ... > Slower than molasses in January! I don't know what's happenin' here. I > have a table, 'CODES_COUNTIES', that contains 95 records f/the counties > of TENN. 2 are indexed, CountyFIPS and District (another geo-political > unit of the client). The DB has become rather large, but I've had some > at least 2x as big. > > Now, whenever I use a WHERE||ORDER BY clause on these 2 fields, it takes > 10's of minutes or more to produce a result-set. This shouldn't take > more than maybe a second on 95 rows if it's un-indexed, much less if it > is. I'm totally bumfuzzled. > > Any ideas. > > In great need of help here, > Steve in Memphis > >
