Microsoft KB Archive/291540

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

Article ID: 291540

Article Last Modified on 10/7/2005

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition

-



This article was previously published under Q291540



BUG #: 352077 (SHILOH)



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 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:   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.

Keywords: kbbug kbfix kbqfe kbsqlserv2000sp1fix KB291540

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.