Re: Maximum of Columns in one table (9i)

Jaap W. van Dijk <j.w.vandijk.removethis_at_hetnet.nl> wrote:

>>> 1000 columns maximum

>>Per sane design 40-50 column max. Above that number it is time to
>>get someone to critique your design.

>Isn't the required number a functional issue? If an entity has more
>than 40 attributes what am I to do in your opinion? Surely not design
>more than one table with one-to-one relations just to keep under your
>limit?

People (and some of the "heavy hitters" of this ng) over the years have built up "rules of thumb". When they see them being broken, they wonder as to why.

If the OP comes back here and gives compelling reasons as to why his table requires more than 50 attributes, then maybe people here will go "hmmm, yes, I think that in this special case, you could be right". But, until he does, I'll stick with my rule of thumb!

Paul...

>Jaap.

-- 

plinehan __at__ yahoo __dot__ __com__

XP Pro, SP 2, 

Oracle, 9.2.0.1.0 (Enterprise Ed.)
Interbase 6.0.1.0;

When asking database related questions, please give other posters 
some clues, like operating system, version of db being used and DDL.
The exact text and/or number of error messages is useful (!= "it didn't work!").
Thanks.
 
Furthermore, as a courtesy to those who spend 
time analysing and attempting to help, please 
do not top post.