Hi. If you have a lot of nulls in CALL.FILE field, you should create this index with NO.NULLS clause.
Regards -- Augusto 2013/4/16 Anthonys Lists <antli...@youngman.org.uk> > Not to say this has anything to do with it, but it sounds like this is a > big file. Does CALL.STATUS just have a few valid values? And when you're > running this report are you selecting a lot of values for one value of > CALL.STATUS? > > It shouldn't mess up, but indexing used to be iffy if you indexed hundreds > of records for a single value of the index. If you're stressing the index > that could be the problem. > > Do you have a "date of appointment" field? Could you index on that? If you > need rapid reports and you could run the report for "appointment == today" > with that indexed, would that give you the fast reports you need? > > Cheers, > Wol > > > On 15/04/2013 22:41, david yu wrote: > >> We did not have any OS or Universe upgrade. >> here is the list.index >> >> >>> LIST.INDEX CALL.FILE ALL >>> >> Alternate Key Index Summary for file CALL.FILE >> File........... CALL.FILE >> Indices........ 4 (2 A-type, 1 C-type, 1 D-type, 0 I-type, 0 SQL, 0 >> S-type) >> Index Updates.. Enabled, No updates pending >> Index name Type Build Nulls In DICT S/M Just Unique >> Field num/I-type >> CALL.STATUS D Not Reqd Yes Yes S L N 13 >> ______________________________**_________________ >> U2-Users mailing list >> U2-Users@listserver.u2ug.org >> http://listserver.u2ug.org/**mailman/listinfo/u2-users<http://listserver.u2ug.org/mailman/listinfo/u2-users> >> >> > ______________________________**_________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/**mailman/listinfo/u2-users<http://listserver.u2ug.org/mailman/listinfo/u2-users> > _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
