Re: Informix C-ISAM performance on SCO

> I was wondering if anyone knew of a serious downgrade with Informix > C-ISAM performance once a program hit a certain point while building a > database. I have a program running on SCO Openserver 3.2v4.2 and [and] > 1 key > length 18 > key type is string > no dups > leading and trailing compression > key is not segmented. I don't claim to know anything about C-ISAM, but in general it's better to create indexes *after* you populate a table. Since this is a no dups index, I'm afraid you can't get around that one. :-( The general theory is that the C-ISAM manages the keys in a balanced b-tree and you're getting to a stage where it's probably doing a lot of index reorganising. I'm clutching at straws here, but is there anyway you can write the data sorted or partially sorted, it might help. Is there any reason why you're indexing on a CHAR? This can be very inefficient. Good luck! -- Ciao, Billy +------------------------------------------------------------------------------+ | I used to be indecisive, but now I'm not so sure... | +------------------------------------------------------------------------------+