Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If I put the user specific data all in one single table, as the number of users increase, the table size is going to grow too large so that queries will run slow. I know partitioning the table is one solution. But is there a way to design it so that the table won’t grow too large? For example, each user has her own table? Every time a new user is created, a new table for this user will be created?
How many users are you expecting? If it’s less than 100 million, you’ll be fine with one table . Even with more users, you’ll still probably be fine. Worry about it only if it becomes a problem.
Just make sure you have appropriate indexes for finding the rows efficiently, and only find them using your efficient indexes.
Planning your database storage plan for “large data volumes” early is a mistake – it breaks the rule “don’t optimize early”. If you get millions of users, and performance is a problem, you’ll have enough money to pay someone to solve it for you.
Just as an aside, having one table per user is completely insane.