Working on redesigning a previously created database.
The existing database has a table to store pump station data.
The table looks something like this, with no related tables associated with it.
(50 Fields) Wasn't me
StatinID pk
StationGals (16 Pump Stations)
StationPump1Hrs (16 PumpStations)
StationPump2Hrs (16 Pump Stations)
StationDate
I thought that there should be two seperate tables. One to store the pump station name and the other to store the gallons and pump hrs.
The data is entered every day so the original table would have 365 records for each year.
With the new design it seems that there will be 16 records for each day or 5840 records per year.
My question is even though the new design would be a better normalization the rows would expand quite a bit over the passing years. Would this create a problem with the database size after so many years.
Thank you in advance
The existing database has a table to store pump station data.
The table looks something like this, with no related tables associated with it.
(50 Fields) Wasn't me
StatinID pk
StationGals (16 Pump Stations)
StationPump1Hrs (16 PumpStations)
StationPump2Hrs (16 Pump Stations)
StationDate
I thought that there should be two seperate tables. One to store the pump station name and the other to store the gallons and pump hrs.
The data is entered every day so the original table would have 365 records for each year.
With the new design it seems that there will be 16 records for each day or 5840 records per year.
My question is even though the new design would be a better normalization the rows would expand quite a bit over the passing years. Would this create a problem with the database size after so many years.
Thank you in advance