Re: Importing a compressed table doesn't go to smallest suitable free space
From: Ken Friday <ken.friday_at_teldta.com>
Date: 1996/02/18
Message-ID: <4g8d1o$6b1_at_madison.tdsnet.com>#1/1
Date: 1996/02/18
Message-ID: <4g8d1o$6b1_at_madison.tdsnet.com>#1/1
chicnorm_at_norm.inforamp.net (Norm LeBlanc) wrote:
>I am trying to import a table that I had previously exported with the
>compress extents option and I am expecting it to be placed in the
>smallest available contiguous block of free space that it will fit in.
>But this does not happen. Am I expecting too much?
>
>Dinesh Fernandopulle
>
>
My understanding of "compress extents" is that the initial extent storage
parameter is set equal to the sum of existing extents allocated. It does
not adjust for actual data volumes.
Ken F.
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Received on Sun Feb 18 1996 - 00:00:00 CET