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
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
SQL Isolation Level
MukeshVerma
Member Posts: 6
Hi,
My client is using NAV 2013 and the current Isolation Level is Read Committed. They are experiencing the Table locking and dead locks.
I have come across various blog with the suggestion that the Isolation Level should be changed to "Repeatable Read" from default("Serializable").
Can somebody suggest if "Read Committed" is better or "Repeatable Read"?
Regards
Mukesh Verma
My client is using NAV 2013 and the current Isolation Level is Read Committed. They are experiencing the Table locking and dead locks.
I have come across various blog with the suggestion that the Isolation Level should be changed to "Repeatable Read" from default("Serializable").
Can somebody suggest if "Read Committed" is better or "Repeatable Read"?
Regards
Mukesh Verma
0
Comments
NAV 2013 uses "Repeatable Read" for write transactions by default.
There may be another cause of the locks you're experiencing.
Are the locks happening for specific processes or at certain times of the day?
Do they resolve themselves slowly or are you guys having to blow them away?