D
Dmitri Levin
Guest
With "one size fits all" RPB approach I believe we look at database from only one side, i.e. how to effectively fit records into blocks. And 128 (or 256) RPB is the most likely answer. However if we look at it from the performance side we will see that the choice of a slightly lower RBP will help to avoid record fragmentation. I believe George wrote that "fragmentation happen to the last record that we put into a block". We can avoid/limit fragmentation by putting table into area with lower RPB or probably better approach is to set a bigger Create limit on a table itself. And changing Create limit is much more easy than to move table in a different area. So I am not actually advising to put table into areas with appropriate RPBs to avoid fragmentation, but only pointing out that it could help to avoid fragmentation.
Continue reading...
Continue reading...