MSSQLSERVER_701

  • Article

Details

Product Name

SQL Server

Product Version

11.0

Product Build Number

11.00.0000.00

Event ID

701

Event Source

MSSQLSERVER

Component

SQLEngine

Symbolic Name

NOSYSMEM

Message Text

There is insufficient system memory to run this query.

Explanation

SQL Server has failed to allocate sufficient memory to run the query. This can be caused by a variety of reasons including operating system settings, physical memory availability, or memory limits on the current workload. In most cases, the transaction that failed is not the cause of this error.

Diagnostic queries, such as DBCC statements, may fail because server the does not have sufficient memory.

A timeout occurred while waiting for memory resources to execute the query in the resource pool 'default'.

User Action

If you are not using Resource Governor, we recommend that you verify the overall server state and load, or check the resource pool or workload group settings.

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

    • min memory per query

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

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

  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.