Incorrect Results - Partitioned Nonclustered Index with Descending Key - by Paul White NZ

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


69
0
Sign in
to vote
ID 797837 Comments
Status Closed Workarounds
Type Bug Repros 10
Opened 8/20/2013 4:46:37 AM
Access Restriction Public

Description

SQL Server can produce incorrect results when reading from a partitioned non-unique nonclustered index with a descending leading key.

The provided script demonstrates the issue with a simple seek, but the bug is quite general. It caused incorrect results from a Merge Join in a production application, for example. The sort order required by the Merge Join was not delivered by the index.

The bug appeared in SQL Server 2008 and persists through SQL Server 2014 CTP 1.

SQL Server 2005's APPLY model partitioning correctly handles the scenario.
Sign in to post a comment.
Posted by Blaž Dakskobler on 1/21/2014 at 11:40 PM
The KB article is here: http://support.microsoft.com/kb/2892741
Posted by Microsoft on 10/15/2013 at 1:21 PM
Dear customer -- Thanks for investigating and reporting this problem. A fix will be included in the next major release of SQL Server, and in cumulative updates for existing releases.

Best regards,
SQL Server product team.
Posted by Microsoft on 10/15/2013 at 1:21 PM
Dear customer -- Thanks for investigating and reporting this problem. A fix will be included in the next major release of SQL Server, and in cumulative updates for existing releases.

Best regards,
SQL Server product team.
Posted by SoHelpMeCodd on 8/24/2013 at 2:54 PM
http://www.sqlperformance.com/2013/08/t-sql-queries/incorrect-results-with-merge-join