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
- 305 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
Index Hinting Whitepaper
Administrator
Member, Moderator, Administrator Posts: 2,500
Index Hinting Whitepaper
Since update 6 Microsoft Dynamics NAV has enabled index hinting by default.
It is hard to argue with a decision that can do miracles which index hinting can do. On the other hand there is a fantastic query optimizer which can do even bigger miracles correcting users and developers mistakes whether on purpose or not.
Fact is that the problem is in SQL Server, not in Navision. Try searching the web for “Parameter Sniffing” and you’ll find that we are not alone in this subject. So bottom line is that the SQL Server team should take care of it and fix this undocumented feature.
What I have done is what MS should have done in the first place and that is to release a whitepaper describing the problem and how to handle it if is occurs.
This file is uploaded as support for the thread Update 6 for Navision 4.0 SP3: BE CAREFULL.
http://www.mibuso.com/dlinfo.asp?FileID=896
Discuss this download here.
Since update 6 Microsoft Dynamics NAV has enabled index hinting by default.
It is hard to argue with a decision that can do miracles which index hinting can do. On the other hand there is a fantastic query optimizer which can do even bigger miracles correcting users and developers mistakes whether on purpose or not.
Fact is that the problem is in SQL Server, not in Navision. Try searching the web for “Parameter Sniffing” and you’ll find that we are not alone in this subject. So bottom line is that the SQL Server team should take care of it and fix this undocumented feature.
What I have done is what MS should have done in the first place and that is to release a whitepaper describing the problem and how to handle it if is occurs.
This file is uploaded as support for the thread Update 6 for Navision 4.0 SP3: BE CAREFULL.
http://www.mibuso.com/dlinfo.asp?FileID=896
Discuss this download here.
0