With relational database design you can more then likely break that 75
column table down into many different tables. Look up information on NORMAL
FORM this will help you design an effective database. Usually from what I
know and have been taught 3rd normal form is as low a level as you want to
go. But this also depends on things such as how large your db will be.
Sometimes redundant data is not always a bad think. In that case a lower
normal form would be fine too. Its an art not a science:)
RH
-----Original Message-----
From: Richard Reina [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 11, 2001 1:26 PM
To: [EMAIL PROTECTED]
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
