Mike-palmer
Registered User.
- Local time
- Today, 17:01
- Joined
- Mar 27, 2003
- Messages
- 37
I have created a DVD database that includes graphics files of the DVD case covers. Each cover is about 300K in size. The databse performed well when I only had 50 DVDs, but now I'm up to 200 DVDs and flipping through the database is getting slower and slower as it pulls up each record. The DB is about 70MB in size.
Currently all the DVD data (including the graphics) is in one table with other tables being used only for ratings.
Sometimes flipping from one record to the next happens quickly, but, especially across the network, it takes several seconds to go from one record to the next.
Are there any best practises that I should be following under these circumstances?
Currently all the DVD data (including the graphics) is in one table with other tables being used only for ratings.
Sometimes flipping from one record to the next happens quickly, but, especially across the network, it takes several seconds to go from one record to the next.
Are there any best practises that I should be following under these circumstances?