Navision 4 - Performance Issues

RobbieXRobbieX Member Posts: 66
We recently upgraded to Navision 4 from 3.7.
Since the upgrade certain dataports/reports which involve the purchase lines have suddenly become very slow.
I am not sure how to fix this.
The forum has a few topics related to performance but I have not found one relevant to this particular problem.
Is Navision 4 slower than 3.7 in some circumstances for some particular reason?
Could it be the way our new Navision Database Server is setup?
Could it be there is not enough/too much cache? Changing this does not seem to make any difference.
I suspect it could be related to flowfields....is there any way to request that flowfields are not "run" if not required for a certain dataport or report?
Please advise....thanks!
Robbiex

Comments

  • kinekine Member Posts: 12,562
    1) Have you 4.00, 4.00SP1 or 4.00SP2 (which was released few days ago... :-))

    2) Are you running on MS SQL or on Native DB?

    3) If on MS SQL and you are using 4.00SP1, there is bug that PK are not set as Clustered indexes. Search this forum for more details about that. There is hotfix for that (you need to ask microsoft to send it to you if you are partner, if you are customer ask your partner about that).
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • RobbieXRobbieX Member Posts: 66
    We are using a Native Database....
    I have been researching....it seems to be related to flowfields between the Sales Lines table and the Purchase Lines table. As soon as they are disabled everything speeds up.
    But these flowfields are required....how to avoid using them?
    For example, we have an option field in the Purchase Lines....if this is changed in the Purchase Lines table, then the change is reflected in 4 other tables using flowfilters.
    This is an important part of the company's data sharing.
    Any ideas?
    Robbiex
  • kinekine Member Posts: 12,562
    Flowfields are good for fast sharing data between tables. But not in case when you need to filters based on this data. If you need to use for example this Option for filtering, it is better to use it as normal field and add C/AL code which will update it when the master field is changed (OnValidate). Than the filtering will be much faster.
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
Sign In or Register to comment.