Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 310 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Deadlock resolution on NAV 2013
MukeshVerma
Member Posts: 6
Hi All,
Our client is using NAV 2013 and experiencing deadlocks.
We have been able to reproduce the issue with 7 users doing the same activity. The issue was resolved by putting an explicit lock on one table. However when the changes were deployed on Prod, it backfired as the other activities were not having the same locking sequence.
Now we are working on breaking a big transaction into smaller one so that we can reduce the transaction time and deadlocks.
I am still worried that this will not resolve the issue entirely unless we correct the Table Locking Order.
Until version 2009 R2, we had Client Monitor in classic client and there was a "Database Resource Toolkit" available which was very useful to identify the locking order. I am unable to find any tool in 2013 which can tell me the transactions in an activity and the Table locking order for all the tables involved in the transaction.
I was hoping if somebody can help me with the approach to resolve deadlock in version NAV 2013.
Regards,
Mukesh Verma
Our client is using NAV 2013 and experiencing deadlocks.
We have been able to reproduce the issue with 7 users doing the same activity. The issue was resolved by putting an explicit lock on one table. However when the changes were deployed on Prod, it backfired as the other activities were not having the same locking sequence.
Now we are working on breaking a big transaction into smaller one so that we can reduce the transaction time and deadlocks.
I am still worried that this will not resolve the issue entirely unless we correct the Table Locking Order.
Until version 2009 R2, we had Client Monitor in classic client and there was a "Database Resource Toolkit" available which was very useful to identify the locking order. I am unable to find any tool in 2013 which can tell me the transactions in an activity and the Table locking order for all the tables involved in the transaction.
I was hoping if somebody can help me with the approach to resolve deadlock in version NAV 2013.
Regards,
Mukesh Verma
0
Comments
http://navappprofiler.codeplex.com/
I doubt it would give you much information about locking order either.
I think you will need to search for Microsoft SQL tools and methods, and just consider NAV as any other application using SQL.
The SQL Profiler is my weapon of choice, but there might be better SQL tools out there giving information about the locking order.
Peter