Re: ? on alter tablespace pctincrease

And with Oracle 8.1, life is even easier, you just declare the tablespace to be locally managed with uniform size (suitably chosen) and forget the whole issue.

--

Jonathan Lewis
Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk

Connor McDonald wrote in message <38002E2C.61FB_at_yahoo.com>...
>
>If you size your objects well - you DON'T need to coalesce free space.
>
>For example, lets say you size all tables in your tablespace to be
>either 1m, 5m or 50m. As extents are freed up for either tables
>shrinking or being dropped altogether, the probability of another object
>being able to fit into the free space is quite good.
>
>Optimal is to have a tablespace for each size. Then you never have
>holes that cannot be filled. Thus you may have tablespaces like:
>
>DATA_BIG default storage 1m
>DATA_MEDIUM 5m
>DATA_SMALL 50m
>
>you don't need to coalesce, you don't need to worry about fragmentation
>because everything just slots neatly in to the gaps...
>
>Thats a lot of admin overhead resolved...!
>
Received on Sun Oct 10 1999 - 08:42:38 CDT