Well, you usualy split your data in tables for a reason, because some data in mulitple numbers are associated to one, or multiple data.
In your case, if you have one address and contact per customers, then make it one table. If you have an unknown numer of contacts and numbers per customer, then make multiple tables. The joins will be on the primary keys (they should be at least). so it should be fast, even with 2 million records. On Saturday 03 November 2001 07:06 pm, florian wrote: > hello! > > im storing pretty big amounts of customer data in a mysql databases. > its about 2 million rows. what im wondering about now is, how does mysql > perform joins on such amounts of data? > > i was planning to split the info in at least 3 tables: a general > customer table, > a address table, and a contact table. since also other needs than > just customers, > for storing addresses and contacts. > > would it perform better though to store all that in one single table or is > is it okay to split it up in 3 and join them later then, depening on > what information > is needed? > > > thanks alot. > > florian --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
