Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Thu, 24 Feb 2005 @ 12:54:04 GMT

  <Prev Next>   <<First <Prev Next> Last>>  

Subj:   Re: TABLE Current Perm not updated after running DEFRAG or PACKDISK
From:   Meade, Cornelius

I think you may be mixing two different concepts.....CURRENT PERM is a measure of the amount of physical space consumed by your user data. That value would not be expected to change regardless of how fragmented that data might be physically spread in the available PERM storage. Think of it this way, first assume your user data consumes exactly 10 cylinders worth of space. If you're using every 10th cylinder up to 100 or just the first 10 in a contiguous fashion, the overall amount of space you are using is still 10 cylinders worth.

FSP is the measure of fragmentation. If you are looking to achieve PERM space reductions then maybe COMPRESSION is what you're looking for.....

Cornelius Meade III
EDS - Consulting Services/BI/CRM

  <Prev Next>   <<First <Prev Next> Last>>  
  Top Home Privacy Feedback  
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 15 Jun 2023