RE: help with fragmentation scheme

Floyd, If you fragment on a range expression like you have below, I am pretty sure that you have issues with fragment elimination. It's only my opinion but if there isn't a performance problem, then I'd just round robin it across multiple spaces. I suspect that the expression you have below would hit sometimes and cause slow performance other times - finding out when could be difficult.. Jarrod ________________________________ From: informix-list-bounces@iiug.org [mailto:informix-list-bounces@iiug.org] On Behalf Of Floyd Wellershaus Sent: Tuesday, 27 October 2009 3:13 a.m. To: informix-list@iiug.org Subject: help with fragmentation scheme We have to fragment a table now because of nearing the page limit size. Yes we could just change the page size but think at 240million rows, it's probably a good thing to fragment the table anyway. Most queries join that table to other tables based on the token and joined to another field(stprofil_token). The other field has values that are spread througout the token range. So if we fragmented on the token field, it would be good to eliminate the proper fragment, but that would have to happen many times until it found the right record that contains the token/stprofil_token value. So would the best thing be to try and find a good split of data between those 2 fields ? Like see if I can fragment with an expression like: token <=x and token >y and stprofil_token <=a and stprofil_token > b ?? Thanks. floyd