Copying table structure to manage large number of rows.

[Philip Parker]

I'm finishing an application and preparing for the possibility of 10 million active users each year. I'm looking at one table that will have 100's of rows per user. I'm a programmer not a DBA and thought duplicating that table structure 50 times could work. Each User would be assigned a permanent table decided by their user_id. Those tables would not JOIN or connect with each other but will JOIN with a few other tables. This is only to manage the very large number of rows expected. Is this a valid design or am I missing something? While researching I see Partioning mentioned. Should I be looking into that? Below illustrates what I have in mind. Thank you.

User
=======
1 John
2 Adam
3 Jane

TableNum = ceiling( user_id )

Table1 ... Table50
======= =======