|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Sunday, May 05, 2013 3:41 PM
Points: 110,
Visits: 368
|
|
Comments posted to this topic are about the item Poor Man's Enterprise Feature - Lock Pages in Memory
------------------------------------------------- -Amit Give a man a fish and he'll ask for a lemon. Teach a man to fish and he wont get paged on weekends !! - desparately trying to fish
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Sunday, July 03, 2011 7:09 AM
Points: 258,
Visits: 494
|
|
All the Microsoft links point to info about the 64-bit versions of Windows. Is this feature restricted to this platform?
Random Technical Stuff
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 6:43 AM
Points: 37,738,
Visits: 30,008
|
|
ta.bu.shi.da.yu (10/15/2009) All the Microsoft links point to info about the 64-bit versions of Windows. Is this feature restricted to this platform?
No, but it tends to be most useful (and most necessary) on 64 bit.
On 32 bit, Lock pages is required to use AWE.
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
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Thursday, May 02, 2013 12:25 PM
Points: 525,
Visits: 215
|
|
What about SQL 2008? Is this an option there?
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: 2 days ago @ 8:15 PM
Points: 1,409,
Visits: 4,509
|
|
we had this when we first went to x64 and there was almost nothing on the internet to document the differences except a MSDN blog post by a Microsoft developer who now works in another department.
we ended up enabling it and all the problems went away. Funny thing is that out of our 3 main servers we only saw the problem on one of them. even on the server that does a lot of huge batch processing we didn't see this. the problem server was tens of millions of queries daily all with different parameters and variables
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]
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 6:43 AM
Points: 37,738,
Visits: 30,008
|
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 6:09 AM
Points: 5,270,
Visits: 11,209
|
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Thursday, June 02, 2011 12:18 PM
Points: 3,
Visits: 86
|
|
according to microsoft this is supprtedin standard 32 bit edition prior to sp3cu4
i have seen the errors you get in the log when you need to add the lock pages in mem policy to the id running sql server and adding stopped the error messages. this is for 32 biut standard edition. i am not so sure I believe any of this blog.
Locked pages in memory operating system (OS) privilege (Allows locking physical memory, preventing OS paging of the locked memory.)4 SQL Server Standard, Enterprise, and Developer editions: Required for SQL Server process to use AWE mechanism. Memory allocated through AWE mechanism cannot be paged out.
Granting this privilege without enabling AWE has no effect on the server.
http://technet.microsoft.com/en-us/library/ms187499(SQL.90).aspx
|
|
|
|
|
SSChampion
        
Group: General Forum Members
Last Login: Today @ 1:49 AM
Points: 10,990,
Visits: 10,540
|
|
ta.bu.shi.da.yu (10/15/2009) All the Microsoft links point to info about the 64-bit versions of Windows. Is this feature restricted to this platform? The problem only affects 64-bit Standard Edition.
In 32-bit Standard Edition, we could grant 'lock pages in memory' and enable AWE to lock buffer pool pages. In 64-bit Standard Edition, prior to SP3 CU4 (2005) or SP1 CU2 (2008), there was no way to achieve the same effect.
This was a shocking omission by Microsoft - it is a shame it has taken them so long to correct it. Using a trace flag to enable it seems overly conservative: a trace flag to disable it would seem more sensible, but never mind.
Not sure why anyone should regard this as more useful or necessary on 64-bit systems (which tend to have more memory, if anything) compared to 32-bit systems, but hey.
Paul White SQL Server MVP SQLblog.com @SQL_Kiwi
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 7:10 AM
Points: 32,910,
Visits: 26,801
|
|
|
|
|