Gee, quick answers to complex questions. Ok.

1) auto. (but auto can be uniform no?).
2) # of extents is not a consideration in query performance in my
opinion.
3) Depends. Especially good if in a data warehouse environment. The
point being how much you want to scoop up during any one pass. OLTP
probably wouldn't make much difference.
4) Transportable tablespaces.

Other than trying to write pages on the subjects, there is at least an
answer.

Joel Patterson
Database Administrator
joel.[Email address protected]
x72546
904 727-2546

-----Original Message-----
From: Claudio Alonso -Oracle DBA
[mailto:oracledba-ezmlmshield-x57222683.[Email address protected]
Sent: Wednesday, November 01, 2006 10:16 AM
To: LazyDBA Discussion
Subject: Performance and extents -again

I'm sorry to insist...
Please, are there any answers for these questions?
Thanks again,

--Claudio

1) I would like to know if you recommend to use uniform extent sizes or
auto
allocation for this (I'm not familiar with the last one, which seems to
be
used in this installation).

2) Do you consider that a few bigger extents (with size multiple of the
multiblock read size) would lead to better query performance than a lot
of
small extents?

3) Would it be good to use a tablespace with bigger block size for the
bigger
tables? (let's say 16k, 32k or 64k against the original 8k).

4) What would be the recommended way to move a table and it's indexes
and lobs
from a group of tablespaces to another group of tablespaces (let's say
from
DATA8K, INDEX8K and LOBS8K to DATA32K, INDEX32K and LOBS32K)


--Claudio
PS: Remember I'm using 9i.



---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html



Oracle LazyDBA home page