Ken ... when you use dynamic memory allocation, SQL Server works with the OS
to help the OS maintain a minimum amt of memory (about 5 meg if memory (oops
... bad pun) serves me correctly. Once SQL Server has taken the mem it
needs, it doesn't necessarily give it back right away, but only when the OS
demands it back.

Look up "Monitoring memory Usage" in BOL for more info, or look in the
microsoft.public.sqlserver groups.

Hope this helps

Tom


-----Original Message-----
From: Ken Nickels [mailto:[Email Address Removed] Monday, June 23, 2003 9:53 AM
To: LazyDBA.com Discussion
Subject: How to read this performance counter


Hi folks

I had noticed that certain large queries were taking more and more time to
execute. When I looked at Perf monitor I noticed that my "Total Server
Memory" counter was up at 100. After a reboot on Friday it came back down
to a low value and has since crept up to around 56 - Monday morning. I ran
the big query again and it didn't budge. But when I ran checkdb it went up
to 68 and did not come back down.

Can anyone tell me how to read this counter? Is it a high threshold value?
If the counter never comes down does that mean that that amount of memory is
now claimed and unusable. The explanation window in the Perf counter says
"Total amount of daynamic memory the server is currently consuming"

Why didn't it come back down after checkdb? As to the long execution time, I
will check the execution plan but still I am puzzled about the perf monitor.

Thanks

---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To unsubscribe, e-mail: mssqldba-[Email Address Removed] additional commands, e-mail: mssqldba-[Email Address Removed]MS Sql Server LazyDBA home page