Article ID: 326934 - Last Review: September 27, 2005 - Revision: 4.2

FIX: Query Compilation Fails with Error 701 After It Uses Up Buffer Pool Memory

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

This article was previously published under Q326934

BUG #: 361298 (SHILOH_BUGS)

Expand all | Collapse all

SYMPTOMS

A query that uses multiple full outer joins may fail with SQL Error 701 after it uses up all the available buffer pool memory while it tries to compile the query plan:

There is insufficient system memory to run this query.

The following additional message may also be present in the SQL Server error log:

BPool::Map: no remappable address found.

Back to the top

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 (http://support.microsoft.com/kb/290211/EN-US/ ) INF: How To Obtain the Latest SQL Server 2000 Service Pack

NOTE: The following hotfix was created before the release of Microsoft SQL Server 2000 Service Pack 3.

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

   07-24-2002   17:58:05   8.00.663    7,467,089 bytes   Sqlservr.exe

NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.

Back to the top

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

Back to the top