Re: What is a good blocksize to use.

I think the "in the right circumstances" is the really big point - there are many features of Oracle which vary from good to poor to terrible depending on the whether you've managed to use them in the right place at the right time.

Given the details that Ben Brugman has supplied so far for this particular case I __suspect__ that an index structure (any index structure, not just an IOT) on the client_id is going to degenerate quite badly because of the data split across clients. It is likely (but something to check) that a significant number of leaf blocks will take a 50/50 split and the lower block will remain half empty. But it's the nature of the data - combined with the design of the feature - that introduces the side-effect.

--
Regards

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

Next Seminar dates:
(see http://www.jlcomp.demon.co.uk/seminar.html )

____USA__________November 7/9 (MI), 19/21 (TX)
____England______November 12/14

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








Howard J. Rogers wrote in message
<9j4l9.41244$g9.118420_at_newsfeeds.bigpond.com>...


>Dunno. In the right circumstances, and especially with 9i, they can be

>excellent.

>

>Their maintenance costs are high (being a b*tree structure). But if you

>primarily access via primary key, I think they're a good solution.

>

>Regards

>HJR

>