[AccessD] Table Structure Ideas

I have been over this several times, but shall try again. 3NF is totally
inadequate. 4NF also fails. 5NF is the miniimalll correct soluution to a
datbase involving 100M rows. Before proceeding further, let's get some
terms straight. "Large" means 500+ tablles; "Rich" means a few gehundred
tables with many millions of rows. It is possible, although rare, to
encounter a database that is both large and rich

Having thus defined the terms, and of course you are free to argue said
terms, but this is IMO not a problem of issues but of terrminology. In my
experience, very few databases are both large and rich; some years back I
did develop one that comprised 500+ tables and 100M rows in the transaction
table. Of course, the only way to make sense of this  amount of data was
partitions etc. Not a  simple task. It took a couplle of years to design
and build, and I could have not done it without Red Gate's tools. I have no
interest in this company, but I have to sayy that the two best players in
the game are Red Gate and ApexSQL.

A.
​