This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 469418 (SHILOH_BUGS)
You may not be able to set the network affinity for a particular instance of SQL Server.
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 hotfix has the file attributes (or later file attributes) 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 the files may also contain additional files.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.
With this fix, you can set the incoming Tabular Data Stream (TDS) network affinity for an instance of SQL Server by using the -N## (case sensitive) startup parameter.
SQL Server uses a high priority thread to handle incoming TDS I/O completion activities. The network thread can be affinitized to a processor by providing the –N## startup parameter. The mask passed to the –N## startup parameter is used in a SetThreadAffinityMask call to establish the network threads affinity.
By default, the network affinity is not set. However, if you must establish network affinity for the server that is 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 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 with the –I## command line parameter, the sp_configure stored procedure "‘affinity mask", and the Virtual Interface Architecture (VIA) card affinity settings to manage the SQL Server resources.
For a SQL Server 2000 Service Pack 2 (SP2) version of this fix, see the following article in the Microsoft Knowledge Base:
818764 FIX: Cannot Set SQL Server Instance Specific Network Affinity
For additional information, 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