You may want to look into normalization to keep everything organized. However if you want pure query speed, you will have to de-normalize some of your tables to get optimum speed.
Have a look here for info on normalization: http://databases.about.com/od/specificproducts/a/normalization.htm HTH --- bruce <[EMAIL PROTECTED]> wrote: > hi... > > i'm considering an app where i'm going to parse a > lot of colleges (~1000) > faculty information. would it be better to have all > the faculty information > in one large table or would it be better/faster to > essentially place each > college in it's own separate table, and reference > each table by a > college_ID, that's unique and assigned to each > college, and maintained in a > master_collegeTBL... > > thoughts/comments/etc.... > > i'm leaning towards the side that keeps each college > information separate, > although this means that i essentially have to deal > with 1000s of > tables/files... > > -bruce > [EMAIL PROTECTED] > > > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
