Wrong execution plan for view with UNION ALL - by Avantix

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


2
0
Sign in
to vote
ID 783813 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 4/16/2013 5:08:25 AM
Access Restriction Public

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.
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