Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««123»»

Poor Man's Enterprise Feature - Lock Pages in Memory Expand / Collapse
Author
Message
Posted Friday, October 16, 2009 1:14 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, April 03, 2014 12:46 PM
Points: 1,413, Visits: 4,531
we always install the HP management software, anti-virus, Emulex HBA Anywhere. The HP software also installs a light version of Apache or Tomcat, forget which one. a lot of people will also install SSIS and other SQL components other than the database engine as well as other database vendors' drivers

https://plus.google.com/100125998302068852885/posts?hl=en
http://twitter.com/alent1234
x-box live gamertag: i am null
[url=http://live.xbox.com/en-US/MyXbox/Profile[/url]
Post #804483
Posted Friday, October 16, 2009 1:19 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 3:30 PM
Points: 41,531, Visits: 34,448
Jeff Moden (10/16/2009)
Heh... wouldn't a reasonable alternative be to only have SQL Server on the SQL Server box?


Unfortunately not. I've heard of a case where SQL was the only thing installed on the box (other than OS) and and it was still getting paged out if max memory was set about about 60% of the total memory. This is a server with >16GB.

Suspicion was a driver bug, but couldn't be sure.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #804486
Posted Friday, October 16, 2009 1:32 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, April 03, 2014 12:46 PM
Points: 1,413, Visits: 4,531
few years ago Emulex and Windows 2003 x64 SP2 had an I/O bug and it caused one of our servers to lock up and reboot. MS released a series of hotfixes and everyone from Emulex to HP released updated drivers for HBA's and RAID controllers

https://plus.google.com/100125998302068852885/posts?hl=en
http://twitter.com/alent1234
x-box live gamertag: i am null
[url=http://live.xbox.com/en-US/MyXbox/Profile[/url]
Post #804492
Posted Friday, October 16, 2009 5:42 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 10:03 PM
Points: 11,168, Visits: 10,934
Jeff Moden (10/16/2009)
Heh... wouldn't a reasonable alternative be to only have SQL Server on the SQL Server box?

On the face of it, yes. And, most of the time, this will work well. However, you are then at the mercy of Window's memory manager - any sudden requests for memory from any other process are likely to result in some of SQL Server's address space being paged out. It is an inviolable law of the universe that it will occur at the most inconvenient time.

There are many things that can cause sudden demands for memory from Windows, even if you lock the server down and carefully control who has access and what processes can run. Not being able to lock memory for SQL Server on 64-bit Standard Edition just introduced a whole new set of avoidable problems.

Paul




Paul White
SQL Server MVP
SQLblog.com
@SQL_Kiwi
Post #804620
Posted Tuesday, October 27, 2009 8:25 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, November 26, 2013 7:40 AM
Points: 162, Visits: 25
How about Enterprise edition 64 bit?
Post #809350
Posted Tuesday, October 27, 2009 2:53 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 10:03 PM
Points: 11,168, Visits: 10,934
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
SQL Server MVP
SQLblog.com
@SQL_Kiwi
Post #809598
Posted Tuesday, October 27, 2009 3:19 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, November 26, 2013 7:40 AM
Points: 162, Visits: 25
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.
Post #809617
Posted Tuesday, October 27, 2009 3:25 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 10:03 PM
Points: 11,168, Visits: 10,934
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
SQL Server MVP
SQLblog.com
@SQL_Kiwi
Post #809620
Posted Wednesday, October 28, 2009 7:26 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, November 26, 2013 7:40 AM
Points: 162, Visits: 25
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.
Post #809909
Posted Monday, September 20, 2010 10:59 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, April 15, 2014 3:04 PM
Points: 198, Visits: 1,116
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.
Post #989580
« Prev Topic | Next Topic »

Add to briefcase ««123»»

Permissions Expand / Collapse