Re: max # of columns in the table (again!)

Tanel Poder wrote:

> Hi,
>
> But this case of chaining doesn't usually cause a performance problem,
> because the row is chained to the same block, thus no additional IO is
> needed.
>
> Tanel.
>
> "dias" <ydias_at_hotmail.com> wrote in message
> news:55a68b47.0302150246.3fbd5c04_at_posting.google.com...
> > Hi,
> >
> > I have the answer ... whith a small test
> > It's still the case in 9i.
> > The stats "table fetch continued row" are incremented when a select is
> > made on a table with more than 255 columns.
> >
> > Dias
> >
> >
> > ydias_at_hotmail.com (dias) wrote in message
> news:<55a68b47.0302142315.39934901_at_posting.google.com>...
> > > Hi,
> > >
> > > 1000 columns is the max for a table (8i and 9i).
> > >
> > > Oracle (8i) has an internal limit of 255. That means that if any
> > > columns beyond 255 are not null, that row will always be chained.
> > >
> > > Is this still the case in 9i ?
> > >
> > > Thanks

I think the bigger issue is anyone working with much more than 50 columns in any table. It makes me think that they likely need a course in relational theory and normalization.

Daniel Morgan Received on Sat Feb 15 2003 - 17:39:11 CST