FIX: Instead of Triggers that Use Work Tables Cause a Memory Leak

Article translations Article translations
Article ID: 291540 - View products that this article applies to.
This article was previously published under Q291540
BUG #: 352077 (SHILOH)
Expand all | Collapse all

SYMPTOMS

INSTEAD OF triggers that require the use of worktables cause a SQL Server buffer pool leak on each execution.

CAUSE

The rowset associated with the worktable is not released when the trigger completes.

RESOLUTION

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix should have the following file attributes or later:
   File name     Platform
   ----------------------

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

WORKAROUND

Re-write the INSTEAD OF triggers to avoid work table usage where possible. Specifically, check for areas associated with sorts and grouping or make use of the Index Tuning wizard to check indexes.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 2000.

Properties

Article ID: 291540 - Last Review: October 7, 2005 - Revision: 3.4
APPLIES TO
  • Microsoft SQL Server 2000 Standard Edition
Keywords: 
kbautohotfix kbhotfixserver kbbug kbfix kbqfe kbsqlserv2000sp1fix KB291540

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