NAV 2017 and SQL Server 2019

(0) Share

Report

Posted on by AndrewHerron

We recently had to upgrade (full database migration to fresh MSSQL install) to SQL Server 2019 and we're now running into issues with the G_L Entry table. When shipping posts a shipment, it runs very slow, and any queries against the table are made to wait until the order shipment is finished with it. My question is, are there specific optimizations that are done to the NAV code and queries that are specific to the SQL version? If so, what do I need to do in order to optimize our NAV for MS SQL 2019?

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

Thomas Brownell on at

Like (0)

Report

RE: NAV 2017 and SQL Server 2019

Hello,

There isn’t specific optimization between SQL versions alone. I would recommend reviewing the following Optimizing SQL Server Performance with Microsoft Dynamics NAV documentation to see if this helps:

https://docs.microsoft.com/en-us/dynamics-nav/optimizing-sql-server-performance-with-microsoft-dynamics-nav

Beyond this you may want to run a SQL Profiler trace to with ‘Full SQL Tracing’ enabled to help isolate if additional keys might be needed or modified. The below document also has an example of this as well:

https://cloudblogs.microsoft.com/dynamics365/no-audience/2012/09/18/example-of-how-to-use-sql-tracing-feature-to-profile-al-code/?source=nav

Hope this helps,

Thomas Brownell | | Support Escal Eng | Dynamics NAV/Business Central

Was this reply helpful? Yes No