Enjoy an ad free experience by logging in. Not a member yet? Register.
Results 1 to 3 of 3
Thread: One table vs. multiple tables
08-21-2012, 04:55 PM #1
- Join Date
- Mar 2010
- Orlando, FL
- Thanked 8 Times in 8 Posts
One table vs. multiple tables
Quick question...is it better to have one big table or many small ones? Example: What are the pros and cons of having one table with a list of teachers and one table with a list of all the students belonging to those teachers as opposed to each teacher having their own table of students?
08-21-2012, 08:14 PM #2
- Join Date
- Mar 2006
- St. Catharines, Ontario Canada
- Thanked 148 Times in 139 Posts
See Normalization, that is the important concept to learn, not whether or not you have a certain number of tables.
As for splitting tables so you don't have "too many" rows, properly normalized and indexed tables with appropriate server tuning and you can get into the hundreds of millions of rows without taxing your server.
08-21-2012, 08:51 PM #3
More succinctly: One table per teacher is a *terrible* design. Don't even think about it.
A pessimist sees the glass as half empty.
A realist drinks it no matter how much there is.