July 25, 2007 at 3:07 am
When I look in Task Manager it seems that the memory usage for the sqlservr.exe process is the same as the PF usage - why would it not be using any of the 8GB of RAM available before using the virtual memory?
The other processes are using negligible memory so there should definitely be plenty of RAM available.
July 25, 2007 at 5:18 am
To my knowledge SQL Server never uses page file when RAM is readily available. You can check this with perfmon counters.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 25, 2007 at 6:41 am
Paul - also, can you give us some detail about what version SS 2k5 you're using, and some information about your platform - op sys, processors, etc.
July 25, 2007 at 7:13 am
here you go:
July 25, 2007 at 8:22 am
if sql is using awe you can't use task manager to view memory usage.
I don't have a full running 64 bit to hand to check but I'm still sure that extended memory use is not reported still in 64bit task manager.
SQL Server should not page, however, 64bit has an issue in as much as if you do not set max memory and lock pages in memory then sql server actually ends up using the page file. ( well in ent+ent x64 it does ) Setting awe on/off does not affect this.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
July 25, 2007 at 8:57 am
i have now locked pages in memory using gpedit.msc.
when running the job the pf usage still went up to 2gb even though there was at least 6gb ram still available?
July 25, 2007 at 10:06 am
There is no reason to assume that the amount of SQL Server memory usage is related to the page file usage.
Take a look at the Performance Monitor, Process, Working Set and Virtual Bytes for the SQL Server process. They will tell you how much memory SQL Server is currently using and how much it would use if the entire process was in memory.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply