Re: SQLServr.exe Process Memory Leak

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

Hi Susan,

First off, THANK YOU. The changes you had posted on your blog did indeed
help dramatically. The memory usage by the SQLServr.exe process is not
growing by the ridiculously fast rate it previously was. One question I
have is that I set it to 100MB max, but I checked it this morning (almost 24
hours since the change), and it had grown to about 130MB. Should I be
concerned that it has gone beyond 100MB?

I'll continue to monitor it. It will be interesting to see how big it grows
to after a week since it would previously grow to about 970MB.

Thanks again!

"Anonymous" <someone@xxxxxxxxxxxxxxx> wrote in message
news:LYqdnZvev5qHG4HeRVn-1g@xxxxxxxxxxxxxx
> Thanks Susan. Its good to see others have experienced the same issue.
> I've made the changes by setting max memory to 100MB and will see if it
> grows beyond that. Thanks again! PS - great blog!
>
> "Susan Bradley" <sbradcpa@xxxxxxxxxxx> wrote in message
> news:uVJrZicsFHA.304@xxxxxxxxxxxxxxxxxxxxxxx
>> http://msmvps.com/bradley/archive/2005/08/27/64328.aspx
>>
>> Stomp on 'em.
>>
>> Anonymous wrote:
>>> Help. We have lots of SBS 2003 servers running at client locations.
>>> Recently, we setup a ner server with very nice specs (dual Xeon, 2GB
>>> RAM, etc). Unfortunately, the server's available memory is quickly
>>> diminished after a reboot. For example, we boot up and SQLServr.exe
>>> (the one related to SQL$SBSMonitoring) starts at about 15MB used RAM.
>>> After about a week, it grows to about 970MB or used RAM. We are forced
>>> to reboot the server each week. This is a standard install except for
>>> the fact that there is a 3rd paty app (Pervasive SQL based) which has
>>> been installed by a vendor. I'm convinced the Pervasive stuff is
>>> conflicting with the mini-SQL engines that are doing Sharepoint and
>>> performance monitoring out of the box in SBS. This is pretty
>>> frustrating as the client needs the app to run their business so
>>> uninstalling is not an option. There is another process called
>>> NTDBSMgr.exe (related to Pervasive) that is also growing at a steady
>>> rate.
>>>
>>> Has anyone ever seen this? Any info would be much appreciated. Thanks!
>
>


.

Relevant Pages

  • Re: Large Amount of Memory Message
    ... If you have 3 GB of RAM, according to the support blog, that figure should ... Memory Properties) means so I don't want to necessarily change the alert: ... I have seen Susan's blog about changing the throttling for RAM ...
    (microsoft.public.windows.server.sbs)
  • Re: Alocated Memory Error (SQLSERVR)
    ... just search her blog for "allocated memory alerts." ... what you should throttle the RAM to. ... Server 2000 SP4, ... The memory problem on my ...
    (microsoft.public.windows.server.sbs)
  • RE: Terminal Server Specifications
    ... Memory (RAM) ... I see that you are saying you are growing very large very ... Enterprise Edition of Windows Server 2003. ...
    (microsoft.public.windows.terminal_services)
  • RE: Terminal Server Specifications
    ... Memory (RAM) ... I see that you are saying you are growing very large very ... Enterprise Edition of Windows Server 2003. ...
    (microsoft.public.windows.terminal_services)
  • Re: IMGRAM64 problem
    ... I read your message in your blog, ... I did not saw that I have more memory as I got in WinCE 5.0. ... All of the IMGRAMxxx memory configurations you see in the Config.bib ... The amount of RAM you have available may be less than the actual memory ...
    (microsoft.public.windowsce.platbuilder)