Is there a identification strategy for candidates with 4K buffer pool to be moved to a bigger buffer pools like 16k, 32k.

Regards
sahana

If you're going to create a tablespace with the page size larger than 4K (tablespace page size and bufferpool page size must be the same)

For each table ask yourself:
- is this row going to fit in the page?
- okay, there are x rows stored in 1 page. All I/O is page-based so I might read (and store in the bufferpool) more rows than I actually require with this specific SQL. Is this behaviour benificial for me?
if OLTP
then the answer might be NO
else the answer might be YES
end-if