R
Richard Banville
Guest
Yes, create and toss limit should be set correctly during the load process. They are created in one step with their final size, right ? - Yes Why the load behave differently with Create limit set to 32 compared to default 150 - Create limit is the amount of space that must be available in the block after a record is created. This is typically reserved for record expansion in the future. By decreasing this value, during the load you were able to insert an additional record in some of these blocks giving you a higher packing but with the drawback that if any record were updated in the future requiring more than 32 bytes of additional space it would fragment. (This is 32 byte of reserved space for updates of records in the block - not per record per block). Assuming that these records will never grow, setting it lower as you did is a good idea, but after the load I would set it higher once again. However, and increase in these existing records in the future would yield very bad performance so you really need to be careful with solving the issue in this way. That is why I mentioned toss limits is the way to go.
Continue reading...
Continue reading...