Skip to main content

How SQL Profiler can save your day by Identifying Lengthy Processes in Microsoft Dynamics NAV / Business Central

Problem Statement:

While building customization for Microsoft Dynamics NAV / Business Central ERP, at times the customization is so heavy that we as developers do not realize how much load we put on the SQL Database which the backbone of the system.

One example of this situation is, I had built a system that can create a Cash Receipt during accepting Payment in terms of Cash from the Customer by temporary passing an entry through the Cash Receipt Journal. There was also a Payment Application code that applied(reconciled) the Payments and the Invoices of the Customer that ran posting of any financial entry concerning that specific Customer.

During this attempt of creating Cash Receipt, the posting would block the Customer, Customer Ledger Entries and G/L Entries Tables which was as per design. And it wouldn't allow anyone to make an entry during this period and it would take approximately 20-30 seconds.

To get out of the Deadlock, I was forced to restart the NAV Server Instance through Power Shell.


In this blog, I will mention how SQL Profiler helped me realize that the Cash Receipt Posting was taking way more resources than expected. There was no metric to even judge what was going on and which query tool precisely how much amount of time to execute.
This also helped me change the process to follow to post Customer Cash Receipts.


  • Microsoft Dynamics NAV / Business Central On-Premise
  • Microsoft SQL Server Management Studio
  • Microsoft SQL Server
  • Understanding of SQL Profiler

Books & References:


1. Open NAV on one side of the screen:
Goto Sessions in NAV search, select the session you want to use SQL Profiler and Start Full SQL Tracing.
NAV Sessions - Enable Full SQL Tracing

2. Open SQL Profiler on the other side of the screen:
Goto SQL Server Management Studio > Tools > SQL Profiler
SQL Server Profiler
SQL Server Profiler - Login 

Trace Properties - General
Check “ShowPlan XML” under Performance Counter.
Trace Properties - Event Selection - Showplan XML

Check “SP:StmtCompleted” Completed under Store Procedures.
Trace Properties - Event Selection - SP:StmtCompleted 

Check all the options under “Locks”
Trace Properties - Event Selection - Locks

3. Run the processes in NAV so the effective background SQL Query Execution can be tracked in  SQL Server Profiler:

Trace SQL - SQL Profiler
4. Tracking which function or line of code is taking the maximum time.:
In this case, check the transaction with a maximum duration
Trace SQL - SQL Profiler - Showplan XML - Exec

After finding the Query taking a long time to run, you can check the corresponding CallStack in C/AL or AL.
Trace SQL - SQL Profiler - NAV Code - Exec

Thus, using this method, you should be able to trace your NAV execution issues.


Thus, to conclude, I had no idea about how SQL Profiler worked. With the help of a friend
from Microsoft Support (Mr. Aananth Rajadevan). I learned what all components are present in  SQL Profiler and how to monitor what is going on and find the correct C/AL Code and rectify it.


Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Setting up OAuth Authentication for Business Central Web Services / APIs

Introduction: After upgrading Business Central to version 17 (Wave2 2020), I found that there was an error telling me that WebService Key is going to be deprecated soon. Web Service Access Key is deprecated. Hence, I decided to explore and probably make it easier through this blog. Pre- requisites : Admin Access to Office 365 Admin Access to Azure Demonstration: 1. App Registration on Azure Portal: To enable OAuth authentication for any apps in Azure Active Directory, you will need to perform App Registration and set up the permissions and security details. i.) Register the App: Search for 'App Registration' on the Azure Portal. Click on New Registration Type in the App Names, Account Types and Redirect URI. Registering Application ii.) Setup API Permissions: Go to API Permissions > Add Permissions > Business Central App > Select Delegated Permissions > Select Other Permissions and Financials > Add Permissions Button. Setup API Permissions iii.) Setup Client Secr

How to Upgrade Data from Microsoft Dynamics NAV to Microsoft Dynamics Business Central On Premise - Part 2

 Introduction: Now that the first step of the problem preprocessing of the NAV Database to make it ready to be migrated to BC is done(refer Part 1 ), we can now proceed further with connecting the database in Business Central On-Premise. Pre- requisites : Microsoft Dynamics 365 Business Central Microsoft Dynamics for NAV Microsoft SQL Server Management Studio (SSMS) Powershell ISE Understand NAV to BC Upgrade Considerations -  Click here Understand Upgrade Path -  Click here Books & References: Demonstration: 1. Install Business