|
Home > Archive > MS SQL Server New Users > November 2005 > sqlservr.exe Mem usage grows to all available RAM, system stops responding
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
sqlservr.exe Mem usage grows to all available RAM, system stops responding
|
|
|
| SBS 2003 Premium edition, dual Xeon, 2GB RAM, separate SCSI hard drives for
system and pagefile, data on SATA RAID5, no clients connected, only default
data files.
On boot-up one of 3 instances of sqlservr.exe in Task Manager grows over a
period of some 24 hrs from around 70MB initially to take all of available
RAM causing the system to stop responding to mouse clicks or keyboard
inputs, only way out is the reset button. This is accompanied by a constant
churning of hard drives with VM Size corresponding to Mem Usage, i.e.
growing to some 2GB.
Setting lower Memory limits in SQL configuration makes no difference
whatsoever. No error messages in log files.
All updates installed, NAV corporate and MS Antispyware also installed.
| |
| Mike Epprecht \(SQL MVP\) 2005-11-13, 1:24 pm |
| The memory utilization is by design
http://support.microsoft.com/defaul...kb;en-us;321363
The fact that your server becomes unresponsive indicates that
1. your disks are not coping with the throughput. RAID-5 is the least
performing RAID types. SATA drives generally do no support command queuing,
slowing IO even more. Your server is spending all it's time servicing
requests and interrupts.
2. You application may be far from optimally tuned and the tables may not be
indexed correctly.
Work your way though
http://www.sql-server-performance.c...icles_audit.asp to identify the
problem.
Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"AZ" <rem.alienzord@gmail.com> wrote in message
news:eZESMkH6FHA.2888@tk2msftngp13.phx.gbl...
> SBS 2003 Premium edition, dual Xeon, 2GB RAM, separate SCSI hard drives
> for system and pagefile, data on SATA RAID5, no clients connected, only
> default data files.
>
> On boot-up one of 3 instances of sqlservr.exe in Task Manager grows over a
> period of some 24 hrs from around 70MB initially to take all of available
> RAM causing the system to stop responding to mouse clicks or keyboard
> inputs, only way out is the reset button. This is accompanied by a
> constant churning of hard drives with VM Size corresponding to Mem Usage,
> i.e. growing to some 2GB.
> Setting lower Memory limits in SQL configuration makes no difference
> whatsoever. No error messages in log files.
> All updates installed, NAV corporate and MS Antispyware also installed.
>
>
| |
| Joe Yong 2005-11-14, 8:24 pm |
| You mention that there are no clients connected. Does that mean none of the
3 instances are actually servicing clients/queries? SQL Server takes memory
when it needs to but if there's no load and it is taking memory, might wanna
call a young priest and an old priest and... oops, sorry. Wrong script. :-)
Seriously, if there are no clients, look to see what jobs are running
(enterprise manager --> current activity, or just sp_who2 from query
analyzer). If you do have active workloads running, look at the links
provided by Mike to figure out which
app(s) is the culprit here.
joe.
"AZ" <rem.alienzord@gmail.com> wrote in message
news:eZESMkH6FHA.2888@tk2msftngp13.phx.gbl...
> SBS 2003 Premium edition, dual Xeon, 2GB RAM, separate SCSI hard drives
> for system and pagefile, data on SATA RAID5, no clients connected, only
> default data files.
>
> On boot-up one of 3 instances of sqlservr.exe in Task Manager grows over a
> period of some 24 hrs from around 70MB initially to take all of available
> RAM causing the system to stop responding to mouse clicks or keyboard
> inputs, only way out is the reset button. This is accompanied by a
> constant churning of hard drives with VM Size corresponding to Mem Usage,
> i.e. growing to some 2GB.
> Setting lower Memory limits in SQL configuration makes no difference
> whatsoever. No error messages in log files.
> All updates installed, NAV corporate and MS Antispyware also installed.
>
>
| |
|
| Hi, I had a good diagnostic session with the machine last Saturday and found
the culprit. It was the ISA server writing log records to a database every
half to 3 seconds! I have uninstalled it as its not needed this time but
will investigate it next time it is required in a SBS2003 installation.
Cheers, Lou.
"Joe Yong" < NO_jyong_SPAM@scalab
ilityexperts.com> wrote in message
news:eC%235uSX6FHA.1248@TK2MSFTNGP14.phx.gbl...
> You mention that there are no clients connected. Does that mean none of
> the 3 instances are actually servicing clients/queries? SQL Server takes
> memory when it needs to but if there's no load and it is taking memory,
> might wanna call a young priest and an old priest and... oops, sorry.
> Wrong script. :-)
>
> Seriously, if there are no clients, look to see what jobs are running
> (enterprise manager --> current activity, or just sp_who2 from query
> analyzer). If you do have active workloads running, look at the links
> provided by Mike to figure out which
> app(s) is the culprit here.
>
>
> joe.
>
>
> "AZ" <rem.alienzord@gmail.com> wrote in message
> news:eZESMkH6FHA.2888@tk2msftngp13.phx.gbl...
>
>
| |
|
| M$ recommend 550MHz processor with 384MB RAM. This system is a dual 3.2GHz
Xeon with 2GB RAM, SCSI system drives capable of 75MB/s data transfer and
RAID5 array using NCQ SATA drives capable of sustained 55MB/s so performance
could not possibly be at fault! No, as I stated in another reply it was a
rogue ISA server, part of SBS2003 premium, writing log records up to twice a
second into a database file. Most likely a bug in the ISA server or
SBS2003's default configuration.
"Mike Epprecht (SQL MVP)" <mike@epprecht.net> wrote in message
news:usHKvAI6FHA.1248@TK2MSFTNGP14.phx.gbl...
> The memory utilization is by design
>
> http://support.microsoft.com/defaul...kb;en-us;321363
>
> The fact that your server becomes unresponsive indicates that
> 1. your disks are not coping with the throughput. RAID-5 is the least
> performing RAID types. SATA drives generally do no support command
> queuing, slowing IO even more. Your server is spending all it's time
> servicing requests and interrupts.
> 2. You application may be far from optimally tuned and the tables may not
> be indexed correctly.
>
> Work your way though
> http://www.sql-server-performance.c...icles_audit.asp to identify the
> problem.
>
> Regards
> --------------------------------
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
>
> IM: mike@epprecht.net
>
> MVP Program: http://www.microsoft.com/mvp
>
> Blog: http://www.msmvps.com/epprecht/
>
> "AZ" <rem.alienzord@gmail.com> wrote in message
> news:eZESMkH6FHA.2888@tk2msftngp13.phx.gbl...
>
>
|
|
|
|
|