Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Why is NEXT_EXTENT changing all the time?
I'm sorry if I misunderstood you, but that does not appear to be what you said.
You originally wrote
"for myself, initial extents should
be sized to hold, as near as possible, 1 to 3 years worth of data depending
on
the application. Next extents are generally sized, again depending upon
anticipated table growth, at between 25% and 100% of initial extent size. "
It was this I was disagreeing with. INITIAL should *always* = NEXT. Moreover initial shouldn't be chosen particularly on one years worth of data or whatever, but on the size of the object. There is (these days Walter is quite right about Oracle 6) no need to worry about multiple extents.per segment.
-- Niall Litchfield Oracle DBA Audit Commission UK "Daniel A. Morgan" <dmorgan_at_exesolutions.com> wrote in message news:3A7111D7.50DF4CAE_at_exesolutions.com...Received on Fri Jan 26 2001 - 05:54:39 CST
> > Well now (and hoping that I am reasonable and that the wind is in the
west)
> >
> > I disagree strongly with this suggestion.
> >
> > For me ALL segments within a tablespace should have an identical extent
> > size, and each segment should be allocated to a tablespace with an
> > appropriate storage clause. This way a table which wants to grab a next
> > extent can always do it (providing the tablespace is not full). In other
> > words fragmentation is eliminated.
> >
> > I utterly fail to see why one would size segments at different sizes,
thus
> > guaranteeing fragmentation, merely in order to hold one to three years
worth
> > of data. The only possible 'justification' would be in an environment
when
> > yearly reviews of database operation were the object. That translates to
> > consultancy.
>
> You are absolutely correct. I wasn't dealing with the fact that one should
have
> multiple tablespaces separated by physical device and other tablespaces
> separated by extent sizes to avoid fragmentation. Just dealing with the
thought
> (shudder) that someone would ever set out to make every NEXT EXTENT in a
> database the same size.
>
> Daniel A. Morgan
>
![]() |
![]() |