DefaultLockGranularity parameter
xavigepe
Member Posts: 185
Hi. Could anyone explain me what's the use of parameter DefaultLockGranularity when working with SQL Server.
I have read a Microsoft paper where they say that if you create a table using:
CREATE TABLE [$ndo$dbconfig] (config VARCHAR(512) NOT NULL) GRANT SELECT ON [$ndo$dbconfig] TO public
and then insert a row with value DefaultLockGranularity=Yes
then SQL manages locks better. Is that true?. Do I have to restart SQL after inserting this record?
Thanks,
I have read a Microsoft paper where they say that if you create a table using:
CREATE TABLE [$ndo$dbconfig] (config VARCHAR(512) NOT NULL) GRANT SELECT ON [$ndo$dbconfig] TO public
and then insert a row with value DefaultLockGranularity=Yes
then SQL manages locks better. Is that true?. Do I have to restart SQL after inserting this record?
Thanks,
0
Comments
-
When the parameter is Yes SQL Server will choose the granularity of the locks that it places. When the parameter is No Navision will override SQL Server and place
ROWLOCK.
http://dynamicslife.dynamicsusers.net/f ... 10175.aspx0
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
- 322 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
