Columns on a table

19 Jan 2006 8:20 PM

millner,kim

I am a new programmer.

Is it always a good idea to put columns on a seperate table which are not
updated very often and very big in size.
Likes Customer notes.
Is is good idea to put notes on a another table with Customerid as the key.

Kim

19 Jan 2006 8:43 PM

W.G. Ryan - MVP

Kim -I think you are referring to normalization and there are exceptions to
the rule and you can go overboard, but as a rule, normalization is a good
thing. But it's a complex issue and not a panacea. There are times where
it's not optimal and denormalization is advised. But that means following
specific rules of denormalization - not just willy nilly sticking columns in
a big table. Google on normalization, E.F. Codd and I think you'll find
tons of answers.
Show quote

"millner,kim" <kim@noemailcom> wrote in message
news:udNBCXTHGHA.2704@TK2MSFTNGP15.phx.gbl...
>I am a new programmer.
>
> Is it always a good idea to put columns on a seperate table which are not
> updated very often and very big in size.
> Likes Customer notes.
> Is is good idea to put notes on a another table with Customerid as the
> key.
>
> Kim
>