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.
I’m building an ASP.NET MVC application.
I will store a lot of data per application user, so I was considering having separate DBs for each user’s data. Of course all DBs will be 100% the same in terms of structure. They should all be derived from some kind of master DB.
Can someone give me any leads on how to realize this?
Unless you are planning to handle millions of users with millions of rows in each table you will not need to use multiple DB’s.
MS Sql can easily handle a billion rows in a table with good indexing and still keep good query performance.
Using multiple DB’s will most likely only cause headaches.
That said, you should design scrips to create the databases, and later update scripts for changing them since you would have to propagate any changes to all databases.
But my recommendation is to stick with one DB. If you actually manages to outgrow that you most likely need to redesign the database structure anyway 🙂