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
NAV 2016 - Find source of table lock
StLi
Member Posts: 83
Hello,
I'm looking for a good guide / tool to find out who or which code segment / user is causing table locks long enough to lock the system for hours.
We're having trouble with a customer that is suffering form occasional table locks. Maybe 2 or 3 times a week with 50+ active users on the clients and several data exchange interfaces using webservices. We where able to temporarily handle the problem by setting the timeout for the lock but would prefer to find the source of the table lock to enhance performance and omit unnecessary errors.
These locks happen scattered over the whole workday. Our contact with the company swears that they didn't start any larger batch jobs at those times, but it's hard to confirm that without having any hard evidence.
Thanks for your input and best regards,
StLi
p.s. we recently became the solution center of that customer and apparently these locks where already happening before that. So, "undoing" or "tracking" our changes will be quite challenging.
I'm looking for a good guide / tool to find out who or which code segment / user is causing table locks long enough to lock the system for hours.
We're having trouble with a customer that is suffering form occasional table locks. Maybe 2 or 3 times a week with 50+ active users on the clients and several data exchange interfaces using webservices. We where able to temporarily handle the problem by setting the timeout for the lock but would prefer to find the source of the table lock to enhance performance and omit unnecessary errors.
These locks happen scattered over the whole workday. Our contact with the company swears that they didn't start any larger batch jobs at those times, but it's hard to confirm that without having any hard evidence.
Thanks for your input and best regards,
StLi
p.s. we recently became the solution center of that customer and apparently these locks where already happening before that. So, "undoing" or "tracking" our changes will be quite challenging.
0
Best Answer
-
NavNab
Member Posts: 181
Answers
https://msdn.microsoft.com/en-us/dynamics-nav/monitoring-database-locks
Check this http://navnilesh.blogspot.fr/2015/01/how-to-determine-who-has-table-locked.html
and this http://navnilesh.blogspot.fr/2015/01/different-techniques-to-identify.html
Thanks, I will use this next time we get the problem reported