Re: Seems like only 1GB RAM being used even when higher MAX RAM is

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Earlier in the thread, all memory usage shown in task manager has been
verified by using the PerfMon to look at memory usage in addition to many
other parameters (paging, disk %, etc, typically used to troubleshoot a SQL
server) Because of the consistent correlation between what Task manager is
showing and PerfMon is showing, I've just been referencing Task Manager since
an earlier post in this thread because it is easier to pull up. If total
usage in the system is 1.4Gb (including all OS, etc), then it is clear that
SQL can't be using all 2Gb (or even 1.7Gb) RAM. But thanks for your input.
The most difficult problems always turn out to be the most satisfying to
solve.

"Aaron Bertrand [SQL Server MVP]" wrote:

Everything you're saying about how much memory is being used, seems to be
evidenced only from Task Manager. A couple of questions have asked about
what performance monitor says about total server memory and target server
memory, but I haven't seen your answer to those questions. I'd also be
curious about what is reported under the MSSQL:Memory Manager/Buffer Manager
counters. (I never trust Task Manager to really tell me how much memory is
being used by SQL Server... it usually lumps the higher memory allocated to
SQL Server into PF usage instead. Performance Monitor does not try to pull
the wool over your eyes like this.)

Also, are there any observable symptoms that make you believe that less RAM
is being used? I didn't review every single message in the thread but I
don't see anything about actual performance problems. I'm not always a fan
of "it ain't broke, don't fix it" but if you have no actual symptoms of
insufficient memory, and are chasing this just because you saw the number in
task manager and didn't like it...



On 7/22/08 10:35 PM, in article
9362B897-200B-4E44-8FF4-435928B82E0A@xxxxxxxxxxxxx, "Larry Epn"
<larryepn@xxxxxxxxxxxxxxx> wrote:

Yes, it appears you understand the situation perfectly.
There are no other significant applications that run on this server. It is
not a domain controller, nor an IIS Server, nor a DNS server, etc. The
largest memory allocation in task manager is sqlservr.exe at 1,064Mb, with
rtvscan.exe a distant second at 52Mb.
Total Mem Usage (task manager): 1411372K / 5794148K (of course the amount
above the 4Gb is the pagefile.)
In this case, if all apps were to share the 2Gb, then I would expect
sqlserver.exe to at least be using around 1.7Gb calculated as 2Gb (available
for all Windows applications) - 1411372 (current total usage) + (1067400
current sql usage) = 1.66Gb for sqlservr.exe. (Yes, I know I've rounded
badly and it is all to the advantage of reduced space for sqlservr.exe for
sake of argument, so no need to clarify that a Gb is > 1000Mb, etc)
So after all this, there is still no explanation that sqlservr.exe is not
using all the memory it should.
Next I will try the 3Gb option and see what happens....even though
theoretically, I shouldn't need to do this - but I'm willing to try just
about anything.
Larry



.

Relevant Pages

  • Re: SBS2003 blank desktop after login
    ... I am at home now but I managed to login to the server using RWW without ... "Disconnected" - I tried to log it out in task manager but it had no ... I guess I'll try remote rebooting and see. ... Sometimes processes just hang, lock up, or leak memory. ...
    (microsoft.public.windows.server.sbs)
  • Re: Terminal Server running extremely slow
    ... When I check the CPU % within Task Manager, it will sit at 100% for several ... Also, within the Task Manager, the Memory display seems to be 50 to 65% used ... server has been running extremely slow. ...
    (microsoft.public.windows.terminal_services)
  • Re: Memory issues with 64-bit SQL Server 2005 on 64-bit Win 2003 C
    ... I would suggest your systems are vastly under-speced for memory. ... Microsoft SQL Server MVP ... I also checked the individual patch levels for the .NET drivers, SQL Server ... >> and even on a pure x64 box, this Task Manager nusance is still ...
    (microsoft.public.sqlserver.clustering)
  • Re: Problems with users logging in
    ... Look specifically at Paged Pool memory usage. ... in Task Manager in the Kernel Memory section. ... maximum on your server should be near 266240KB. ... RAM and it always has plenty of free physical RAM, ...
    (microsoft.public.windows.terminal_services)
  • Re: .NET on XPE and paging files
    ... I think what Task manager shows is just what virtual memory usage counter ... The VM size in Task manager doesn't really mean process VM usage but rather ... How does the app work on XP Pro? ...
    (microsoft.public.windowsxp.embedded)