Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Microsoft distributes Microsoft SQL Server 2012 Service Pack 1 (SP1) 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 SP1 fix release.

Symptoms

When Microsoft SQL Server requires memory in non-uniform memory access (NUMA)-enabled environments, Windows may allocate too much memory from a remote node before allocating a page of local memory. Additionally, SQL Server may experience various performance issues.

Notes

  • The memory from the remote node is frequently known as "remote memory" or "foreign memory" in SQL Server.

  • The MSDN blog post titled How It Works: SQL Server 2008 NUMA and Foreign Pages MSDN blog post explains that remote memory allocations are added to an "Away” list. These remote memory allocations are not available to service memory requests from SQL Server. Therefore, SQL Server tries to allocate memory until it obtains local memory or reaches the committed target for a local memory node. This memory allocation process may cause various performance issues such as long startup and recovery times, connection time-outs, and query time-outs.

  • This issue occurs in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2 and SQL Server 2012.

Cause

On computers that has large amounts of memory such as 512 GB or 1 TB, when a query that needs to perform sort operations requests a large memory grant, this memory allocation takes some time to complete. This leads to the error 17883 is logged in SQL Server error log.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:


Cumulative Update 3 for SQL Server 2012 SP1The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:

2812412 Cumulative update package 3 for SQL Server 2012 Service Pack 1Note 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 2012 SP1 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:

2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released

Cumulative Update 12 for SQL Server 2008 Service Pack 3 (SP3)The fix for this issue was first released in Cumulative Update 12 for SQL Server 2008 Service Pack 3. 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:

2863205 Cumulative update package 12 for SQL Server 2008 Service Pack 3Note 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:

2629969 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released

References

For more information about non-uniform memory access (NUMA), go to the following MSDN website:

General information about NUMAFor more information about Soft NUMA and related concepts, see the following MSDN blog post:

How It Works: Soft NUMA, I/O Completion Thread, Lazy Writer Workers and Memory NodesFor 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

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×