sql - Should I use flat tables or a normalized database? -


i have web application working on uses mysql database back-end, , need know better situation before continue further.

simply put, in application users able construct own forms number fields (they decide) , right have stored in couple tables linked foreign keys. friend of mine suggests keep things "easy/fast" should convert each user's form flat table querying data them stays fast (in case of large growth).

should keep database normalized pooled relational tables foreign keys (indexes, etc) or should construct flat tables every new form user creates?

obviously positives of creating flat tables data separation (security) , query speeds cut down. how gain this? don't want 10000 tables , dropping, altering, , adding of time, if better it... need input.

thank you

rule of thumb. it's easier go normalized denormalized other way around.

start reasonable level of database normalization (by reasonable mean readable, maintainable, , efficient not prematurely optimized), if hit performance issues grow, have option of looking ways in denormalization may increase performance.


Comments

Popular posts from this blog

asp.net - repeatedly call AddImageUrl(url) to assemble pdf document -

java - Android recognize cell phone with keyboard or not? -

iphone - How would you achieve a LED Scrolling effect? -