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

Following up on dias, 09 Mar 2003:

>
> Well, to conclude, dont' use tables with a large number of columns
> because of performance issues and bugs.

Say what?

>
> How Oracle chain rows depend on the average row length:
> - If a the rows are small, Oracle will store several rows in a block,
> there will be logical chaining, no problem !
> - If the rows are larges and if one row don't fit in a block, there
> will be chaining accross blocks, logical !
> - If rows are small enough to fit in a block, but the size are almost
> the size of the block, Oracle will store juste one row in a block !!!!
> Oracle will always store all the pieces (a piece = 255 columns) of a
> row in the same block.

Keh?....

>
> About bugs, the first one (and it's not the last), you can't use
> dbms_stats against a partitionned table with more than ~ 200 columns.
> Bug 2603036.
>

Duh?

-- 
Cheers
Nuno Souto
wizofoz2k_at_yahoo.com.au.nospam