RE: Q about autoextent tablespaces and performance

<span style='font-size:

10.0pt;font-family:Arial;color:navy'>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.

<span style='font-size:

10.0pt;font-family:Arial;color:navy'> 

<span style='font-size:

10.0pt;font-family:Arial;color:navy'>You could always ask them to give you an idea (perhaps give them a query to run before exporting) of he size of the data and indexes.

<span style='font-size:12.0pt;

color:navy;mso-no-proof:yes'>"Do not criticize someone until you walked a mile in their shoes, that way when you criticize them, you are a mile a way and have their shoes."

<span style='font-size:18.0pt;

font-family:"Comic Sans MS";color:navy;mso-no-proof:yes'>Christopher R. Spence<font color=navy>
<span

style='font-size:10.0pt;font-family:"Comic Sans MS";color:navy;mso-no-proof: yes'>Oracle DBA<span style='color:navy;
mso-no-proof:yes'>
<span

style='font-size:10.0pt;font-family:"Comic Sans MS";color:navy;mso-no-proof: yes'>Phone: (978) 322-5744<span
style='color:navy;mso-no-proof:yes'>
<span

style='font-size:10.0pt;font-family:"Comic Sans MS";color:navy;mso-no-proof: yes'>Fax:    (707) 885-2275<span
style='color:navy;mso-no-proof:yes'>

<span style='font-size:10.0pt;

font-family:"Comic Sans MS";color:navy;mso-no-proof:yes'>Fuelspot<font color=navy>
<span

style='font-size:10.0pt;font-family:"Comic Sans MS";color:navy;mso-no-proof: yes'>73 Princeton Street<span style='color:navy; mso-no-proof:yes'>
<span

style='font-size:10.0pt;font-family:"Comic Sans MS";color:navy;mso-no-proof: yes'>North, Chelmsford 01863<span
style='color:navy;mso-no-proof:yes'>
 

<span

style='font-size:10.0pt;font-family:Tahoma'>-----Original Message----- From: Schoen Volker
[mailto:v.schoen_at_inplan.de]
Sent<span
style='font-weight:bold'>: <st1:date Month="10" Day="5" Year="2001"><span style='font-size:10.0pt;font-family:  Tahoma'>Friday, October 05, 2001<font size=2 face=Tahoma> <st1:time
Hour="13" Minute="10"><span style='font-size:10.0pt;  font-family:Tahoma'>1:10 PM<span
style='font-size:10.0pt;font-family:Tahoma'> To: Multiple recipients of list
ORACLE-L
Subject: Q about autoextent
tablespaces and performance

<span

style='font-size:12.0pt'> 

<span style='font-size:

12.0pt;font-family:Arial'>Hi list,

<span style='font-size:

12.0pt;font-family:Arial'>I need some opinions about following question.

<span style='font-size:

12.0pt;font-family:Arial'>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 now how much space I need for those imports. My solution is to create tablespaces with about 50 MB and set autoextent on (localy managed). I import the customers data first time and tablespace may use 200 mb. After some weeks I get the next export. After import, tablespace growth to 300 mb.

<span style='font-size:

12.0pt;font-family:Arial'>So now my question, is it better to create a large tablespace, because of continouges db and hdd blocks, or does this have no influence or small influence on performance. I prefer to build small tablespaces with limited autoextent option. Reason is, that my cold backups were quicker, cause I do not have to reserve a lot of unused space for my tablespaces.

<span style='font-size:

12.0pt;font-family:Arial'>I have databases on Suse Linux, NT4 and W2K. This question is for all platform. If there are some platform specific issues, please let me know.

<span style='font-size:

12.0pt;font-family:Arial'>Hope you understand my question.

<span style='font-size:

12.0pt;font-family:Arial'>TIA

<span

style='font-size:12.0pt;font-family:Arial;color:black'>Volker Schoen

E-Mail:
<span

style='font-family:Arial'>mailto:v.schoen_at_inplan.de http://www.inplan.de

<span

style='font-size:12.0pt'>  Received on Fri Oct 05 2001 - 12:12:05 CDT