Skip to content

Latest commit

 

History

History
70 lines (47 loc) · 3.08 KB

mssqlserver-802-database-engine-error.md

File metadata and controls

70 lines (47 loc) · 3.08 KB
title description author ms.author ms.reviewer ms.date ms.service ms.subservice ms.topic helpviewer_keywords
MSSQLSERVER_802 - Database Engine error
MSSQLSERVER_802 - Database Engine error
MashaMSFT
mathoma
wiassaf
11/04/2021
sql
supportability
reference
802 (Database Engine error)

MSSQLSERVER_802 - Database Engine error

[!INCLUDE SQL Server]

Details

Attribute Value
Product Name SQL Server
Event ID 802
Event Source MSSQLSERVER
Component SQLEngine
Symbolic Name NO_BUFS
Message Text There is insufficient memory available in the buffer pool.

Note

This article is focused on SQL Server. For information on troubleshooting out of memory issues in Azure SQL Database, see Troubleshoot out of memory errors with Azure SQL Database.

Explanation

This is caused when the buffer pool is full and the buffer pool cannot grow any larger.

User action

The following list outlines general steps that will help in troubleshooting memory errors:

  1. Verify whether other applications or services are consuming memory on this server. Reconfigure less critical applications or services to consume less memory.

  2. Start collecting performance monitor counters for [!INCLUDEssNoVersion]: Buffer Manager, [!INCLUDEssNoVersion]: Memory Manager.

  3. Check the following [!INCLUDEssNoVersion] memory configuration parameters:

    • max server memory

    • min server memory

    • min memory per query

    Notice any unusual settings and correct them as necessary. Account for increased memory requirements for [!INCLUDEssNoVersion]. Default settings are listed in Server memory configuration options.

  4. Observe DBCC MEMORYSTATUS output and the way it changes when you see these error messages.

  5. Check the workload (number of concurrent sessions, currently executing queries).

The following actions may make more memory available to [!INCLUDEssNoVersion]:

  • If applications besides [!INCLUDEssNoVersion] are consuming resources, try stopping these applications or running them on a separate server.

  • If you have configured max server memory, increase its setting. For more information, see Set options manually.

Run the following DBCC commands to free several [!INCLUDEssNoVersion] memory caches.

  • DBCC FREESYSTEMCACHE

  • DBCC FREESESSIONCACHE

  • DBCC FREEPROCCACHE

If the problem continues, you will need to investigate further and possibly reduce workload.