Home Dashboard Directory Help
Search

Wrong execution plan for view with UNION ALL by Avantix


Status: 

Resolved
 as Won't Fix Help for as Won't Fix


2
0
Sign in
to vote
Type: Bug
ID: 783813
Opened: 4/16/2013 5:08:25 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

If we have 2 tables with the same structure with a clustered and non-clustered indexes, and combine them in a view with UNION ALL operator, optimizer chooses wrong execution plan when we trying to use non-clustered index in reverse sort order. When we using direct sort order (as defined in non-clustered index definition), query execution plan is as expected (using this index), but in reverse sort order we get a clustered index scan.
Details
Sign in to post a comment.
Posted by Microsoft on 4/26/2013 at 11:15 AM
Hello,

Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SQL Server. Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SQL Server. The reasons for closing this bug is because the scenario reported in the bug are not common enough and due to the risk of implementing a fix it unfortunately does not meet the bar for the current version of the product.

If you have more supporting information and details or feel strongly that we should reconsider, please do resubmit this item for review.

Thanks again for reporting the product issue and continued support in improving our product.
Gus Apostol, SQL Server Program Manager
Sign in to post a workaround.