Microsoft KB Archive/933499

= FIX: Error message when you use transactional replication to replicate the execution of stored procedures to subscribers in SQL Server 2005: &quot;Insufficient memory to run query&quot; =

Article ID: 933499

Article Last Modified on 11/20/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Standard X64 Edition

-



Bug #: 50000921 (SQL Hotfix)



Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.



SUMMARY
This article describes the following about this hotfix release:
 * The issues that are fixed by this hotfix package
 * The prerequisites for applying the hotfix package
 * Information about whether you must restart the computer after you apply the hotfix package
 * Information about whether the hotfix package is replaced by any other hotfix package
 * Information about whether you must make any registry changes after you apply the hotfix package
 * The files that are contained in the hotfix package



SYMPTOMS
In Microsoft SQL Server 2005, you use transactional replication to replicate the execution of stored procedures to subscribers of an article. When you do this, you may receive the following error message on the publisher server:

Insufficient memory to run query

Additionally, the follow error message is logged in the SQL Server Errorlog file:

Error: 701, Severity: 17, State: 123.

There is insufficient system memory to run this query.



CAUSE
This problem occurs because most of the buffer pool memory is used up by the replication cache.



Cumulative update information
To resolve this problem, obtain the cumulative update package (build 3161) for SQL Server 2005 Service Pack 2 (SP2). For more information, click the following article number to view the article in the Microsoft Knowledge Base:

935356 Cumulative update package (build 3161) for SQL Server 2005 Service Pack 2 is available

Hotfix information
A supported hotfix is now 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
To apply the SQL Server 2005 Service Pack 1 (SP1)-based hotfix, you must have SQL Server 2005 SP1 installed. To apply the SQL Server 2005 SP2-based hotfix, you must have SQL Server 2005 SP2 installed.

For more information about how to obtain SQL Server 2005 Service Pack 1 or SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005

Restart information
You do not have to restart the computer after you apply this hotfix.

Registry information
You do not have to change the registry.

Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

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 item in Control Panel.

SQL Server 2005 SP2-based hotfix, Itanium architecture version


WORKAROUND
To work around this problem, run the sp_replflush stored procedure to clear the replication cache.

Note The replication cache is not cleared as soon as you run the stored procedure. Instead, the stored procedure sets up a flag, and this flag causes the replication cache to be cleared before the next cache read operation occurs.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

Additional query words: merge replication memory leak out of memory

Keywords: kbqfe kbpubtypekc kbhotfixserver KB933499

-

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

© Microsoft Corporation. All rights reserved.