I’m having great difficulty getting a database setup to handle a large amount of information.
It’s for an 8-ball league that my wife and I run. Every week there are a dozen matches. Each match is two teams, 5 to 7 players per team and 35 games. We track individual player game scores, averages, handicaps, runouts, and other information as well. Each scoresheet has roughly 350 bits of information. Twelve scoresheets per week and twenty-seven weeks in the season. That works out to around 113,000 bits of data.
My initial attempt had 364 records and 348 fields. It works but slowly.
Then on my next attempt I thought I would try to simplify things by reducing the number of fields down to 7 and putting a lot of the needed information into a dictionary for each record. Each dictionary has 343 entries. I expected an improvement in performance with the reduced field count but it is actually considerably worse.
These attempts take a lot of time to put together, and I don’t really want to waste too much time with poorly-conceived structures.
Do you guys have any suggestions for a general structure for my database?