-
Maximum number of columns in table
All,
I remember, if total number columns reach to N in a table, oracle would not store the record in the same data block. I don't remember the value N. Can any one answer for this?.
Regards
GT
-
Originally Posted by pranavgovind
All,
I remember, if total number columns reach to N in a table, oracle would not store the record in the same data block. I don't remember the value N. Can any one answer for this?.
Regards
GT
1000 max.
"What is past is PROLOGUE"
-
Anything over 255 is chained.
-
David is right its is 255.Over 255 the rows are chained
-
But in this case chained doesn't mean that the data are not all stored in the same block
-
Originally Posted by slimdave
Anything over 255 is chained.
It is not chained. The data of the columns whose number is > 255 is still stored in the same block provided the block has space.
The real problem is "table fetch continued row " event appears in the statspack report.
Oracle has to do 2 IOs (logical) for the data appears after the 255th column even when all the columns data are stored in one block and the row is fetched via index look up.
However, full table scan will not suffer from 2 IOs.
You can have 1000 columns in a table. In my opinion, restrict the number of columns less than 255 and the performance will be good.
Tamil
Tamil
-
Originally Posted by tamilselvan
It is not chained. The data of the columns whose number is > 255 is still stored in the same block provided the block has space.
Tamil
Will the block size 2k ~ 32k has more ~ less impact with the number of I/O's for columns > 255?
"What is past is PROLOGUE"
-
Originally Posted by dbasan
Will the block size 2k ~ 32k has more ~ less impact with the number of I/O's for columns > 255?
The block size does not matter.
Tamil
-
Tamil,
In you answer, you are saying, "row is fetched via index look up".
What does it mean?.
Originally Posted by tamilselvan
It is not chained. The data of the columns whose number is > 255 is still stored in the same block provided the block has space.
The real problem is "table fetch continued row " event appears in the statspack report.
Oracle has to do 2 IOs (logical) for the data appears after the 255th column even when all the columns data are stored in one block and the row is fetched via index look up.
However, full table scan will not suffer from 2 IOs.
You can have 1000 columns in a table. In my opinion, restrict the number of columns less than 255 and the performance will be good.
Tamil
Tamil
-
It's a real learning experience this, ain't it?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|