Skip to main content

Microsoft Dynamics NAV 2017 - SQL Database Locks.

Hi Readers,

Yes, you read the title correctly it says, Database Locks. There are some pretty cool changes in terms of Identifying Locks that may occur during our code execution in Microsoft Dynamics NAV 2017.

After Release of Microsoft Dynamics NAV 2013, we were unable to identify that from Dynamics NAV it was so hard to figure out the Lock details via SQL Server.

For Already Published Articles about NAV 2017, Click Here.

Below are the details of Enhancements for Monitoring SQL Database Lock in Microsoft Dynamics NAV 2017.




1. Microsoft Dynamics NAV Debugger Shows us the Duration of the Code That is executing. 

Put some breakpoint, Run the debugger, start the Code Processing and Navigate to Debugger when system waits for action at a breakpoint.
Now we can see the time duration that code took to execute till the breakpoint.


2. Microsoft Dynamics NAV 2017 can show the Current Locks in Database if there are any.

In an Event of Lock, select Tools - Debugger - Database Lock as shown below.


System will show you details about Lock which will include -

  1. Table Name - Specifies the name of the Dynamics NAV table affected by the lock.
  2. SQL Lock Resource Type - Specifies the database resource affected by the lock,such as DATABASE, FILE, OBJECT, PAGE, KEY, and more.
  3. SQL Lock Request Mode - Specifies the lock mode that determines how concurrent transactions can access the resource.
  4. SQL Lock Request Status -
    1. CNVRT - The lock is transitioning from another mode, but the conversion is blocked by another process that holds a lock with a conflicting mode.
    2. GRANT - The lock is active.
    3. WAIT - The lock is blocked by another process that holds a lock with a conflicting mode.
  5. The user who is causing the Lock (not the user who is running Navision Service).
  6. Object Type. 
  7. Object ID.
  8. Function Name.

The feature is enabled for the demo database from Microsoft. 
In the Next article, we will discuss how we can enable this feature for a customer database.

What do you feel about this new feature? Waiting for your comments. 
If you want a demo of the Locking to see how it works, do let me know.

Regards,
Saurav Dhyani

Comments

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.