You have not said what type of information you will be storing in this database. Is it going to be just faculty information? Even if it is just faculty information, you do realize that each school treats departments a bit dfferently. The faculyt maybe under different school, may specialize in certain field(s). What about all those data? Or are you going strictly for First, Last, College type simple scenario?
On 7/7/05, Daniel Kasak <[EMAIL PROTECTED]> wrote: > bruce wrote: > > >even though this might mean i get a table with 5 million records??? as > >opposed to say a 1000 different tables, each with 50,000 records? > > > >-bruce > > > > > That's right. > Databases are made for this sort of thing. > If you have a separate table for each location, constructing queries to > pull data from a number of them at once will be an absolute nightmare, > not to mention what will happen if you have to modify the table structure. > For example, what do you do if you want to see all records that were > entered yesterday? You run 1000 separate queries! You can bet that this > will be slower than if everything was in 1 table. > Seriously, put everything in 1 table. > > -- > Daniel Kasak > IT Developer > NUS Consulting Group > Level 5, 77 Pacific Highway > North Sydney, NSW, Australia 2060 > T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 > email: [EMAIL PROTECTED] > website: http://www.nusconsulting.com.au > > -- > 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]
