FIX: Out-of-memory error when you run an instance of SQL Server 2012 on a computer that uses NUMA

Microsoft distributes Microsoft SQL Server 2012 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release.
SYMPTOMS
Consider the following scenario. You run an instance of Microsoft SQL Server 2012 on a computer that uses non-uniform memory access (NUMA), and SQL Server uses lots of foreign pages. In this scenario, you may encounter an out-of-memory error. For example, the following 701 error may be logged in the SQL Server error log file:
<Date><Time><spid ID> Error: 701, Severity: 17, State: 123.
<Date><Time><spid ID>There is insufficient system memory to run this query.
This issue typically occurs if the max server memory option is used to set aside a large part of RAM from SQL Server usage. In this case, SQL Server is more likely to experience imbalanced NUMA distribution.
CAUSE
This issue occurs because the function that is used for calculating available memory pages for a memory node does not work correctly.
RESOLUTION

Cumulative update information

SQL Server 2012

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2012. For more information about how to obtain this cumulative update package for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
2679368 Cumulative update 1 for SQL Server 2012
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released
MORE INFORMATION
To check foreign memory amount, use one of the following methods:
  • Query the sys.dm_os_memory_nodes dynamic management view (DMV). For more information about the sys.dm_os_memory_nodes DMV, visit the following MSDN website:
  • Run the following statement or check the memory status output in the SQL Server error log when the 701 error occurs:
    DBCC memorystatus
  • Check the Foreign Node Memory (KB) counter in the Memory Node object in SQL Server 2012. For more information about the Memory Node object, visit the following MSDN website:
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
REFERENCES
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 Naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Properties

Article ID: 2688697 - Last Review: 04/12/2012 07:08:00 - Revision: 1.0

Microsoft SQL Server 2012 Standard, Microsoft SQL Server 2012 Developer, Microsoft SQL Server 2012 Enterprise, Microsoft SQL Server 2012 Express, Microsoft SQL Server 2012 Web

  • kbqfe kbfix kbexpertiseadvanced kbsurveynew KB2688697
Feedback