Microsoft distributes Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release.
Symptoms
Consider the following scenario.
-
You have a query that uses the ROW_NUMBER function together with a left outer join in Microsoft SQL Server 2008.
-
You create a SELECT statement that uses the query as a subquery and that returns unique rows by using the DISTINCT keyword.
-
You run this SELECT statement.
In this scenario, you may receive an incorrect result. The left outer join is incorrectly ignored.
Note For more information about how to reproduce this issue, see the "Steps to reproduce this issue" subsection in the "More information" section.
Resolution
Cumulative update information
SQL Server 2008 R2
The 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 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2489376 Cumulative Update package 6 for SQL Server 2008 R2 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 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:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
SQL Server 2008 Service Pack 1
The fix for this issue was first released in Cumulative Update 11 for SQL Server 2008 Service Pack 1.
For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2413738 Cumulative update package 11 for SQL Server 2008 Service Pack 1Note 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 fix release. Microsoft recommends 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:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
SQL Server 2008 Service Pack 2
The fix for this issue was first released in Cumulative Update 2 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2467239 Cumulative update package 2 for SQL Server 2008 Service Pack 2Note 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 fix release. Microsoft recommends 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:
2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
Steps to reproduce this issue
-
Run the following statements. These statements create two tables and insert some data into the tables.
create table A (a1 int)
create table B (b1 int)
insert into A values(1)
insert into B values(1)
insert into B values(1) -
Run the following statement. This statement uses the ROW_NUMBER function together with a left outer join.
select a1, row_number() over (partition by a1 order by a1) as a3
from A
left join B ON A.a1 = B.b1 -
Run the following statement. This statement uses the query in step 2 as a subquery:
select distinct a1, a3
from (
select a1, row_number() over (partition by a1 order by a1) as a3
from A
left join B ON A.a1 = B.b1
) as x
Note The query in step 3 returns an incorrect result when this issue occurs.
References
For more information about the ROW_NUMBER function and outer joins, visit the following Microsoft Developer Network (MSDN) websites:
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499New naming schema for Microsoft SQL Server software update packagesFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
