Best Extent Size for Locally Managed Temporary Tablespaces

In the old Oracle7 world the recommended practice was to make initial and next extent sizes to be a multiple of SORT_AREA_SIZE plus 1 DB block. I guess the thinking was that if a sort needed to move from memory to disk then it could fit neatly into the next extent.

So lets say:
SORT_AREA_SIZE = 512K and
sort_area_retained_size = 64K

Any ideas for deriving the best extent size for a locally managed temporary tablespace? Or do you think it no longer makes a difference?

Can we "SORT" this out?

Steve Orr
Fremont, CA Received on Fri Jun 16 2000 - 12:46:48 CDT