August 29, 2007 at 10:15 am
I ran across the following link regarding Lock Pages in Memory. The link is in the 2005 BOL, but my question is does it apply also to SQL 2000. The following statement has me concerned.
"On 32-bit operating systems, setting this privilege when not using AWE can significantly impair system performance."
http://msdn2.microsoft.com/en-US/library/ms190730.aspx
I believe with SQL 2000 Lock Pages in Memory is automatically set for the service account used to install SQL Server. If you change service accounts after the installation the option must be manually set. My question is does the above warning only apply to SQL 2005 or also to SQL 2000?
Thanks, Dave
August 30, 2007 at 11:45 am
DBADave, I have used this setting as a default on all of my SQL 2000 servers (at least 200+) for a number of years (when did SQL 2000 come out) now with no ill affects at all. I do also set min/max memory to the same value and always leave 1 Gb left over for the OS. When you use this option on Windows 200 servers you will get a warning message in the SQL Server errorlog on startup that says is cannot lock (insert large curious number here) in memory - ignore it, it is a known spurious message generated by the SQL Server. When you use this option on a Windows 2003 server it is ignored and the SQL Server errorlog will state that - or so they say. In both cases I contacted SM PSS and received this informatino under our support agreement. Hope this helps
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply