Re: Extents: Less or More?

From: Phil Herring <revdoc_at_uow.edu.au>
Date: 1998/02/02
Message-ID: <6b3bcv$lv$1@wyrm.its.uow.edu.au>#1/1

In article <34d4ded2.0_at_news1.ibm.net> Brian S. Hummer, hummerb_at_usa.net writes:
>[...] But recently, while taking the DBA course at
>an Oracle Education center, I was lead to believe that the number of extents
>for an object doesn't really matter.

That's about right, assuming that you're talking about all the extents being located on one disk (which is not always a valid assumption). There may be a small effect either way, depending on the application, but I don't see how it could be a significant consideration in the majority of cases.

For the record - I *never* compress extents. I've never seen it have any positive benefits, and I have seen it create problems, so my own philosophy is to leave them alone. The only qualification to that is when tables get too close to MAXEXTENTS, but when that happens, I usually rebuild the table with multiple extents and a larger INITIAL and NEXT, rather than forcing the table into one large extent.

Received on Mon Feb 02 1998 - 00:00:00 CST