Ask Learn
Preview
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign inThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Consider the following scenario on a X64 system:
You install SQL Server [2008 R2, 2008, 2005] standard edition.
You grant the "Lock Pages in Memory" user right to the SQL Server service startup account.
You did not enable the trace flag 845, as a result the SQL Server instance did not use locked page allocations
Now you attempt to upgrade this SQL Server instance to SQL Server 2012.
Now the upgraded SQL Server instance starts using locked page allocations.
There is a upgrade rule named "LPIM check for x64 installations" which is supposed to warn you about this change in behavior. But you notice that this rule indicates PASSED for the above circumstances.
Consider the following scenario on a X86 system:
You install SQL Server [2008 R2, 2008, 2005] standard edition.
You grant the "Lock Pages in Memory" user right to the SQL Server service startup account.
You did not setup and configure the ‘awe enabled’ feature, as a result the SQL Server instance did not use locked pages allocations
Now you attempt to upgrade this SQL Server instance to SQL Server 2012.
Now the upgraded SQL Server instance starts using locked page allocations.
There is a upgrade rule named "LPIM check for x86 installations" which is supposed to warn you about this change in behavior. But you notice that this rule indicates PASSED for the above circumstances.
The upgrade rule shows a PASSED status due to a bug in the upgrade rule code. The upgrade rule incorrectly checks for the "Lock Pages in Memory" user right assignment.
A bug is filed and work is underway to fix this in a future Cumulative Update.
You can find more information about the change in behavior from the Knowledge Base article:
2659143 How to enable the "locked pages" feature in SQL Server 2012
https://support.microsoft.com/default.aspx?scid=kb;EN-US;2659143
Aaron Bertrand originally blogged about these two rules not working in the blog: https://sqlblog.com/blogs/aaron_bertrand/archive/2012/02/06/upgrading-to-sql-server-2012-with-lock-pages-in-memory.aspx
Thanks
Suresh Kandoth
Microsoft
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign in