MSSQLSERVER_802 - Database Engine error
Applies to:
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:
Verify whether other applications or services are consuming memory on this server. Reconfigure less critical applications or services to consume less memory.
Start collecting performance monitor counters for SQL Server: Buffer Manager, SQL Server: Memory Manager.
Check the following SQL Server 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 SQL Server. Default settings are listed in Server memory configuration options.
Observe DBCC MEMORYSTATUS output and the way it changes when you see these error messages.
Check the workload (number of concurrent sessions, currently executing queries).
The following actions may make more memory available to SQL Server:
If applications besides SQL Server 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 SQL Server memory caches.
DBCC FREESYSTEMCACHE
DBCC FREESESSIONCACHE
DBCC FREEPROCCACHE
If the problem continues, you will need to investigate further and possibly reduce workload.
Σχόλια
https://aka.ms/ContentUserFeedback.
Σύντομα διαθέσιμα: Καθ' όλη τη διάρκεια του 2024 θα καταργήσουμε σταδιακά τα ζητήματα GitHub ως μηχανισμό ανάδρασης για το περιεχόμενο και θα το αντικαταστήσουμε με ένα νέο σύστημα ανάδρασης. Για περισσότερες πληροφορίες, ανατρέξτε στο θέμα:Υποβολή και προβολή σχολίων για