First published on MSDN on May 19, 2009
Note this article has been updated to include an update for SQL Server 2005
I
posted
in April that we would be releasing cumulative updates for SQL Server 2008 and 2005 to support the concept of
Locked Pages
for SQL Server Standard.
SQL Server 2008 Cumulative Update 2 for SP1 was released yesterday to provide this support. You can download the CU at:
http://support.microsoft.com/kb/970315
SQL Server 2005 Cumulative Update 4 for SP3 was also recently released to provide this support. You can download this CU at:
http://support.microsoft.com/kb/970279
We have published a KB article that talks about the change in the CU to support Locked Pages for SQL Server Standard:
Support for Locked Pages on SQL Server 2005 Standard Edition 64-bit systems and on SQL Server 2...
As you can read in the article, you must do the following to enable this support:
1) Install the Cumulative Update (which requires you first install SQL 2008 SP1. Remember if you have not installed SQL Server 2008 yet, you can use
slipstream
support to install RTM, SP1, and CU 2 all in one setup execution).
2) Enable trace flag 845 as a startup parameter
3) Ensure the service account for SQL Server has the
Locked Pages in Memory
privilege set. This is not required if the service account is LOCAL SYSTEM.
As part of this change, we have updated the following KB article (note the article is updated to indicate it applies to both SQL Server 2005 and 2008) that has many more details about Locked Pages, Working Set Trim, and the possible ramifications of enabling this for 64bit systems.
How to reduce paging of buffer pool memory in the 64-bit version of SQL Server.
Bob Ward
Microsoft
