I think ideally you want to use the smallest pagesize possible to get the
highest hit ratio on the bufferpool.
(since rows are hot, but not necessarily entire pages)
The direction that I'm seing though is that teh benefits are comparatively
small, so the movement is towards having as few pagesizes (max 2) as
possible to simplify management.
So if all you tables fit on 4K use 4K if 90% of your tables fit on 4k and
10% need 8k, use 4k and 8k.
If it's a mix, don't bother and make them all 8K.
Unless you have soem really narrow tables which would mean your pages half
empty of course....

Just my two cents. I'm no expert in that area.

Cheers
Serge



"Michael Bell " <db2udbdba-ezmlmshield-x97802322.[Email address protected]
wrote on 10/25/2005 03:53:49 PM:

> Is there an optimal number of rows / page for a transactional table? I
> know there's a 255 row/page limit, but what guidelines are there
> regarding rows/table and fill factor? We have over 1,000 tables, so I
> don't have time to optimize each one of them.
>
>
>
> Thanks,
>
> Mike
>
>
>
> ---------------------------------------------------------------------
> PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
> website: http://www.LazyDBA.com
> To unsubscribe: http://www.lazydba.com/unsubscribe.html
>


DB2 & UDB email list listserv db2-l LazyDBA home page