Closed Teming closed 2 years ago
Why do you need them there?
There is no need for SIFT on primary key, we even have special code cop rule to prevent it.
Some elaboration on why not would be nice - the warning could link to the relevant BC page, which should be updated with info on why it's not useful anymore - I guess because the Classic database engine benefited from SumIndexFields on PKs but SQL Server for some reason does not. I can't quickly find any info on why this isn't needed/desirable anymore. It would be nice to.
Record selectivity on PK index and amount summary (number of records that is calculated from) are identical. And SQL can do SUM on PK by scan quickly. You could define SumIndexFields but you should set the SIFTMaintanance property (or how it is called) to false value.
From NAV 14, we could see several SumIndexFields for the primay key of Service Line table 5902. It seems that they are missing for the later BC versions.
NAV 14.
BC 19 for the same table -
Is it possible? Thanks very much.