MSDN Library


Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2).

Product Name

SQL Server

Event ID


Event Source




Symbolic Name


Message Text

A time out occurred while waiting for memory resources to execute the query. Rerun the query.

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

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 for SQL Server 2016. 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.




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

Community Additions

© 2015 Microsoft