SQL Server 2008 Cumulative Update 2 for SP1 - support the concept of Locked Pages for Standard Edition
During the keynote session of European PASS 2009 Bob Ward from Microsoft CSS team has announced about standard SKU for SQL Server 2005 and 2008 version to enable 'Locked Pages in Memory' privilege that will allow the hardware resources to use the AWE threads. As you may be aware about 'locked pages' configuration option to assist the problems related to working set within SQL Server.
In continuation to SQL 2008 CU2 post here it is a wonderful news for DBAs to hear that this cumulative updates for SQL Server 2008 and 2005 to support the concept of Locked Pages for SQL Server Standard edition. As referred by Bob Ward's blog post you need to follow the steps from KBA that talks about the change in the CU to support Locked Pages for SQL Server Standard: Support for Locked Pages on SQL Server 2008 Standard Edition 64-bit systems
Further to this process the following steps are required to enable this support:
- A pre-requisite of SQL Server 2008 Service Pack1 should be followed.
- Enable the trace flag 845 as a startup parameter for that instance.
- Then apply the changes to the service account for SQL Server services has 'Locked Pages in Memory' privilege set.
- If you are using a local system account then above step is not-required.
- Also see how to use slipstream support to install RTM, SP1, and CU 2 all in one setup execution.
I recommnd this KBA How to reduce paging of buffer pool memory in the 64-bit version of SQL Server which indicates the process which applies to both SQL Server 2005 and 2008 versions and many more details about 'locked pages','working set trim' and blurb about enable the same for 64 bit systems.
Finally you can download this SQL Server 2008 Cumulative Update 2 for SP1 and best practice word is to test the update thoroughly in your pre-production environment that will have similar workloads as per your production environment.