Re: Locally managed tablespaces and migrated rows

On Mon, 07 May 2001 16:17:24 GMT, nsouto_at_nsw.bigpond.net.au.nospam (Nuno Souto) wrote:

>Yeah, good point. Fact is: with LMTS and uniform allocation, all
>extents are same size. That doesn't automatically match every
>situation. There are many instances in PS where one knows certain
>tables are gonna be empty or nearly, so they should have a much
>smaller extent.

The simple solution of course is to have table spaces defined for different size tables, i.e. a table space with uniform size 64 KB, another with 1M and another with 100M a.s.o.

If a certain table grows more than anticipated it can relatively easy be transferred to more appropriate table space. The extents freed in the old table space will be used efficiently to new extents for other tables. The DBA still have some planning and surveillance to do, but fragmentation of free space can really be a memory from the old days.

Yours Hans Erik Busk
tbf_at_cn.stam.dk Received on Tue May 08 2001 - 00:55:54 CDT