I am currently working on a large application that will be used by many people each having a large amount of data. I thought to manage these multiple users through a single database but I am asked to create a separate database for each new user that is registered. Now what I am wondering is : is it a good idea to do so i.e. having the app create a separate database for each new user that gets registered and manage it's data through it? What will be the performance issues, if any?
Take the tour
×
Stack Overflow is a question and answer site for professional and enthusiast programmers. It's 100% free, no registration required.
|
|
My answer is create a separate database for each new user is a wonderfool idea.you must set appropiate indexes over the table and you will get good performance | |||||
|
|
Separate DB for each new registered user might be bad idea. You can do it like this; Put 100 users in each separate db. 1-100 => db1, 101-200 => db2, n, n+100 => dbn You can keep a table for which id interval will be connect to which db. By doing this, you can lower db load. 100 users for each db is just an example. You need to use such a structure for a system that has lots of users. | |||
|
|
