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

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

RTC Report It is not possible to instantiate the Visual Studio bridge.

Hi all, As a Navision developers I have Multiple Versions of Navision running in single Machine. As discussed Earlier in the post how to run multiple Version of RTC in single machine. So my machine have following details for RTC Versions - NAV 2009 R2    - is installed. NAV 2009 SP1  - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 SP1 IN\ NAV 2009         - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 IN\ This approach has been working great for execution of Classic and RTC Clients. However, after installing Dynamics NAV 2009 R2, if i tried to view the Layout for an NAV 2009 SP1 Report i was getting the following error: ---------------------------  Microsoft Dynamics NAV Classic  ---------------------------  It is not possible to instantiate  the Visual Studio bridge.  ---------------------------  OK    --------------------------- After searchi...

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.