Re: extents

thuc, > WARNING:TBLSpace coris:informix.syscolumns has more than 8 extents this is, as it says, only a warning. if a table has more than 8 extents, it can hurt the performance of the system, but it isn't an error and many tables can exist with much more than 8 extents. if you want to optimize the performance of your system however, you should do what you have described below to take care of this. > I was told by an Informix Consultant to do the followings: > > 1. unload the table to a flat file > > 2. drop the table > > 3. create the table, get the extent size, next extent size, and row > leveling locking. > > 4. load the tape...this willneed to have constraints dropped > and trigger dropped. > > I cant find enough information about that script in any informix manual. > > Is an Informix Consultant right? yes, he is right. there is no script for this, you must do each one of these steps by hand. again, it is worthwhile doing if you have the time to do it. make sure that you set the extent size and next extent size though, that is the whole point of this. although the table will load in one contiguous extent during the load procedure, (unless another process working in the same dbspace grabs an extent right next to the current extent allocated for that table), still you want to set thing up properly. hope this helps. mickm