Hi,
I would like to have an opinion on this one:
In a NAV2015 implementation, I am using CALCSUMS on a couple of fields F1, F2 of a table that I have made Temporary.
This code is inside a REPEAT UNTIL loop that will be executed many times.
1) What do you think is the best practice: To add the F1, F2 fields in the SumIndexFields of the according key or not? (now that in 2015 I don't get the runtime error)
2) Is there a differentiation between usage of CALCSUMS on a Temporary table and a permanent table? Does it work differently for Temp tables?
* IF NOT done THEN REPEAT UNTIL done *
0
Answers
1) If there is the chance that you have to backport it, add the sumindexfields.
2) No idea. I think the index is in the tempdb.
with best regards
Jens
No, I will not have to backport it, this is in a new NAV 2015 development.
It seems a good idea to me to include in SIFT to get faster calculations, but I don't know
if there's any different behavior from the recommended, just because my table is Temporary.
If somebody knows any issues that make Temporary tables CALCSUMS perform differently than standard,
I'd be glad to hear it and take it into consideration.
Makes sense what you're saying.
So I guess this means there's no reason to add the fields in the SumIndexFields for this purpose,
because I will not get the desired effect from SIFT functionality.
We did talk with MS about TempDB. It might releave the service tier from heavy memory consumption and it will also allow us to use SIFT on temp tables.
So far there are no plans to make this happen.
Feedback?
So until MS does it, it seems that it's not really a valuable practice to use SIFT for CALCSUMS on Temp tables