SamirNaenenjad
Programmer
I have a large Access 97 database (~500MB) that has a large table with about 250,000 records. This table has a lot of different indexes. There is no primary key set on the table, but many queries I use do a join on fields A and B (both text fields and indexed) as if they were a composite key.
These queries used to run fine, until I added some more indexes to some other fields people wanted to search on. All of the sudden, any query that used a join on field A grinded to halt. After much experimentation, I isolated the problem and determined that taking the index off of field A made the queries run quickly again.
This surprises me because I was taught that indexes sped up searches and joins on the indexed fields (but added to the size of the DB). Has anyone else seen behavior like this? Does anyone have a theory as to why this may occurr?
Thanks,
A.J.
These queries used to run fine, until I added some more indexes to some other fields people wanted to search on. All of the sudden, any query that used a join on field A grinded to halt. After much experimentation, I isolated the problem and determined that taking the index off of field A made the queries run quickly again.
This surprises me because I was taught that indexes sped up searches and joins on the indexed fields (but added to the size of the DB). Has anyone else seen behavior like this? Does anyone have a theory as to why this may occurr?
Thanks,
A.J.