For technical upgrades from <4.0SP3 versions to later, I prefer 4.0SP3 hotfixed. Especially if you need some SQL-tuning. 4.0SP3 is easier to tune because it uses extra tables for the SIFT.
And if you are on SQL2000, you best don't use NAV 5.0SP1 that uses indexed views for the SIFTS : SQL2000 has some problems using indexed views: sometimes SQL2000 decides to recalculate the complete table instead of only what is needed. SQL2005 doesn't have that problem.
Regards,Alain Krikilion No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
Comments
U must use find('-') (include with locktable if you make datamanupulations) instead of findset.
There are a lot of advantages for SQL (and also some for native).
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
The question here is: can he upgrade (Upgrade contract / costs) or can he not ....
For technical upgrades from <4.0SP3 versions to later, I prefer 4.0SP3 hotfixed. Especially if you need some SQL-tuning. 4.0SP3 is easier to tune because it uses extra tables for the SIFT.
And if you are on SQL2000, you best don't use NAV 5.0SP1 that uses indexed views for the SIFTS : SQL2000 has some problems using indexed views: sometimes SQL2000 decides to recalculate the complete table instead of only what is needed. SQL2005 doesn't have that problem.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!