A table for each user, on app designed for over 10K users?
Posted: Tue Feb 23, 2010 5:06 pm
Hello, I am designing a financial online tool. A person makes entries of purchases, essentially. My plan is having one table for user info, then a table for each user, where it will record entries. An estimate is that each user will add one entry per day. (This is greatly simplified)
I want this to be scalable, so it will run well with 10,000 users and more. Does making a unique table for each user not make sense at that point?
I'm worried that if I just have one 'entries' table for all the users, the data set could become so large it would be hard to search, even if the entries database was very much relational.
Thank you for your insight.
I want this to be scalable, so it will run well with 10,000 users and more. Does making a unique table for each user not make sense at that point?
I'm worried that if I just have one 'entries' table for all the users, the data set could become so large it would be hard to search, even if the entries database was very much relational.
Thank you for your insight.