Udostępnij za pośrednictwem


MSSQLSERVER_8651

Details

Product Name

SQL Server

Product Version

10.0

Product Build Number

10.00.0000.00

Event ID

8651

Event Source

MSSQLSERVER

Component

SQLEngine

Symbolic Name

MEMGRANT_ERR

Message Text

Could not perform the requested operation because the minimum query memory is not available. Decrease the configured value for the 'min memory per query' server configuration option.

Explanation

Other processes are consuming server memory (exerting memory pressure in the server).

User Action

Either decrease the configured value for the min memory per query' server configuration option or reduce the query load to the server.

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 SQL Server: Buffer Manager, SQL Server: Memory Manager.

  3. Check the following SQL Server memory configuration parameters:

    • max server memory

    • min server memory

    • awe enabled

    • min memory per query

    Notice unusual settings. Correct them as necessary. Default settings are listed in "Setting Server Configuration Options" in SQL Server Books Online.

  4. If you are using Address Windowing Extensions (AWE), verify that the Windows security setting Lock pages in memory' is enabled.

  5. Check the workload (for example, 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 running these applications or consider running them on a separate server. This will remove external memory pressure.

  • If you have configured max server memory, increase its setting.

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.