Dynamics User Group
Since 1995 - The Microsoft Dynamics Online User Community

February 2008 - Microsoft Dynamics NAV Sustained Engineering Team Blog

Sort by: Most Recent | Most Viewed | Most Commented

  • Index Usage Query

    This is a follow up from an earlier blog "Finding Index usage" . In that blog, I described a very simple way to list how indexes are being used. In this blog, the query is much extended so that it now shows your Navision keys, listed by either number of updates, or by their cost divided by their usage, and it shows when an index was last used for reading. The idea is to show a list of indexes that are being maintained, but never or rarely being used. The query uses SQL Server Dynamic Managament...

  • How to detect locking order for a NAV process

    The nature of a deadlock is that two processes lock resources in different orders. Deadlocks can in theory be eliminated by ensuring that all processes always lock resources in the same order. This document describes how to determine the locking order of a process in Microsoft Dynamics NAV. Note, that I mention locking of "resources". For most of the time, this means placing locks on a table, but it could as well mean placing locks on different parts of the same table, or of different indexes...
    Filed under:

  • Record-level locking in the SQL Server option for Microsoft Dynamics NAV

    If you are designing a system for high throughput and want to minimize blocking, it's important to know in advance exactly what kind of locking behaviour to expect. On SQL Server, Microsoft Dynamics NAV uses record-level locking, as opposed to table-level locking on the native database server. In reality, SQL Server can lock a little bit more than the individual records you want to lock: It can also lock the next and the previous records. This happens when SQL Server applies a range-lock. This...

Copyright Dynamics User Group, 1995-2008, all rights reserved. The Dynamics User Group is not affiliated with Microsoft Corporation.