RE: Hom many columns is too many?

. -Original Message- From: ryc [mailto:[EMAIL PROTECTED]] Sent: Friday, May 11, 2001 4:09 PM To: [EMAIL PROTECTED] Subject: Re: Hom many columns is too many? Just because one table has many columns does not mean it is not normalized. The original message stated that there is all kinds of different

Re: Hom many columns is too many?

Personal data databases often seem to have variable information that doesn't fit all that well in relational databases. For example, multiple phone numbers for different purposes. One thing I'm considering is to have a variable text field that contains XML-encoded data to handle all this

Re: Hom many columns is too many?

On Mon, May 14, 2001 at 03:51:00PM -0700, Gary Bickford wrote: Personal data databases often seem to have variable information that doesn't fit all that well in relational databases. For example, multiple phone numbers for different purposes. Create a table with three columns. (1) And id

Re: Hom many columns is too many?

the way to where they went to high school could be stored in one table logically or more importantly efficiently. -Original Message- From: ryc [mailto:[EMAIL PROTECTED]] Sent: Friday, May 11, 2001 11:58 AM To: 'Richard Reina'; [EMAIL PROTECTED] Subject: Re: Hom many columns is too

RE: Hom many columns is too many?

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

Re: Hom many columns is too many?

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

Re: Hom many columns is too many?

I dont think the problem was redudant data. He is talking about 75 distinct fields that no other table contains and ALL data is related to the contact. It makes sence that a table with more columns would have a higher overhead when parsing the queries, but but other than that I dont _think_

RE: Hom many columns is too many?

[mailto:[EMAIL PROTECTED]] Sent: Friday, May 11, 2001 11:58 AM To: 'Richard Reina'; [EMAIL PROTECTED] Subject: Re: Hom many columns is too many? I dont think the problem was redudant data. He is talking about 75 distinct fields that no other table contains and ALL data is related to the contact

Re: Hom many columns is too many?

:[EMAIL PROTECTED]] Sent: Friday, May 11, 2001 11:58 AM To: 'Richard Reina'; [EMAIL PROTECTED] Subject: Re: Hom many columns is too many? I dont think the problem was redudant data. He is talking about 75 distinct fields that no other table contains and ALL data is related to the contact