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