web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics NAV (Archived) / VSIFT on primary Keys
Microsoft Dynamics NAV (Archived)

VSIFT on primary Keys

(0) ShareShare
ReportReport
Posted on by Gwenael Riotteau 237

Have too much VSIFT table can be a performance penality, so i try to remove not necessay vsift table

According to http://dynamicsuser.net/nav/b/stryk/posts/optimizing-vsift-getting-rid-of-nonsense,the MaintainSIFTIndex must be set to False on all primary keys.

But :

  - https://community.dynamics.com/nav/b/navmarkbrummel/archive/2014/01/15/nav2013r2-maintain-sift-index say the opposite

  - on a Cronus 2016, there are some primary keys with a SIFT table (for example MaintainSIFTIndex=true  for the primary keys of Sales Line table)

   Microsoft don't apply the best practices ?

So what do you think ? good or bad ?

*This post is locked for comments

I have the same question (0)
  • Gwenael Riotteau Profile Picture
    Gwenael Riotteau 237 on at

    dynamicsuser.net/.../optimizing-vsift-getting-rid-of-nonsense

  • Suggested answer
    Alexander Ermakov Profile Picture
    Alexander Ermakov 28,096 on at

    I actually support the vision of Jorg regarding VSIFTs on unique primary keys, as (theoretically) you would not gain additional performance having non-grouped values in VSIFTs - especially for older versions.

    However here you should remember that starting from NAV 2013 version, when native database has been skipped, NAV started to use SQL database with "real" SQL methods (which was not the case when native database was available). Thus, the performance issue started to be much less issue :-).

    Therefore it might sound reasonable to skip VSIFT for unique primary key as the processing of the real data would not degrade your performance much. However it should be treated case by case - what exactly VSIFT table you are planning to drop?

  • Gwenael Riotteau Profile Picture
    Gwenael Riotteau 237 on at

    well, ALL VSIFT table which are related to a primary key

    according to mbspartner.microsoft.com/.../1108 (Optimize Part 1), i have better performance if i have less unnecessary VSIFT table (as with indexes), so i plan to remove all related to a primary key

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans