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
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 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
Using plan guides
Phenno
Member Posts: 630
Hi all!
Could I have a problem if I use sp_create_plan_guide to create a fixed plan guide for a specific query in NAV2013+?
I have a situation where there is a table with Entry No. as CI and Table No., Entry No. as NCI. I need to filter that table by Table No. and find first Entry No. occurring after specific entry no. so my query looks like:
Select TOP (1) timestamp, "Entry no.", "Table no.", "other fields" from MyTable where "Entry No." > @0 and "Table No." = @1 (OPTIMIZE FOR UNKNOWN)
Since this is parametrized query and table is large I receive a really bad execution plan with clustered index seek. Higher my entry no. in filter is the larger number of reads I get.
I've tested with sp_create_plan_guide and RECOMPILE option for this query and I get only few reads per query, but not sure if that will led to other problems? Is there any other options for this, maybe a change of CI?
P.S.
Query isn't fired to often during the day, it's a batch job running few times in one hour.
Could I have a problem if I use sp_create_plan_guide to create a fixed plan guide for a specific query in NAV2013+?
I have a situation where there is a table with Entry No. as CI and Table No., Entry No. as NCI. I need to filter that table by Table No. and find first Entry No. occurring after specific entry no. so my query looks like:
Select TOP (1) timestamp, "Entry no.", "Table no.", "other fields" from MyTable where "Entry No." > @0 and "Table No." = @1 (OPTIMIZE FOR UNKNOWN)
Since this is parametrized query and table is large I receive a really bad execution plan with clustered index seek. Higher my entry no. in filter is the larger number of reads I get.
I've tested with sp_create_plan_guide and RECOMPILE option for this query and I get only few reads per query, but not sure if that will led to other problems? Is there any other options for this, maybe a change of CI?
P.S.
Query isn't fired to often during the day, it's a batch job running few times in one hour.
0