Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 305 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
SIFT Levels List
Yuri
Member Posts: 16
Hi!
Recently I begun to analyze keys of some large tables, and occasionally I discovered one interesting form "SIFT Level List"
(You can find it by this way: Open table for design -> View Keys->Show columns (SIFT Levels To Maintain))
Does anybody know the practical meaning of this form?
Best regards, Yuri
Recently I begun to analyze keys of some large tables, and occasionally I discovered one interesting form "SIFT Level List"
(You can find it by this way: Open table for design -> View Keys->Show columns (SIFT Levels To Maintain))
Does anybody know the practical meaning of this form?
Best regards, Yuri
0
Comments
SQL does not have such a thing as SIFT technology. Therefore the flowfields are implemented through a set of tables based on the number of levels that you just saw.
So for each level you have say for a key in Cust. Ledger Entry table the SQL server will maintain an internal table in which will insert/ update/ delete data everytime a record is inserted/deleted/modified in Cust. Ledger Entry table.
The levels you have will allow you to trade off reporting speed with database transaction speed. It is recommended to turn off any level you do not need ... If a level is turned off and you report on it the system will calculate it on the fly which obviously will not be as fast as if it was precalculated ...
This is a very crude explanation and if you get your hands on the Navision and SQL documentation it explains it there much better than I can ever will.
Hope this helps.
Cristi Nicola