BUG: SELECT INTO with Fixed Memory May Cause Errors 802 and 17803

• Microsoft SQL Server version 7.0

SYMPTOMS

Concurrent execution of a SELECT INTO statement while the configuration option 'max server memory' is set to a fixed size (other than 0) may cause the following errors:

Error: 802, Severity: 17, State: 1
No more buffers can be stolen..

Error: 17803, Severity: 17, State: 17
Insufficient memory available..

WORKAROUND

To work around this problem, avoid setting a fixed 'max server memory' value. A 'max server memory' value of 0 allows SQL Server to dynamically adjust its memory requirements. If you are receiving these errors and you must use a fixed value, you can try either of the following:

• Increase the value of the 'max server memory' parameter until these errors no longer occur.
  
  -or-



• Reduce the number and frequency of concurrent SELECT INTO operations.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 7.0

Additional query words: buffer manager

Keywords          : SSrvTran_SQL kbbug7.00 
Version           : WINNT:7.0
Platform          : winnt 
Issue type        : kbbug 

Last Reviewed: April 19, 1999