Re: Extents

You are correct in that if the goal is to minimize the # of extents one needs to know the growth history. But you don't have to do that. Use locally managed tablespaces and make the sizes uniform. If you want to go further have three sizes small uniform, medium uniform, and large uniform. Where small is at least 128K uniform extents. Then you don't have the dictionary management overhead for extents.(allocation is fast, a bitmap in the first 64K of the datafile)

Jim

"Kevin McDaniel" <kmcdaniel96_at_home.com> wrote in message news:9c966595.0111211353.70e0617b_at_posting.google.com...
> Please help me understand something: How is it not important to know
> WHEN or HOW OFTEN an extent is thrown? It seems that a DBA's focus is
> on how many extents and the size of the next extent. But when trying
> to decide if you need to adjust the next extent (in order to minimize
> the total number of extents for a segment), doesn't one need to now
> how often or at least when the segment extends? I've tried looking
> for a value being captured in the DBA_ views but no luck. I'm still
> "green" as a DBA, so I realize I may be overlooking something, or
> heading down the wrong path on this issue. But I'd certainly
> appreciate someone correcting me if I am wrong. I can't seem to find
> any information on this issue, which leads me to believe I'm chasing
> my own tail.
Received on Wed Nov 21 2001 - 16:36:41 CST