Re: DB2 HADB

Mark A apparently said,on my timestamp of 26/11/2005 9:48 AM:

>>
>>DB2 clustering only "tries" to insert the row on the correct page (never 
>>rearranges rows on the page like an index), and if the correct page or a 
>>nearby page is not available, then it doesn't waste time with page splits 
>>(just puts the row anywhere). The area on a page used for inserting new 
>>rows is different on Oracle compared to DB2, and a reorg restores the free 
>>space percent (as specified when the table is created) on each page for 
>>new inserts in when a clustering index is defined.

You know: that is one of the best descriptions of good old VSAM multi-index file structure I've ever heard. I'm surprised that dinossaur is still used as a storage technique by db2. But what the heck: there's gotta be a market for it...

>
> Correction:
>
> it does provide a definite performance enhancement WITHOUT the extra
> overhead
> of an index ordered table in Oracle.
>
>

Yeah, I got it Mark. No worries. Hence why I did't comment on it.

-- 
Cheers
Nuno Souto
in sunny(at last) Sydney, Australia
wizofoz2k_at_yahoo.com.au.nospam