Re: Large Amount of Memory Message

On the server, open a cmd prompt and type "tasklist /svc" without the
quotes. It'll give you the instance names for each of those PIDs.

Time Matters does sound like the culprit, though. I can't recall ever
seeing any of the built-in instances go that high. If it's that, you could
mention it to their tech support to see if they have recommendations.
Personally, I wouldn't mess with that instance unless they sign off on your
plan, especially in the absence of negative symptoms.

"thomas" <thomas@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:37CF8081-52C0-454B-B107-F2C6F02E65F3@xxxxxxxxxxxxxxxx
It should be our main application (Time Matters/Billing Matters Enterprise
7.0).

But wasn't really sure how to match each instance of SQL with a specific
application.

I have 4 Instances of SQL running. With PID # 1956, 1968, 1984, and 2004.

Thomas

"Dave Nickason [SBS MVP]" wrote:

If you have 3 GB of RAM, according to the support blog, that figure
should
be set to 3221225472.

It's alerting you if the server is using more memory than the amount of
physical RAM - in other words, if it's using the page file. It's not
that
any one process is using an abnormal amount of RAM, but rather that the
total RAM in use by the server is high. If you have a single SQL
instance
using 1.8 out of 3 GB, I'd say that's a big part of the cause. What's
running in that instance?


"thomas" <thomas@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:650FF589-3FC7-4D8E-8FD1-36C36CFBF761@xxxxxxxxxxxxxxxx
Mr. Nickason,

I guess my problem is I don't understand what this expression (for
Allocated
Memory Properties) means so I don't want to necessarily change the
alert:

If the average value of Committed Bytes [Real Number] Is greater than
3500000000
(3.5GB).

Before I learned how to interact with this property I assumed it was
related
to the SQL instance that was using 1.8 GB of memory. But now I don't
think
that is the case.

Besides I only have 3 GB of RAM memory so how would it every go over 3
GB?

If you would please explain this Expression for me because I'm
obviously
not
understanding.

I only care about this because it was set up as default not because of
any
symptons.

Again, thanks for you patience.

Thomas
"Dave Nickason [SBS MVP]" wrote:

You don't really need to throttle that memory IMO. What I initially
did
when I was getting these alerts daily was to ignore them for a month.
Then
I went in and set the alert threshold to 110 or 120% of the 30-day
average
value. If you're not having specific symptoms that lead you to want
to
make
adjustments, I'd just up the alert threshold rather than mess with
SQL.

For anything you change from its default, I recommend keeping a
written
record of the default setting in case you get an unintended result.


"thomas" <thomas@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:05BDF6AC-3DF9-4014-96D5-82B45E6C3140@xxxxxxxxxxxxxxxx
Thanks Mr. Nickason for the quick reply.

The first site was very helpful except now I don't know what is
causing
the
problem.

Once I've gone to the Health Monitor > Right click on Allocated
Memory
Properties:

The Expression I have is "If the average value of Committed Bytes
[Real
Number] Is greater that 3500000000 (3.5 GB).

So I'm not sure what that is pertaining to or what is causing this
value?

Also, I have seen Susan's blog about changing the throttling for RAM
for
SQL
instances, should I do this? I didn't think it need to be done.

Thomas

"Dave Nickason [SBS MVP]" wrote:

I recommend going to this article and verifying that the alert
settings
are
correct. This is the blog of top-level SBS support at MS, so
please
add
to
your feeds or bookmark for future reference. These guys watch the
community
for common issues, so there's always a lot of good stuff here.

Allocated Memory Errors After Adding RAM
http://blogs.technet.com/sbs/archive/2006/06/07/433707.aspx

Failing that, I'd search Susan Bradley's blog for information on
throttling
the RAM allocation for SQL instances. Susan's blog is a primary
source
of
relevant and current info about SBS, and other small business
computing
issues, and also lots of good security stuff.

http://msmvps.com/blogs/bradley/default.aspx

"thomas" <thomas@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A68D2660-34A7-43E4-9EF1-F96CEA20E52B@xxxxxxxxxxxxxxxx
Hello All! Please give me some guidance.

We currently have SBS 2003 SP1 and 3GB of Memory.

I've been receiving this alert:

"A large amount of memory is committed to applications and
processes.
Consistently high memory usage can cause performance problems.

To determine which processes and applications are using the most
memory,
use
Task Manager. Monitor the activity of these resources over a few
days.
If
they continue to use a high level of memory and are less critical
processes
or services, try stopping and then restarting them.

You can disable this alert or change its threshold by using the
Change
Alert
Notifications task in the Server Management Monitoring and
Reporting
taskpad."

The SQL process is using (Under Task Manager > Processes > Mem
Usuage)
1.8
GB of memory. I'm assuming the alert above is pertaining to
this
process.
This is our primary use for SBS other than for file sharing. It
the
alert
it
says "you can disable this alert", but I haven't been able to
figure
out
how
to do that.

Am I correct in my assesment, that SQL is causing this alert?
Should I
allow SQL to reserve 1.8 GB of memory? IF so how to I disable
the
alert.
I've gone to the Monitor and Reporting under Server Management,
but
have
been
unable to find this specific alert.

Thanks for you assitance,

Thomas














.

Relevant Pages

  • Re: 2 Critical Alerts since I added more RAM
    ... This newsgroup only focuses on SBS technical issues. ... Do you SBS server encounter any performance issue? ... The inetinfo.exe process uses lots of memory and memory usage continues to ... the allocating more memory than usual alert ...
    (microsoft.public.windows.server.sbs)
  • Re: Performance problems -- need guidance on scaling
    ... Thanks for the update on the FT Catalog corruption, ... will use, up to a max of 512Mb, if this memory is available. ... a server with 512 MB of RAM and a resource_usage value of 5 ... the data, you could, detach your SQL 2000 mdf & ldf files ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Memory Issues
    ... Exchange and SQL Server. ... you identified memory problems and large amounts of paging. ...
    (microsoft.public.sqlserver.setup)
  • RE: Process (Inetinfo.exe) Alert
    ... Thank you for posting in SBS newsgroup. ... I understand that you received memory allocation ... alert of the inetinfo.exe process from the SBS 2003 server. ... You may safely ignore this alert. ...
    (microsoft.public.windows.server.sbs)
  • Re: 2 Critical Alerts since I added more RAM
    ... Exchange Server 2003 in a Small Business Server environment. ... you check it for more information to optimize memory usage. ... Click Change Alert Notifications, ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
Quantcast