Article ID: 938915 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Bug #: 50001313 (SQL Hotfix)
Consider the following scenario:
Cumulative update informationThe 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 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
946608Note 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 2005 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:
(http://support.microsoft.com/kb/946608/LN/ )Cumulative update package 6 for SQL Server 2005 Service Pack 2
937137Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 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.
(http://support.microsoft.com/kb/937137/LN/ )The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Note When you request hotfix 946608, you need to obtain only the Yukon_SP2_CU6_SharePointRS file.
To work around this problem, click Apply after you update the parent parameter. Then, edit the remaining parameters.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.