FIX: Locked page allocations are enabled without any warning after you upgrade to SQL Server 2012

Article ID: 2708594 - View products that this article applies to.

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.
Expand all | Collapse all

On This Page

Symptoms

Consider the following scenarios.

Scenario 1
  • You have the Standard Edition of one of the following installed on an x64-based system:
    • Microsoft SQL Server 2005
    • Microsoft SQL Server 2008
    • Microsoft SQL Server 2008 R2
  • You grant the "Lock Pages in Memory" user right to the SQL Server service startup account.
  • You do not enable trace flag 845. Therefore, the instance of SQL Server does not use locked page allocations.
  • You upgrade the instance of SQL Server to SQL Server 2012.
  • You start the upgraded instance of SQL Server.

In this scenario, the upgraded instance of SQL Server starts by using locked page allocations without warning. However, the LPIM check for x64 installations upgrade rule does not warn you about this change in behavior. Additionally, you notice that this rule incorrectly indicates PASSED.

Scenario 2
  • You have the Standard Edition of one of the following installed on an x86-based system:
    • Microsoft SQL Server 2005
    • Microsoft SQL Server 2008
    • Microsoft SQL Server 2008 R2
  • You grant the "Lock Pages in Memory" user right to the SQL Server service startup account.
  • You do not set up and configure the Address Windowing Extensions (AWE) feature. Therefore, the instance of SQL Server does not use locked page allocations.
  • You upgrade the instance of SQL Server to SQL Server 2012.
  • You start the upgraded instance of SQL Server.

In this scenario, the upgraded instance of SQL Server starts by using locked page allocations without warning. However, the LPIM check for x86 installations upgrade rule does not warn you about this change in behavior. Additionally, you notice that this rule incorrectly indicates PASSED.
Back to the top | Give Feedback

Cause

This problem occurs because of a known issue in the upgrade rule code. The upgrade rule incorrectly checks for the "Lock Pages in Memory" user right. Specifically, it checks for the "Lock Pages in Memory" user right for the service security identifier (SID) and not for the service account.
Back to the top | Give Feedback

Resolution

To resolve this problem, apply this fix. This fix corrects the known issue in the upgrade rule code to correctly check for the "Lock Pages in Memory" user right and to warn you during the upgrade. When you use the slip-stream setup method to apply this cumulative update together with the release version of Microsoft SQL Server 2012, the upgrade rule correctly displays the warning.

SQL Server 2012

The fix for this issue was first released in Cumulative Update 2 for SQL Server 2012. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2703275
(http://support.microsoft.com/kb/2703275/ )
Cumulative update package 2 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 2012 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
(http://support.microsoft.com/kb/2692828/ )
The SQL Server 2012 builds that were released after SQL Server 2012 was released
Back to the top | Give Feedback

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

More information

Trace flag 845 is useful in Standard Edition versions of SQL Server to enable the "Lock Pages in Memory" user right to work, as described in the following article in the Microsoft Knowledge Base: 
970070
(http://support.microsoft.com/kb/970070/ )
Support for Locked Pages on SQL Server 2008 R2 Standard Edition x64, on SQL Server 2005 Standard Edition 64-bit systems, and on SQL Server 2008 Standard Edition 64-bit systems
For more information about how to enable the "Lock Pages in Memory" option, go to the following Microsoft TechNet websites:
Enable the Lock Pages in Memory Option (Windows)
(http://technet.microsoft.com/en-us/library/ms190730.aspx)


Lock pages in memory now available for 64 bit Standard Edition of SQL Server
(http://blogs.msdn.com/b/suhde/archive/2009/05/20/lock-pages-in-memory-now-available-for-standard-edition-of-sql-server.aspx)


For more information about how to enable locked pages in SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2659143
(http://support.microsoft.com/kb/2659143/ )
How to enable the "locked pages" feature in SQL Server 2012
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/ )
Description of the standard terminology that is used to describe Microsoft software updates
Back to the top | Give Feedback

Properties

Article ID: 2708594 - Last Review: November 21, 2012 - Revision: 2.1
Applies to
  • Microsoft SQL Server 2012 Business Intelligence
  • Microsoft SQL Server 2012 Enterprise
  • Microsoft SQL Server 2012 Standard
  • SQL Server 2012 Enterprise Core
Keywords: 
kbtshoot kbqfe kbfix kbexpertiseinter kbsurveynew KB2708594
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top