Feb 25, 2019 02:58 PM|rogersbr|LINK
Hi, yes I had gone thru this normalization exercise way back, but in this application its just a form. One area is not necessarily of higher priority than another except for an ID number perhaps. Its just a big form so all the data has to be kept together.
Checking with a real sharp SQL person who's written books and all, the advice was a wide flat table is fine. I vaguely recall the caveat, its fine until the size limit is reached. Then? You'll definitely have to... and I cant remember what he said after
I could split the sections of the form into tables, so if it has say 20 sections? well then some tables will be small and it may cause a performance hit doing 20 sql table reads versus 1 big one; Or I could look at what uses the most data and split into
the 5 widest groups
Or let me ask this, is there a table PROFILER program that can look at the table and report STATS on the size of various things and say it will lose data when it... ? Some kind of table profiler wizard?