I am working on a project where I have to deal with large column table storing meter readings for power stations. Presently date is being stored in a table as below.
Date, Block No, Station 1, Station 2, ....... , Station N (N can go upto 650) 2013-05-21, 10, 23, -45,........ , 57
Now there is another Table B which has fields derived from Table A.
Date, Block No, F1, F2, ....... , FX 2013-05-21, 10, 23, -45,........ , 57
Here Table B fields are derived as below
- F1= Station 1 + Station 3,
- Fx = Station p + station r + Station w
Now I want to change this approach of having a field for each station and derived field. I want to make tables as below.
Date, Block, Station_Name, Reading 2013-05-21, 10, Station 1, 23 2013-05-21, 10, Station 2, -45 . . . 2013-05-21, 10, Station N, 57
My questions are:
- Is my proposed normalized design will have processing impacts?
- Generally how such tables should be designed, what are best practices?
- Will SQL be more complex in my approach for updating derived field of Table B compared to earlier one?