Title: Q about autoextent tablespaces and performance
Hi list,
I need some opinions about following question.
I have a developer box with about 20 schemas. Sometimes our customers send us a export of there data which I had to import into our develop instance. My problem is that I don't
Since its only a development instance, I don't think
the autoextend is going to be an issue. Alternatively
you could run 'imp indexfile=y' and add up what you
see in the storage clauses to get an approximate idea
of what space is going to be needed.
hth
connor
--- Schoen Volker [EMAIL
Title: Q about autoextent tablespaces and performance
I generally add about 33% to the size of
the uncompressed export. This gives
me some idea how much space it may take.
Of course, this depends on how many indexes (as they are not stored in
export) and storage parameters on the database
Title: Q about autoextent tablespaces and performance
Accidently hit send before I finished my response...
Anyway, one thing I used to do is give them a CRETAB/CREIDX script and have them run it.
This will allow you to build the table and
indexes ahead of time, and of the size you
