Question about SumIndexFields and Keys

serdarulutas
serdarulutas Member Posts: 50
edited 2009-12-30 in NAV/Navision Classic Client
Hello all,

I have a simple question about SumIndexFields.

I have secondary key that has a SumIndexField. One of the fields in the secondary key is a unique integer that is incremented by one. The integer field is unique per record (and it is not the primary key).

Sample: Imagine your primary key is Document No., and Line No. and you have a unique Integer field (such as "Entry No." that is a part of the secondary key).

Why I have this field: I want to be able to say this:
Rec.SETFILTER("Entry No.",'>5255');
Rec.SETFILTER("some other filter");
Rec.Calcsums("sumindexfield");

I am not sure if I should be concerning about performance because of this unique field. Would I be forcing Navision to create one SIFT entry per record in the original table?

Thanks

Answers

  • kriki
    kriki Member, Moderator Posts: 9,121
    Yes, you will have 1 SIFT-record per record in the table.

    On SQL, it might be useful for performance anyway. SQL needs to read all the record anyway, but the records will be smaller (the SIFT-table [or indexed view] will contain only document no,line no.,entry no and the amount field(s). It will NOT contain the other fields, thus SQL needs to read less data to get the info.
    But writing will be slower because the extra index has to be maintained.
    Regards,Alain Krikilion
    No PM,please use the forum. || May the <SOLVED>-attribute be in your title!

  • serdarulutas
    serdarulutas Member Posts: 50
    Thanks kriki.

Categories