FIX: Cannot Set the Network Affinity for an Instance of SQL Server 2000 Service Pack 3

Article translations Article translations
Article ID: 818772 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 469459 (SQL Server 8.0)
Expand all | Collapse all

On This Page

SYMPTOMS

You cannot set the network affinity for an instance of SQL Server 2000 Service Pack 3 (SP3).

RESOLUTION

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

Hotfix information

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.
   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   26-Feb-2003  03:41  2000.80.777.0      29,244  Dbmslpcn.dll     
   25-Apr-2003  02:12                    786,432  Distmdl.ldf
   25-Apr-2003  02:12                  2,359,296  Distmdl.mdf
   30-Jan-2003  01:55                        180  Drop_repl_hotfix.sql
   07-Apr-2003  19:15  2000.80.801.0   1,557,052  Dtsui.dll        
   24-Apr-2003  02:51                    747,927  Instdist.sql
   30-Jan-2003  01:55                      1,402  Inst_repl_hotfix.sql
   08-Feb-2003  06:40  2000.80.765.0      90,692  Msgprox.dll      
   01-Apr-2003  02:07                      1,873  Odsole.sql
   05-Apr-2003  01:46  2000.80.800.0      62,024  Odsole70.dll     
   02-Apr-2003  21:48  2000.80.796.0      57,904  Osql.exe         
   02-Apr-2003  23:15  2000.80.797.0     279,104  Pfutil80.dll     
   04-Apr-2003  21:27                  1,083,467  Replmerg.sql
   04-Apr-2003  21:53  2000.80.798.0     221,768  Replprov.dll     
   08-Feb-2003  06:40  2000.80.765.0     307,784  Replrec.dll      
   01-Apr-2003  02:23                  1,084,828  Replsys.sql
   16-Apr-2003  22:39                    115,892  Sp3_serv_uni.sql
   07-Apr-2003  17:44                     25,172  Sqldumper.exe    
   19-Mar-2003  18:20  2000.80.789.0      28,672  Sqlevn70.rll
   24-Apr-2003  05:39  2000.80.811.0     176,696  Sqlmap70.dll     
   08-Feb-2003  06:40  2000.80.765.0      57,920  Sqlrepss.dll     
   30-Apr-2003  23:52  2000.80.816.0   7,540,817  Sqlservr.exe     
   08-Feb-2003  06:40  2000.80.765.0      45,644  Sqlvdi.dll       
   26-Feb-2003  03:41  2000.80.777.0      29,244  Ssmslpcn.dll     
   26-Feb-2003  03:41  2000.80.777.0      82,492  Ssnetlib.dll     
   30-Apr-2003  23:52  2000.80.816.0      45,132  Ums.dll          
   28-Feb-2003  01:34  2000.80.778.0      98,872  Xpweb70.dll
NOTE: Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

STATUS

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.

MORE INFORMATION

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.

REFERENCES

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

Properties

Article ID: 818772 - Last Review: February 27, 2014 - Revision: 3.3
APPLIES TO
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000, Workgroup Edition
  • Microsoft SQL Server 2000 Desktop Engine (Windows)
  • Microsoft SQL Server 2000 Enterprise Edition 64-bit
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbqfe kbconfig kbsqlserv2000presp4fix kbfix kbbug KB818772

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com