Select the product you need help with
FIX: You receive an incorrect result when you run a query against a partitioned table in SQL Server 2008 R2 or in SQL Server 2012Article ID: 2770258 - View products that this article applies to. On This PageSymptomsWhen you run a query against a partitioned table in Microsoft SQL Server 2008 R2 or in Microsoft SQL Server 2012, an incorrect result returns intermittently. This issue occurs if the following conditions are true:
ResolutionCumulative update informationCumulative update 6 for SQL Server 2012The fix for this issue was first released in Cumulative Update 6. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:2728897 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2728897/
)
Cumulative update package 6 for SQL Server 20122692828
(http://support.microsoft.com/kb/2692828 /
)
The SQL Server 2012 builds that were released after SQL Server 2012 was released Cumulative Update 2 for SQL Server 2012 SP1The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:2790947 Note Because the builds are
cumulative, each new fix release contains all the hotfixes and all the security fixes
that were included with the previous SQL Server 2012 SP1 fix release. We recommend that
you consider applying the most recent fix release that contains this hotfix. For more
information, click the following article number to view the article in the Microsoft
Knowledge Base:
(http://support.microsoft.com/kb/2790947/
)
Cumulative update package 2 for SQL Server 2012
Service Pack 12772858
(http://support.microsoft.com/kb/2772858/
)
The SQL
Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was
releasedCumulative update 4 for SQL Server 2008 R2 Service Pack 2 (SP2)The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:2777358 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 Service Pack 2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2777358/
)
Cumulative update package 4 for SQL Server 2008 R2 Service Pack 22730301
(http://support.microsoft.com/kb/2730301/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was releasedWorkaroundTo work around this issue, run a query that uses a degree of parallelism of less than six. Note The optimal MAXDOP value may vary. To make sure that you remove the problem, set the MAXDOP value to 1. StatusMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. PropertiesArticle ID: 2770258 - Last Review: February 18, 2013 - Revision: 4.0 Applies to
| Article Translations
 |
Back to the top
