July 23, 2008 at 1:38 am
My SQL Server is 2005--64-bit. Do i need to assign SQL service account to be part of "LOCK PAGES IN MEMORY" policy?
Thanks,
July 23, 2008 at 1:51 am
how much RAM does the server have?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 23, 2008 at 1:53 am
24 GB!
July 23, 2008 at 5:23 am
you do need to assign the user account sql runs as to the local policy "lock pages in memory"
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 23, 2008 at 2:50 pm
Thanks for the post.
In what cases do i have to assign the policy "Lock pages in memory" to the service account? I.E say if i have SQL 2005-64 bit with 64GB of RAM - do i still need to assign the service account to that policy?
What about SQL 2000? Say if i have 24 GB on SQL 2000-32 bit. do i still need to do the above?
Appreciated if someone please suggest.
many thanks,
Cali
July 23, 2008 at 3:31 pm
this is the MS description
this explains it too
http://technet.microsoft.com/en-us/library/ms190730.aspx
basically without it set memory can be paged to disk which will cause huge problems for the running SQL instance. Its important to set the min and max server memory also to your required spec, making sure max is higher than min
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 23, 2008 at 4:33 pm
Thanks you SSC - you are just great.
I looked at the provided URL's and have one last question. So say if i am running SQL 2005-64 bit with 64 GB of ram - i still need to enable the lock memory and dont need to worry about AWE.
SQL 2005-32 bit with 64 GB of RAM - i need to enable lock memory policy and as well enable AWE as well too. Yes with min and max memory configuration. right?
Appreciated if you could clarify this.
Thanks again for all your postings.
Cali
July 23, 2008 at 4:50 pm
Note: if you are not running Enterprise Edition, locking pages in memory will not have any effect. The Standard Edition cannot lock pages in memory.
Jeffrey Williams
Problems are opportunities brilliantly disguised as insurmountable obstacles.
How to post questions to get better answers faster
Managing Transaction Logs
July 24, 2008 at 12:52 am
Always, always set the max memory on 64 bit systems with lots of memory. SQL loves memory and will happily starve the OS if permitted.
I've seen my 48 GB server with less than half a GB free memory after the 2005 upgrade when we forgot to set max memory
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 24, 2008 at 9:31 am
just found the MS kb article, it seems 32 bit SQL2005 std can lock pages its just the 64bit that is an issue
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 28, 2008 at 1:08 pm
Another option is get rid of (do not use) the system page file. Works well for us, we have 32Gb of RAM
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply