Microsoft KB Archive/946037

= FIX: The Processors page in the Server Properties dialog box in SQL Server Management Studio does not correctly report the processor affinity for an instance of SQL Server 2005 on a computer that has more than 32 processors =

Article ID: 946037

Article Last Modified on 12/26/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard X64 Edition
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems

-



Bug #: 50002171 (SQL Hotfix)



Microsoft distributes Microsoft SQL Server 2005 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 2005 fix release.



SYMPTOMS
In Microsoft SQL Server 2005, you open the Processors page in the Server Properties dialog box in SQL Server Management Studio. However, this page does not correctly report the processor affinity for an instance of SQL Server that is installed on a computer that has more than 32 processors. In the dialog box, the processor affinity shows that the affinity64 mask option has the same value as the affinity mask option regardless of the value that you set for the affinity64 mask option. When you run the sp_configure stored procedure to examine the processor affinity, the values of the affinity mask option and the affinity64 mask option are reported correctly.

For example, consider the following scenario:
 * You install SQL Server 2005 on a computer that has 64 processors.
 * You set the affinity mask option by using the sp_configure stored procedure to assign the first 10 processors to the instance.

Note The first 10 processors are shown as CPU0 to CPU9 in the Processors page in the Server Properties dialog box.
 * You also use the sp_configure stored procedure to set the affinity64 mask option to 0. Therefore, the last 32 processors (CPU32 to CPU63) are not assigned to the instance.

In this scenario, when you examine the processor affinity in the Processors page in the Server Properties dialog box in SQL Server Management Studio, you will find that processors CPU0 to CPU9 and processors CPU32 to CPU41 are all incorrectly assigned to the instance.



RESOLUTION
The fix for this issue was first released in Cumulative Update 5. 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:

943656 Cumulative update package 5 for SQL Server 2005 Service Pack 2

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

937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released

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



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

943656 Cumulative update package 5 for SQL Server 2005 Service Pack 2

