We are developing an on-line database application for tracking Athletic Data.I estimate the average customer will have 500 Athletes, 2,000 Injuries and 10,000 Treatments.
+---- > Athletes
+---- > Injuries
+------ > Treatments
The advantage to a single SQL datababse would be:
1. One schema to maintain.
2. Ability for customers to compute collaborative statistics.
The downside would be:
1. Individual customer Queries are against the complete database.
2. Multiple customers accessing the same database concurrently.
The total number of records, even over 500 customers is small compared to SQL's capabilities, so I would expect a single database to be best. What are the considerations for creating a single large vs. multlple seperate (one per customer) databases of the same schema? My primary concern is querry speed.