I have spent some time optimizing my Navision Database (NAV 5.0 on SQL2000) and have had quite a bit of success doing so.
However, I am a little confused about what should be done with respect to SIFT maintenance.
I have looked at the SQL Server Stored Procedure "ssi_delzerosift" provided by STRYK System Improvement as well as a SQL Server Stored Procedure provided by PaddyMullaney (modified by ara3n and Waldo) called "pDeleteZeroSiftValues".http://www.mibuso.com/forum/viewtopic.php?t=16985http://www.mibuso.com/forum/viewtopic.php?t=17035
My concern is this...how will NAV 5.0 handle these 'missing' SIFT records?
I understand that the built-in optimize function performs SIFT maintenance and I believe that it is deleting zero SIFT records as well.
I tried this only to find that it causes certain flowfields to total incorrectly.
I then had to immediately rebuild the SIFT tables by deselecting the MaintainSIFTIndex checkbox on all my keys where an associated SIFT table existed, saving my changes.
Immediately following, I turned the checkboxes back on, effectively rebuilding 'corrected' SIFT tables after saving the table changes a second time.
It seems that this is a known bug from 4.0 SP3. :bug:http://www.mibuso.com/forum/viewtopic.php?t=19387
So with all this in mind...won't these two stored procedures cause the same problem?
Although deleting the zero SIFT records is recommended by some forum users that I feel know a great deal about Navision, the posts that introduce the SQL Server Stored Procedures are older than the one that explains the bug.
Do I have cause to be concerned?
I might be totally be off-base here and I might be confusing two different things, but I want to be sure because I certainly don't want to rebuild all my SIFT tables again, should something go wrong.
Any feedback would be greatly appreciated.