Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 270 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
NAV2015 CALCSUMS on Temporary Tables with/without SIFT
ILME
Member Posts: 23
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?
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
Best Answers
-
Options
bbrown
Member Posts: 3,268
A CALCSUM on a temporary table is just going to sum the individual records. Since there will be no SIFTIndex (indexed view) to provide the usual supporting summary data.There are no bugs - only undocumented features.5 -
Options
Marije_Brummel
Member, Moderators Design Patterns Posts: 4,262
NAV is not using TEMPDB explicitly for Temp Tables. Everything is in memory of the service tier.
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?5
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