FIX: SNMP Extended Stored Procedures May Leak Memory (234679)

SYMPTOMS

If Simple Network Management Protocol (SNMP) integration is enabled and any of the SNMP-related extended stored procedures are run, you may see a handle and memory leak within the SQL Server address space. The leak is characterized by an increase of four handles and 8 KB of virtual bytes for each invocation of one of the extended stored procedures.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

   Version       File name        Platform
   ---------------------------------------

   6.50.441      Sql441i.exe      Intel
   6.50.441      Sql441a.exe      Alpha

NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.

MORE INFORMATION

SQL Server SNMP integration is provided by Sqlsnmp.dll. This module contains two different extended stored procedures, xp_snmp_getstate and xp_snmp_raisetrap.

The memory leak actually leads to a fragmented virtual address space and may cause SQL Server to stop responding. For additional information, please see the following article in the Microsoft Knowledge Base: