FIX: Query that you run against a partitioned table returns incorrect results in SQL Server 2008, SQL Server 2008 R2 or SQL Server 2012
Consider the following scenario:
You have a partitioned table in Microsoft SQL Server 2008, SQL Server 2008 R2, or Microsoft SQL Server 2012.. The table has a non-unique, nonclustered index in a descending order. You run a query against the table. The query spans multiple partitions and requests an order.
In this scenario, the query returns incorrect results.
This issue occurs because SQL Server reverses partition ID ranges when a descending index is queried. Therefore, the correct order across the partitions is violated.
The issue was first fixed in the following cumulative update of SQL Server. After you apply the fix, you have to enable trace flag 4199 to make the hotfix work.
About cumulative updates for SQL Server
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 2892741 - Last Review: 01/20/2014 17:16:00 - Revision: 3.0
Applies to Microsoft SQL Server 2008 Service Pack 3 Microsoft SQL Server 2008 R2 Service Pack 2 Microsoft SQL Server 2012 Service Pack 1 Keywords: kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2892741