Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 267 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
For better performance [Always Row Lock]="yes" or "no"
kamalbaaklini
Member Posts: 37
HI
it is not clear what setup is better for performance [Always Row Lock]="yes" or "no"
(this is found in the path = Files -> Database -> Alter -> Advanced)
in a 150 concurrent sessions environment, and big database (around 1.2 terra), where lot of purchase order and transfer orders created daily. (a lot means more than 1000 PO and 1000 Transfer per day)
your comments are appreciated
:-k
it is not clear what setup is better for performance [Always Row Lock]="yes" or "no"
(this is found in the path = Files -> Database -> Alter -> Advanced)
in a 150 concurrent sessions environment, and big database (around 1.2 terra), where lot of purchase order and transfer orders created daily. (a lot means more than 1000 PO and 1000 Transfer per day)
your comments are appreciated
:-k
0
Comments
Please note that this option was lost in versions released since NAV2013.
The setting disable Lock Escalation on the SQL server.
Instead of escalation of recordlocks into page- or tablelocks, It will add more recordlocks (req. more memory).
This will reduce lockings, but increase memory load.
Please note that this is a global setting for the entire SQL Server..
This only prevents lock escalation due to excessive number of locks. Other factors, such as memory pressure, can still induce lock escalations. Thus you want to have plenty of RAM before using this setting. This also does not SQL from acquiring less granular locks to begin with.
we have SQL 2008R3 64bits with RAM=196GB
and NAV 2009 R2
so what do you suggest?
What edition of SQL?