SQLServr.exe Process Memory Leak

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!

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!
>
>

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@pacbell.net> wrote in message
news:uVJrZicsFHA.304@TK2MSFTNGP11.phx.gbl...
> 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!

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@somewhere.local> wrote in message
news:LYqdnZvev5qHG4HeRVn-1g@comcast.com...
> 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@pacbell.net> wrote in message
> news:uVJrZicsFHA.304@TK2MSFTNGP11.phx.gbl...
>> 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!
>
>

Hi,

I had the same memory leak problem. I modify to 100 Mo. But After 1 days, i
received a critical alerts of processor activity (process was staying in idle
time....). And processes stopped atuomatically. example: no more monitoring,
back up reports, RWW,....Why? Do I need to change a value in the alert
threshold?

So i increase the value to 600... But how could i go back to the automatic
settings?
Or why doe he start to stop these services?

Thank you

sebastien


"Anonymous" wrote:

> 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@somewhere.local> wrote in message
> news:LYqdnZvev5qHG4HeRVn-1g@comcast.com...
> > 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@pacbell.net> wrote in message
> > news:uVJrZicsFHA.304@TK2MSFTNGP11.phx.gbl...
> >> 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!
> >
> >
>
>
>

Sebastian, all I did was change the max threshold using OSQL. Sounds like
you have something else at play. Here are the links to the awesome person
who helped me with this! It is all set on this end.

http://msmvps.com/bradley/archive/2005/02/04/34984.aspx
http://msmvps.com/bradley/archive/2005/05/22/48500.aspx

I hope it helps!

"sbDF" <sbDF@discussions.microsoft.com> wrote in message
news:62766175-0AD2-4E05-AA29-EDBBA3FB1748@microsoft.com...
> Hi,
>
> I had the same memory leak problem. I modify to 100 Mo. But After 1 days,
> i
> received a critical alerts of processor activity (process was staying in
> idle
> time....). And processes stopped atuomatically. example: no more
> monitoring,
> back up reports, RWW,....Why? Do I need to change a value in the alert
> threshold?
>
> So i increase the value to 600... But how could i go back to the automatic
> settings?
> Or why doe he start to stop these services?
>
> Thank you
>
> sebastien
>
>
> "Anonymous" wrote:
>
>> 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@somewhere.local> wrote in message
>> news:LYqdnZvev5qHG4HeRVn-1g@comcast.com...
>> > 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@pacbell.net> wrote in message
>> > news:uVJrZicsFHA.304@TK2MSFTNGP11.phx.gbl...
>> >> 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!
>> >
>> >
>>
>>
>>