Re: Alocated Memory Error (SQLSERVR)
- From: "Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 1 Aug 2006 15:38:25 -0400
I'll give you the short answer and please feel free to post back if you have
questions.
- See http://blogs.technet.com/sbs/archive/2006/06/07/433707.aspx. If you
think the alert is misconfigured, fix that and give it a while to see what
happens (ignore the part about this happening when adding ram since the same
guidelines apply anyway). If you're not familiar with this site, I
recommend bookmarking it for future reference - these are the top SBS gurus
at MS support.
- If the above isn't your answer, open Task Manager and view the Processes,
with the PID column showing. Get the PID for the SQL instance in question.
Open a command prompt and type "tasklist /svc" without the quotes. Find
that PID and note which instance of SQL is the culprit (for example,
SBSMONITORING, MSFW).
- You can throttle the instance to use less RAM following the procedure in
the following KB. If the instance whose ram usage you want to throttle back
is not MSFW, substitute the correct instance name in place of MSFW when
following the steps. Use a memory threshold you consider to be practical -
I've used 128 MB for MSFW and monitoring. SharePoint and WSUS haven't used
an unusual amount of RAM so I've left those in their default configurations.
Please carefully note any changes you make in case of unintended results.
You may experience high memory usage on an ISA Server 2004-based computer
that logs messages to an MSDE database
http://support.microsoft.com/kb/909636/en-us
"somebody" <somebody@xxxxxxxxx> wrote in message
news:2wLzg.7636$L31.4664@xxxxxxxxxxx
I have a fully patched SBS 2003 installation that has a problem with
SQLSERVR demanding more memory the longer the system stays active. When I
reboot it start out normally (like other SBS 2003 servers I help support)
but over time it grows to 900mb of total system memory and critical errors
are reported to me about the same.
I don't use exchange server (we use pop mail provided by our ISP and which
is collected by outlook directly - not using pop-connector or shared
exchange server address book or anything exchange related). However my
daily status report is sent out from the server and I think that uses
exchange server to send the daily report.
How can I track down the cause of this error before it becomes a problem.
I haven't had any problem come of this, but that is likely due to the many
recent Windows updates that require restarts about every other week... if
I left this server running for a long time I fear it will run out of
memory.
Thank you!
.
- Follow-Ups:
- Re: Alocated Memory Error (SQLSERVR)
- From: N. Hughes
- Re: Alocated Memory Error (SQLSERVR)
- References:
- Alocated Memory Error (SQLSERVR)
- From: somebody
- Alocated Memory Error (SQLSERVR)
- Prev by Date: Re: Automatic Client Login
- Next by Date: Re: Alocated Memory Error (SQLSERVR)
- Previous by thread: Alocated Memory Error (SQLSERVR)
- Next by thread: Re: Alocated Memory Error (SQLSERVR)
- Index(es):
Relevant Pages
|
