Tables of a huge database When I work on a huge database, and after following normalization rules, I found that I have many tables for each part of my huge database. That makes me worry about the final number of tables, it will be in the hundreds.

What is the best choice for me?


make many tables with a small number of columns? or
make few tables with many columns?
In general, the more tables in a database, the more normalised it is. 

If your table has many columns, the chances are that some of them will be empty a lot of the time, or repeating types, or other breaches of normalisation, so as you've discovered, normalisation leads to more tables. This is perfectly normal (no pun intended), is nothing to worry about and will lead to easier and more efficient querying