Re: Storage parameters

For Dictionary managed tablespace using initial = next with pctincrease =0 is a good plan providing you can move the very large and very small objects into tablespaces designed to hold object for the extent size chosen.

Being that you are going to migrate the data to a new tablespace in two months I would not go to alot of work now resizing everything but would instead just verify each object has a realistic next extent size and proper setting of pctincrease, that is 0. The exception is if by reloacting and resizing objects now you would be getting the object ready for how you intend to store it on the new database.

Locally managed tablespaces are very nice. I like uniform extents especially for large objects. We divided all our tables/indexes into small and large and built the correct number of tablespaces to hold eveything with room to grow. Space management consists of counting the number of free exents left in the tablespaces every week.

We use autoallocate for a couple of tablespace that house vendor products that lump everything into one tablespace.

HTH -- Mark D Powell -- Received on Thu May 05 2005 - 14:31:19 CDT