On NAV Techdays 2016 in Antwerpen (Belgium) Microsoft demonstrated a beautiful new feature. Microsoft Dynamics NAV 2017 now offers ‘Database Deadlock Detection and Monitoring’. If NAV 2017 detects a deadlock it will rollback one of the transactions.
This blog post is a continuation of a previous post about dealing with deadlocks in NAV. That post presented two possible solutions of how to locate and terminate the offending session that was causing the deadlock. One solution was to view the Database Sessions in the classic client, and then delete the session. The other was to use SQL Server and use TSQL queries to locate and terminate.
Blocks and Deadlocks are a major issue in NAV/SQL systems; causing decreased performance and poor user experience. This session will explain the locking mechanisms with Dynamics NAV and SQL Server and how they could be properly used. Further it will be demonstrated how blocks & deadlocks could be easily monitored and analyzed to get clues about the problem’s origin and to find appropriate solutions.
Some practical examples will highlight common problems and give inspiration for practicable solutions.