.png)
MSSQLSERVER_4846
SQL Server 2005
New:
17 July 2006
Follow these general steps to troubleshoot 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
-
awe enabled
-
min memory per query
-
max server memory
-
If you are using Address Windowing Extensions (AWE), verify that the Windows security setting Lock pages in memory' is enabled.
-
Observe DBCC MEMORYSTATUS output and the way it changes when you see these error messages.
-
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.
