Re: Storage Clause Problem

Without really having transaction info. The table has probably had quite a few transactions, followed by deletions and the residue is then dispersed throughout your table. To be sure perform, compute stats will then give you the average per row by the no. of rows = actuel space used
Then select the number of records per block based on the rowid. You should see that certain blocks have very few rows (0 rows). This will show the varying data spread as a result of the transactions. Peter

Matthew, MacFarland wrote:

> Hello everyone,
>
> I have a table with 600 rows that has grown to 22 extents (44megs). The
> data in the long column of the table is about 300 bytes in each row. The
> initial and next extents were set to 2meg so I cannot figure out how the
> table got so big so fast.
>
> Do you see anything wrong with the ddl below that could be causing this? I
> am really not sure about the pctused and pctfree.
>
> Thanks,
>
> Matthew MacFarland
> Dril-Quip
> matthew_macfarland_at_dril-quip.com
Received on Thu Sep 24 1998 - 16:23:05 CDT