Page 1 of 1
Does the number of tables in a DB affect performance?
Posted: Tue Aug 19, 2003 5:42 am
by JayBird
As to topic title says.
I have 86 tables in my DB, is that a lot? Will performance be reduced compared to if i only had one table?
I am only ever querying 1 table at a time on any one page of my site.
Cheerz
Mark
Posted: Tue Aug 19, 2003 3:05 pm
by brewmiser
I have read that the amount of tables do not matter, and that it could be a better design if you have more tables with a lot of differnt types of data to be stored.
To put it simply, if I was looking for a certain type of orange among all the other fruits in the world, then it would be easier to find this under a table named orange's, and not to look through all the different fruits just to find that orange.
Does this make sense? Does anyone disagree with me?

Posted: Tue Aug 19, 2003 6:15 pm
by Coco
i think the question really is... is it more efficient to have separate tables for each kinda of fruit, or a single table with a collumn denoting which type of fruit you are after
personally i would say it depends, on how many lines of data, and how often you will be doing a select...
eg if it was an archive table then you shouldnt be using it much... but if it was a sales database or something that you use alot, then it might be better to split it up a little... to make the selects faster
and even then most the efficiency gained is in the human department... its easier to understand a db with a few tables, but one with alot takes more brain power :p