Re: Create table statement, weird behavior...

120 extents isn't a big issue, and LMTs
with uniform extents are a good idea.

I tend to prefer a slightly smaller limit and define a few different classes of
tablespace with different sizes of
uniform extent - like 128k, 1MB, 8MB
64MB, 512MB and then put an object
into a tablespace where it will collect
a couple of dozen extents. If I pick
the wrong tablespace one way
either side I feel embarrassed that
my estimates were poor, but not
sufficiently worried to make a fuss
about moving it.

--
Jonathan Lewis
http://www.jlcomp.demon.co.uk

Author of:
Practical Oracle 8i: Building Efficient Databases

Next Seminar - Australia - July/August
http://www.jlcomp.demon.co.uk/seminar.html

Host to The Co-Operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html



Jim wrote in message ...


>Johathan,

>

>   Great site, very helpful link, thankyou...

>

>   This is 9i, your link suggest the preference of LMT's.  Should I just

>leave well enough alone?  I have 1 table with over 120 extents.  Would I do

>better to make it "Dictionary Managed"?

>

>Thanks..

>

>Jim

>

>"Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk> wrote in message

>news:1020887349.24761.0.nnrp-08.9e984b29_at_news.demon.co.uk...

>>

>> Is tablespace DATA a locally managed tablespace ?

>> If so see

>>     http://www.jlcomp.demon.co.uk/ch_08.html

>>

>>