I have an application that I believe to be growing beyond the capabilities of Access. There is a table with about 5.9 million records that my application is having speed issues accessing after compacting. Here's the deal:
DB size (no compact): 700mb
Records in table: 5.9 million
Simultaneous users: 9
Time of report without compact on my machine (no simultaneous users): 50 seconds
Time of report on file server that is sharing this db: 12 minutes
If I compact and repair, it actually INCREASES the time it takes to run the report on my machine to about 24 minutes!!!!! I can't seem to find an explanation for this. I tried defragging and then compacting/repairing and the same thing happens. If after the compact/repair I get the number of records down to about 3.1 million, the report only takes 50 seconds to run again.
Can anyone explain why compacting/repairing, even after a defrag causes the report to take 30 times as long to run?
DB size (no compact): 700mb
Records in table: 5.9 million
Simultaneous users: 9
Time of report without compact on my machine (no simultaneous users): 50 seconds
Time of report on file server that is sharing this db: 12 minutes
If I compact and repair, it actually INCREASES the time it takes to run the report on my machine to about 24 minutes!!!!! I can't seem to find an explanation for this. I tried defragging and then compacting/repairing and the same thing happens. If after the compact/repair I get the number of records down to about 3.1 million, the report only takes 50 seconds to run again.
Can anyone explain why compacting/repairing, even after a defrag causes the report to take 30 times as long to run?