When to use multiple databases?
Posted 21 September 2006 - 07:21 AM
I am building a website that will allow access for 3 different types of users: owners, admins, and users. Each of these user types will have their own unique tables and fields. I expect there to be over 10,000 users for each type.
Now, I realize that I can just use one database and create a bunch of tables in it, each specific for my 3 user types. And this would be easier for me to program. Conceptually, however, it seems to make better sense to use a different database for each user type.
I would like to know if it is better/faster/more resource efficient/etc to use one large database with many tables, or to break it down into 3 databases, one for each user type.
Thanks for reading this and your input!
Posted 21 September 2006 - 08:39 AM
Meaning: I'm some ISP, I have a RDMS server, different clients use that server. Different clients logon to that server, and have access to different groups of tables, eg databases.
Posted 21 September 2006 - 08:41 AM
The only system design I can think of that should allow multiple DB's is a DB manager like phpMyAdmin.
Posted 21 September 2006 - 10:47 PM
In the case of my current project at work, we have multiple clients using the same system. So we've assigned a separate database to each client.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users