Re: What is a good blocksize to use.

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 "Ben Brugman" <benbrugman_at_onbekend.nl> wrote in message news:3d940861.688046_at_news.nl.uu.net...
>
> >
> >Ben,
> >
> >For the Oracle implementation, I'd suggest:
> >1) Forget about IOTs. Just put an index on the client_id.
>
> This confirms the general feeling that you should not use IOT's.
> But (Sorry for the But) :
> In MS-SQL-server the clustered table is very similar to the IOT's in
> Oracle. (There is no row-id in MS-SQL-server so all indexes point to
> the clustered key value. Oracle has a row Id but for IOT's is can
> become a approximate row id.)
> In MS-SQL-server the clustered tables work very wel for our type
> of applications.
>
> Why do so many people advice against IOT's ?
>
> ben
> (Trying to make decisions before the application is build, or a
> complete set of data is available, based on knowledge about
> the internal workings of more than one RDBMS).
>
> >2) Analyze your schema, with compute statistics.
> >3) Forget about block size, for the time being at least.
> >
> >Hope this helps.
> >Paul
> >
> >
> >
>
> Ben Brugman
Received on Fri Sep 27 2002 - 16:52:48 CDT