February 12, 2009 at 1:35 pm
Hope someone can explain this
I am running 64 bit standard and I am getting a sql page dump after target and total memory = each other for a while. This seems to be a known problem. cant use lock pages since this is standard.
I currently have the dynamic memory runnning, I am a ware I need to set the max setting down a bunch as this could be one of my problem for the dump. and therefor cure my problem.
when target and total are = my page file utilization is about 13 % but after a reboot or mem dump it sits at 100% until target and total are = again.then is drops to around 10%
so my ? is what is causing the 100% page file? The buffer manager is 99.9 and life expectancy is 10,000 +. avail memory is about 6 gig so it seems the paging can not be an OS issue. Page/sec is almost nothing. processor is about 15-20% so it seems that the processors should not need to go the page file to get memory either it should be able to use cache.
My only guess is the page file is being used every time a page is brought in memory?
Thanks
February 16, 2009 at 2:02 am
you cannot use dynamic memory management with x64 sql server, you must set a max memory at least and give the o/s adequate room - ideally around 6GB as a minimum.
You're quite right you cannot use lock pages in memory.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply