Export (0) Print
Expand All
Expand Minimize
This topic has not yet been rated - Rate this topic

MSSQLSERVER_8645

Product Name

SQL Server

Product Version

10.50

Product Build Number

10.50.0000.00

Event ID

8645

Event Source

MSSQLSERVER

Component

SQLEngine

Symbolic Name

MEMTIMEDOUT_ERR

Message Text

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

There is not enough memory in the system to handle the query load.

Either configure the time-out value to be higher 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. Account for increased memory requirements for SQL Server 2005. 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. Observe DBCC MEMORYSTATUS output and the way it changes when you see these error messages.

  6. 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.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.