SQL Server 2012 Memory Manager KB articles


Since the release of SQL Server 2012 with a redesigned memory manager, a steady stream of KB articles have been produced by CSS to provide guidance on the new or changed options, as well as fixes that have been published..

 

How has memory sizing changed in SQL 2012?

2663912 Memory configuration and sizing considerations in SQL Server 2012 – http://support.microsoft.com/default.aspx?scid=kb;EN-US;2663912  

 

Setting “locked pages” to avoid SQL Server memory pages getting swapped has been simplified, particularly for Standard Edition, the details can be found here:

2659143 How to enable the “locked pages” feature in SQL Server 2012 – http://support.microsoft.com/default.aspx?scid=kb;EN-US;2659143

 

Note the following deprecation (particularly relevant for 32-bit installations):

2644592 The “AWE enabled” SQL Server feature is deprecated – http://support.microsoft.com/default.aspx?scid=kb;EN-US;2644592

 

Note the following fixes available:

2708594 FIX: Locked page allocations are enabled without any warning after you upgrade to SQL Server 2012 – http://support.microsoft.com/kb/2708594/EN-US

2688697 FIX: Out-of-memory error when you run an instance of SQL Server 2012 on a computer that uses NUMA – http://support.microsoft.com/kb/2688697/EN-US

Comments (4)

  1. Thanks for collating and sharing

  2. Dont forgot Bob Wards article says:

    There is no “MemToLeave” for the 64bit version of the SQL Server Engine!

    blogs.msdn.com/…/come-on-64bit-so-we-can-leave-the-mem.aspx

  3. Nishant says:

    Sad to see we have to resort to blogs and details are not uploaded to technet.. What's going on ?????????????

  4. gbowerman says:

    Hi Nishant, thanks for commenting. Our goals are:

    1. Make sure all the technical information you need is available on TechNet.

    2. Provide KB articles for any late-breaking support issues.

    3. Blog any information we think might be useful. The difference between a blog article and a TechNet article in this context is that blogs can be written directly by engineers working on features, so it's a direct means of communication. Any information that shows up in blogs and KB articles can become a source for a TechNet article if it includes product knowledge beyond pure support knowledge such as details about patches. We love to get suggestions on particular articles that should go in the documentation or gaps in the current documentation.

    Thanks

    Guy