Question
One table or many?
I'm just starting to re-write a web app and looking at the
database one of the tables is getting quite large (field wise)
The table in question is for room attributes but is used in 3 different apps. It's not particularly large in either direction and isn't high demand on records so I suspect the overall answer to this is in this case it doesn't matter but I'd be interested in people's thoughts.
Do i have one large table with approx 90 fields which has less query load as I'm not joining tables so much or do i have 3 tables (one for the basic room details (5-10 fields) one with the equipment in the room (30 fields) etc. which would need joining each time I used them but would be easier for writing queries as select * would be appropriate most of the time and would arguably be easier to maintain and modify (for both db and queries)?
The floor is now open!
The table in question is for room attributes but is used in 3 different apps. It's not particularly large in either direction and isn't high demand on records so I suspect the overall answer to this is in this case it doesn't matter but I'd be interested in people's thoughts.
Do i have one large table with approx 90 fields which has less query load as I'm not joining tables so much or do i have 3 tables (one for the basic room details (5-10 fields) one with the equipment in the room (30 fields) etc. which would need joining each time I used them but would be easier for writing queries as select * would be appropriate most of the time and would arguably be easier to maintain and modify (for both db and queries)?
The floor is now open!
AdChoices