I am trying to design a database which will collect data on the people coming to a particular swimming pool divided by age groups. For one such pool, I want to be collecting data once a day. There are more than 1000 such swimming pools I want to collect data on.
Now I want to use this database to be able to provide a reporting facility through a front end.
The problem is how I go about designing it. Should I have one table for each pool, and another table having the list of pools. Or should I have one table where the primary key is <poolname>.<day-time> and have all data in one table.
My concern is how do I measure the performance criterion without actually building a database. any other pointers on what to consider while designing this will also help.