We recently upgraded a client to MS Dynamics NAV 2017 and one user was reporting slowness entering sales orders. The slowness was determined to be a delay at the quantity field validation of approx. 6 seconds. After more testing, this issue appears to affect other users but in different databases. For example, one user experiences the delay in Production database but not in the TEST database, another has the delay in TEST but not in Production database, and yet another has no delay in either database. We have checked object versions, role centers, user setup, config file, and are not able to explain the behavior. Has anybody seen an issue like this or know what could cause a delay at the user/database level?
0
Answers
If your server is virtualized then random activity peaks at different unrelated guests may have an impact.
If server disks are SAN based it could be some periodic activities/maintenance on the SAN
For example in our virtualized environment we have a SAN snapshot running every so often, and it has a visible impact on our NAV - but the impact is only visible when the other guests have a load/activity peak at the same time. So overall it looks like a random issue - from time to time NAV slows down, for one user or another.
Try to setup the some monitring on the SQL and NST server and try to correlate NAV issues with unusual system activity peaks, perhaps this will help you to pinpoint the problem
Slawek
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-03
After more investigation, we found that notifications were set up on the role center for the affected user/database. When the notification options were removed, the performance improved and there was no more delay in entering the sales order. When SQL Profiler trace was run again, the SQL:Batchcompleted lines were gone. It was tested on two different users who experienced the issue and the results were the same.
Thanks again for the suggestions!
I expect Microsoft has fixed this issue in NAV 2017 Cumulative Update 09 application hotfix. Change on TAB 1518.
I have not tested this fix by Microsoft yet. Lets hope this does the trick.