Home Dashboard Directory Help
Search

Sub-optimal performance of MIN/MAX query for a non leading partition column by Ami Levin


Status: 

Closed
 as Won't Fix Help for as Won't Fix


2
0
Sign in
to vote
Type: Bug
ID: 782083
Opened: 3/25/2013 2:56:35 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

For a query that looks for the MIN / MAX value of a column which is the partitioning column but is not the leading column of the clustered index, all partitions are scanned when partition elimination can be used for optimal performance as the MIN/MAX value will always be in the first/last non empty partition respectively.
Details
Sign in to post a comment.
Posted by Microsoft on 4/26/2013 at 11:20 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.