By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,677 Members | 1,094 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,677 IT Pros & Developers. It's quick & easy.

Multiple Databases or Single Database

P: 2
Can anyone plz tell me the advantages and disadvantages of using multiple databases / single database for all tables.

I have a site with more than a 100 tables. Current all the tables are in a single database, so that I can access it with a single Database Wrapper Object (PDO). Should I split it into multiple databases? Will it affect the speed?
Nov 5 '08 #1
Share this Question
Share on Google+
4 Replies


code green
Expert 100+
P: 1,726
Sounds to me that you have a collection of 100 flat files rather than a database.
I doubt you would be asking the question if it was a true database design.
Nov 5 '08 #2

P: 2
Sounds to me that you have a collection of 100 flat files rather than a database.
I doubt you would be asking the question if it was a true database design.
I am not sure why you said that. My experience with database is limited.
Nov 5 '08 #3

code green
Expert 100+
P: 1,726
Well a hundred tables of what?
If they are all an integral part of the database, then splitting them is not an option.
If however they are storing similar information,
and I suspect they are growing in number,
then you simply have a collection of tables
Nov 5 '08 #4

Atli
Expert 5K+
P: 5,058
How you split up your tables is more of a design issue than anything else.

For most projects, putting all the tables into a single database is fine. It's not unless you are working on some massive project that might need some larger scale organization that you should start considering splitting it up.
Nov 6 '08 #5

Post your reply

Sign in to post your reply or Sign up for a free account.