efined as fixed size (in
this case you would add another datafile to the tablespace) or
autoextending (where the datafile increases in size whilst there is
physical space on the drive).
Hopefully this gives you a start to how Oracle uses the storage clause.
I've skipped a lot of details, li
...
can somebody help in sizing the table/index using the storage clause ? what
r the key values to check and how to calculate the table size & the related
storage parameters ? how does it change from an OLTP appln to a
Datawarehouse ?
lets say for the table "emp" :
Nam
ld add another datafile to the tablespace) or
autoextending (where the datafile increases in size whilst there is
physical space on the drive).
Hopefully this gives you a start to how Oracle uses the storage clause.
I've skipped a lot of details, like the impact of PCTINCREASE so take
February 20, 2003 3:19 PM
To: Multiple recipients of list ORACLE-L
Hi Gurus ...
can somebody help in sizing the table/index using the storage clause ? what
r the key values to check and how to calculate the table size & the related
storage parameters ? how does it change from an OL
128m extent
size.
Dennis Williams
DBA, 40%OCP, 100% DBA
Lifetouch, Inc.
[EMAIL PROTECTED]
-Original Message-
Sent: Thursday, February 20, 2003 3:19 PM
To: Multiple recipients of list ORACLE-L
Hi Gurus ...
can somebody help in sizing the table/index using the storage clause ? what
r th
Regarding the storage clause, you might get a number of replies saying to use locally
managed tablespace, so let me start.
By now you should be using locally managed tablespaces with uniform allocation or
automatic allocation depending on circumstances.
Here is a link to more info...
http
Hi Gurus ...
can somebody help in sizing the table/index using the storage clause ? what
r the key values to check and how to calculate the table size & the related
storage parameters ? how does it change from an OLTP appln to a
Datawarehouse ?
lets say for the table "emp" :
Nam
