Poor Man's Enterprise Feature - Lock Pages in Memory

Question

Post reply

Poor Man's Enterprise Feature - Lock Pages in Memory

Viewing 11 posts - 16 through 25 (of 25 total)

You must be logged in to reply to this topic. Login to reply

Paul White SSC Guru Points: 150468 More actions · Answer 1

Kristy Lanter (10/27/2009)
How about Enterprise edition 64 bit?

Enterprise Edition has always had the ability to lock pages in memory.

Paul White
All articles available on SQL.kiwi
@SQL_Kiwi

Kristy Lanter SSC Veteran Points: 232 More actions · Answer 2

Yeah, but what I was wondering was if it was really needed. Back a few years ago I read someplace it wasn't necessary to set it up but I'm doing it anyhow. Just recently experiencing I/O messages. Thanks.

Paul White SSC Guru Points: 150468 More actions · Answer 3

Kristy Lanter (10/27/2009)
Yeah, but what I was wondering was if it was really needed. Back a few years ago I read someplace it wasn't necessary to set it up but I'm doing it anyhow. Just recently experiencing I/O messages. Thanks.

Personally, I always enable it. You don't say what the I/O messages say...?

This article was about lock pages in memory on Standard Edition and the message that can appear to say that a significant part of SQL Server's allocated memory has been paged out. Is that what you're seeing?

Paul White
All articles available on SQL.kiwi
@SQL_Kiwi

Kristy Lanter SSC Veteran Points: 232 More actions · Answer 4

Just researching issues we have that really are not related to the article but came across this article and got me thinking. I was able to lock the issue down to a peice of code that when submitted locked the floor down (casino) and disabled it. Things are good now, just need to fix that code. Good article though.

Chuck Hottle SSCarpal Tunnel Points: 4777 More actions · Answer 5

Is this update required for an environment running SQL Server 2008 SP1 Standard 32-bit using AWE and PAE in order for Lock Pages in Memory to be functional? I only see 64-bit referenced in the various posts that I've seen. Thanks.

Paul White SSC Guru Points: 150468 More actions · Answer 6

Charles Hottle (9/20/2010)
Is this update required for an environment running SQL Server 2008 SP1 Standard 32-bit using AWE and PAE in order for Lock Pages in Memory to be functional? I only see 64-bit referenced in the various posts that I've seen. Thanks.

No the update is for 64-bit only.

See http://blogs.msdn.com/b/psssql/archive/2009/09/11/fun-with-locked-pages-awe-task-manager-and-the-working-set.aspx

Paul White
All articles available on SQL.kiwi
@SQL_Kiwi

brown-415622 SSC Enthusiast Points: 158 More actions · Answer 7

When adding the -T846 where exactly do add the parameter at the very begining? Can you please show an

example, it would be well appreciated.

Thank you

Paul White SSC Guru Points: 150468 More actions · Answer 8

brown-415622 (9/25/2010)
When adding the -T846 where exactly do add the parameter at the very begining? Can you please show an example, it would be well appreciated.

The trace flag is 845 not 846.

You need 2005 64-bit Standard at least SP3 + Cumulative Update 4, or 2008 64-bit Standard at least SP1 + Cumulative Update 2:

http://support.microsoft.com/kb/970070

Here is a link showing how to set it as a start-up option:

http://blogs.msdn.com/b/psssql/archive/2010/02/19/did-you-start-your-sql-server-engine-correctly.aspx

How to know your system is now using Locked Pages successfully:

http://blogs.msdn.com/b/psssql/archive/2007/10/18/do-i-have-to-assign-the-lock-privilege-for-local-system.aspx

How to configure start-up options (general info):

http://msdn.microsoft.com/en-us/library/ms345416.aspx

Using start-up options:

http://msdn.microsoft.com/en-us/library/ms190737.aspx

Paul White
All articles available on SQL.kiwi
@SQL_Kiwi