Can someone point me to good reading material on this
subject. Is one better than the other for performance
and manageability?
Syntactically the autoallocate is shorter and seems to
be more hands off (does that mean worry free also?).
TIA
=
Sundeep Maini
Consultant
Currently on
http://technet.oracle.com/doc/oracle8i_816/server.816/a76956/tspaces.htm
-Original Message-
Sent: Tuesday, March 26, 2002 12:54 PM
To: Multiple recipients of list ORACLE-L
Can someone point me to good reading material on this
subject. Is one better than the other for performance
and
Sundeep - Start by reading the classic paper How to Stop Defragmenting and
Start Living at this link:
http://www.dbatoolbox.com/WP2001/spacemgmt/defrag.htm
Actually, autoallocate and uniform extents work very well together. But you
need to understand the concepts behind them first. And make sure
And also Metalink doc 105120.1
Reddy, Madhusudana wrote:
http://technet.oracle.com/doc/oracle8i_816/server.816/a76956/tspaces.htm
-Original Message-
Sent: Tuesday, March 26, 2002 12:54 PM
To: Multiple recipients of list ORACLE-L
Can someone point me to good reading material
Sundeep,
Major differences between AUTOALLOCATE and UNIFORM is the fact that extent
sizes in AUTOALLOCATE tablespace are not uniformly-sized.
I've been working in v9.0.1 (not 8.1.7 -- don't have one of those!) and
noticed the following pattern in non-partitioned tables and
range-partitioned
There's a note on my website in the errata and addenda
to the book, chapter 8, about this. 64MB extents kick in
when the segment has grown to about 1GB.
However, oddities occur all over the place, particularly
when the tablespace has been exercised for a while.
It is possible for Oracle to be
Sundeep
Oops, egg on my face. Reading too fast, seeing one word and thinking
another. My understanding from Stop Defragmenting and Start Living was
that uniform extents was the direction Oracle was heading. The problem with
autoallocate is that you can end up with fragmented tablespaces
Reading descriptions of the effects of Autoallocate leads me to
think that Autoallocate is nothing more than PCTINCREASE redux--a
little less crude, but still no way to manage your space.
Paul Baumgartel
--- sundeep maini [EMAIL PROTECTED] wrote:
Dennis,
I mentioned Autoallocate and not
I heard of it some place. that is try to have three different
tablespaces. One for large table, one for medium size table and third
for small tables. Each of these tablespaces can have their own extent
sizes. Large having large extent size. Medium can have medium size
extents and same for small
