Database speed optimization: few tables with many rows, or many tables with few rows?

Question

I have a big doubt.

Let\'s take as example a database for a whatever company\'s orders.

Let\'s say that this company make around 2000 orders per month, so, a

Answer 1

Look into partitioning your tables in time slices. Partitioning is good for the log-like table case where no foreign keys point to the tables.