This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 469459 (SQL Server 8.0)
You cannot set the network affinity for an instance of SQL Server 2000 Service Pack 3 (SP3).
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
NOTE: Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.
After you apply this hotfix, you can set the incoming Tabular Data Stream (TDS) network affinity for an instance of SQL Server by using the startup parameter -N##. This parameter is case-sensitive.
SQL Server uses a high-priority thread to handle incoming TDS I/O completion activities. The high-priority network thread can be affinitized to a processor by providing the -N## startup parameter. The mask that is passed to the -N## parameter is used in a SetThreadAffinityMask call to establish the network thread's affinity.
By default, the network affinity is not set. However, if you must establish network affinity for the computer running SQL Server, Microsoft recommends that you set the mask to the last physical processor. When you set the affinity mask to the last physical processor of your computer, all incoming connection activity is automatically affinitized with the last physical processor, and the UMS scheduler that is associated with the last processor is correctly weighted to allow more network-based activities.
For high-end systems, you can combine the -N## startup parameter, the –I## command-line parameter, the sp_configure stored procedure affinity mask, and the Virtual Interface Architecture (VIA) card affinity settings to manage SQL Server resources.
For additional information about a hotfix for this problem in SQL Server 2000 SP2, click the following article number to view the article in the Microsoft Knowledge Base:
818764 FIX: Cannot Set SQL Server Instance Specific Network Affinity