I would personally suggest they be broken up. I've noticed in the past some
speed issues when you have too many columns.
----- Original Message -----
From: "Richard Reina" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 11, 2001 11:26 AM
Subject: Hom many columns is too many?
> I am designing an in house database app. for sales/contact management.
> We've identified out about 75 things to know about a customer/contact
> from there name all the way to where they went to highschool. Should
> all these attributes be in one table since they all describe the contact
> or should they be broken up into seperate tables like education,
> professional backround, business backtound special interests?
>
> ---------------------------------------------------------------------
> 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
>
>
>
---------------------------------------------------------------------
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
