Hi folks,
As part of a migration operation, we have an opportunity to move tables and lobs to new tablespaces.
This is in part for defrag operation and other reasons.
The current initial extent in our tablespaces is 65k.. Doesn't seem much...
Ive always believed that indexes benefit from larger extent sizes.
Is the same true for our tables and lobs?
Should I suggest that we increase the INITIAL/NEXT extent sizes of the migration tablespaces to 1M?
Unfortunately there is no capacity planning and instead Im looking for a more 'general rule of thumb'.
Otherwise I'll just create the new migration tablespaces with the same INITIAL/NEXT extent sizes as is current to be safe.
Any thoughts or advice very much appreciated.
Thanks,
jd
TABLESPACE CREATION SYNTAX
CREATE TABLESPACE DATAOWNER_TABLES
DATAFILE '+N11DSM_D_DATA' SIZE 5G
REUSE AUTOEXTEND ON
NEXT 1M
MAXSIZE UNLIMITED
EXTENT MANAGEMENT LOCAL
UNIFORM SEGMENT SPACE MANAGEMENT AUTO; <-- any reason why ASSM should not be used?