AW: SQL / DB2 and need for "Index Rebuild" or RUNSTATS

Hi,

and if it's a SQL index would result in 64K pages too -- a real boon to

performance, even from HLL IO.

Did you know, in release V5R4 the page size of an SQL index AND a DDS
described logical file can be set at creation time to any page size between
8K and 512K?
But the default values for page sizes stay untouched, i.e. 8K for DDS
described logical files and 64K for SQL indexes.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok) 



-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Walden H. Leverich
Gesendet: Friday, January 19, 2007 18:03
An: Midrange Systems Technical Discussion
Betreff: RE: SQL / DB2 and need for "Index Rebuild" or RUNSTATS

Indexes are maintained as the underlying data changes and with binary

radix

tree indexes the tree is always optimized, i.e. it is not necessary to 
reorganize indexes or keyed logical files.

I'd be curious to see any technical documentation on how the tree is always
optimized. It still needs to be a trunk/branch/leaf structure, no? 

Regardless, a rebuild, preferably as a SQL index, not a DDS logical (see Dan
Cruikshank's "iSeries Database Reengineering" PDF) would result in physical
storage optimization, and if it's a SQL index would result in 64K pages too
-- a real boon to performance, even from HLL IO.

-Walden