Skip to main content

Lock Pages in Memory

It is generally recommended that 'lock pages in memory' be enabled for your SQL Servers to prevent the OS paging out SQL Server memory.

how do you do this?

Well, the answer is straight forward...If you have SQL Server Enterprise Edition:

You allocate the service account running SQL Server the 'Lock Pages In Memory' permission.

How Can I Tell if 'Lock Pages in Memory is Enabled?'


I am using Windows 2003 R2 and SQL Server 2008 SP1 for this demo but I have also done this on Windows 2008 R2 and it works just the same way. It is a 64 bit environment.

If you are running SQL Server with the Local System account, I know most of you are not, but for those of you that are, SQL Server will automatically 'lock pages in memory'. Bob Ward has a blog post on this here: (

If you are using the local system or a domain account with appropriate permissions you will see an entry similar to the following at the start of the SQL Server log:


Therefore if you are running SQL Server using a domain account and the domain account does not have the necessary permissions to lock pages in memory then you will not have this message in the log:


If you do not have 'Lock Pages In Memory' enabled and you would like too enable it then follow these steps:

Logon to the SQL Server in question

Click <Start><Run> and enter 'secpol.msc' in the run box.

In the 'Local Security Policy' window that opens expand <Local Policies> and <User Rights Assignment> in the left hand pane.


In the right hand pain scroll down to the 'lock pages in memory' policy. Right Click, select <Properties> <Add User or Group> and add the domain account that is running the SQL Service and click <OK>


That's it, you need to restart the SQL Server service for the change to take effect, the next time that SQL Server starts up you should see


in the SQL Server log.

Standard Edition

Up until SQL Server 2005 SP3 Cumulative Update Package 4 and SQL Server 2008 SP1 Cumulative Update Package 2 'Lock Pages in Memory' was not supported in SQL Server Standard Edition.

You may find this link helpful

as you need to request the CUs from Microsoft. They will then send you a link to download the CU.

These two CUs add the 'lock pages in memory' option for SQL Server Standard edition.

Note you you have to enable trace flag 845 to for standard edition to be able to 'lock pages in memory.'

Virtualisation, SQL Server and Lock Pages

Are you running SQL Server in Virtual Land, well here is something else to to consider care of Mr Denny:


Popular posts from this blog

SQL Server 2012 and Virtual Service Accounts

This post is written by David Postlethwaite
If you are using SQL Server 2012 you will probably have noticed that the default account for the SQL services has changed from that used in previous versions. With SQL 2005 and 2008 the default account for SQL service and SQL Agent service was “NT Authority\System”. This is one the built in accounts on a Windows machine, managed by the machine and selectable from a dedicated dropdown list

The Network Service account was introduced in Windows 2003 as an alternative to using the LocalSystem account, which has full local system privileges on the local machine, a major security concern.
The Network Service has limited local privileges easing these security concerns but when many services on a machine use the Network Service account it becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account.
Also, this account, by default, has sysadmin per…

Always Encrypted

By David Postlethwaite

Always Encrypted is new features in SQL Server 2016 and it is also available in Azure SQL Database. Here you can encrypt columns in a table with a master key and a certificate so that they will appear as encrypted strings to those who don’t have the required certificate installed on their pc.
Once the certificate is installed on the computer then the unencrypted data can then be seen as normal.

The data passes from database to your application as the encrypted value, only the application with the correct certificate can unencrypt the data so it is secure across the wire. This will go some way to resolving the concern of people worried about putting their sensitive data on a shared server in the cloud such as Microsoft Azure and accessing the data across the Internet.

At the time of writing Always Encrypted is only supported with ADO.NET 4.6, JDBC 6.0 and ODBC 13.1 but expect other driver to become available.

The calling application (including SSMS) must also hav…

New in SQL Server 2017: Graph Databases

David has recorded and published a video of his presentation on SQL Server Graph Database. In his video which you can watch below, David provides an excellent introduction into SQL Server 2017 Graph Databases. In his presentation he looks at Tennis results at tournaments for  his favourite player "The Fed"  Rodger Federer.

David  shows how to set up graph database and work with them in SQL Server 2017.

Graph Database is not new. Other vendors have had graph database capabilities for some time so Microsoft are quite late to the market. In David presentation it appears that Microsoft have done a reasonable job of implementing some of the graph database features but he does point some of the limitations of the Microsoft product too and suggests that it is not ready for production yet but Microsoft seem serious about this feature.

Please watch the video and feel free to leave a comment or feedback - David is delivering a version of this talk on Graph databases in SQL Saturday Ka…