We have an "appointments" table with following schema.
app_type - type of appointment
location_id - keeping the location for multiple location setup.
We are using MySQL and expect about 20,000-50,000 rows inserted per day around 365 days.
The expected number of operations = number of appointments * 5
For each operation in our app, we'll read this appointment table to get particular appointment details and update certain flags in the same table.
SPEED is our main concern.
My question is, performance wise is it OK to
- leave this schema as it is (large number of rows and many reads across it), or
- keep separate appointments tables for locations?