Database design for millions of posts I have this issue. I have three types of posts a user can generate (some users can generate all some can only generate one type).  I have the following types: main, employee and admin posts. 

I expect to have to deal with millions of posts (all three types).  But about 90% of all posts would be main_posts. Also, most reads from the DB would be of the main_posts too.

NOTE
The main_posts table would have about 50-100 more fields than what is currently there. update
those fields would be normalized into different tables. The ideea is that the main-posts table would have the bulk of the posts and therefore would have the most reads and writes.

Which design option is more sound?

Option1


or Option 2


Thank you.
Read this post how StackExchange does it:

http://www.brentozar.com/archive/2014/01/how-to-query-the-stackexchange-databases/