Last updated 02 March 2021.
General - Performance troubleshooting and profiling for Dynamics NAV | BC and SQL Server
Checks SQL Server in scope for some of most common skewed Best Practices and performance issues.
Valid from SQL Server 2012 onwards. By default all databases in the SQL Server instance are eligible for the several database specific checks, and you may use the optional parameter to narrow these checks to specific databases.
Only a system administrator/local host administrator is able to perform all checks or functions.
This code and information are provided "AS IS" without warranty of any kind, either expressed or implied. Furthermore, the author or Olav Treffurt IT Consulting shall not be liable for any damages you may sustain by using this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages.
Since the release of Microsoft Dynamics NAV 2013, tracking user activity has become a little more complicated than in previous versions because, unlike before, all user connections to SQL Server are now server connections. This makes it more difficult to track the activities of individual users.
But not impossible: Enabling "Full SQL Tracing" adds comments with data such as user ID, C/AL row executed, call stack, and more to SQL Server Extended Events.
Nevertheless, tracking and analyzing activity in front of the user in V8 XE Profiler (even with C/AL tracing enabled) can be a complex task. That's why we introduced the V8 XE Profiler, a tool similar to the old Client Profiler.
You can use this tool to profile the activities of the user(s) from a Dynamics NAV page (in the same way as we did with the Client Monitor).
Here you will find the information you were missing so far.
Which user with which NAV/BC object locked another user. You can see the complete transaction that led to the table lock. Not only the SQL scripts that were executed by the C/AL code are displayed, but also from which C/Side/Object (NAV) or AL Object (BC 365) the action was executed.