Temp dbspace sizing

Currently I have 4 temporary dbspaces @ 100M each. I'm in the process of reorganizing my system, so I'm paying a bit more attention to updating my dbspace sizings. A while back, I started encountering errors in my update statistics routines; a few update stats SQLs were erroring out due to a lack of temporary space. As a workaround, I've set PSORT_DBTEMP within my update stats script. No problems since. Since this is the only area that would tax my smaller temporary dbspaces, would it be worth the time to shuffle data around and resize them (once I get an idea of how much space I'd need) or would the benefit gained not justify the time needed? Even though my tables may be relatively large, temp space hasn't been utilized much when I've recreated indices. Just looking for a few good opinions. 8-) -- John Carlson Informix DBA WHSmith USA #include std_disclaimer.h /* These are my opinions, not my company's opinion */