Table/Index Storage Parameter

[Kumud]

Our system is going to production and I created table/index creation script with storage parameter.
According to our DBA in 9i we should not define storage parameter oracle will automaticaly take care.
Is this true ? we have heavy data laoding data warehouse.
What is your experience in 9i for performance gain should we define appropriate storage parameter for table and index creation ?

[slimdave]

Which parameterts are you referring to? I wrote a brief article on storage parameters for DW environments here ... http://databasejournal.com/features/...le.php/3304791 ... which might help.

You certainly shouldn't be specifying initial, next and pctincrease, if you are referring to those, whether in a DW or an OLTP environment, but this applied back in v7, as well as in 8i, 9i, 10g.

[Kumud]

I am talking about initial and next parameters. I have gone through your article it does not say about it.
Shell we create tables/indexes with initial and next parameters in 9i for better performance ?

[davey23uk]

no need as long as you are using LMT's with either uniform extents or autoallocate.

[DaPi]

The "leaf blocks" of Slim's articles don't point to each other - you have go via a "branch block" to find the others. #1 is the one you want http://databasejournal.com/features/...le.php/3113551