Ive have been given a 10 page paper from to convert into a db with a web input. Previously on a similar project someove very simply made a seperate table for each page of the paper from, linked with a user id.
Is this the best method I know how to normalise the data, Having counted through it looks like my table would have about 40 varchar fields, and about 40 fields being a combination of boolean or tiny int fields that would join with a lookup. there would also be about three other tables for repeating data entries.
Im having a discussion in the office that this is the wrong approach and it should be split into each page having its own table, regardless of what the data represents. If I did it in the normalised approach would I run into difficulty with the amount of fields (around 80)? and would performance be an issue?
Is this the best thing to do, and how would I know if I was getting near the maximum size for a table?
The application will page through and insert data at each stage rather than at the end.