Re: Low on Virual Memory in SBS 2003

Hmmm...
Am I supposed to be putting a cap on the maximum amount of RAM that Exchange
and/or SQL is permitted to use?
If so, where is that setting and what are reasonable maximums?
TIA.

--

Regards,

Allan C
"Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:ewn3Yj6cGHA.564@xxxxxxxxxxxxxxxxxxxxxxx
Interesting. I'm not inclined to play with this on my production SBS,
which
is the only box I've got with 4 GB RAM, but it's showing a recommended
page
file size of 6142. Of course that doesn't mean it would let me set it
that
high, but logically you'd assume the system wouldn't recommend something
it
didn't allow.

I don't think a memory leak is the only explanation for this. The system
sets the initial size pretty low by default. If something called for a
lot
of RAM faster than Exchange could release it, that could probably trigger
a
page file size increase.

"Maxibo" <totallyanon@xxxxxxxxx> wrote in message
news:ujoxeW6cGHA.4276@xxxxxxxxxxxxxxxxxxxxxxx
Hi Allan

System low on virtual memory is a system leak somewhere. Have all
updates
applied especially Exchange and ISa ? Also SBS SP1.

Task Manager, proccesses, tick show all proceses... does this show
anything ?

Have you increased the memory but not increased the paging file ?

Just to add to Dave 1.5 calculation of RAM is correct but to a maximum
of
4096 (standard 2003 server), therefore cannot have 4.5gb, if had 4gb
memory cannot make pagefile bigger than 4096.


"Allan C" <proven_solutions@xxxxxxxxxxx> wrote in message
news:Or$fW25cGHA.3632@xxxxxxxxxxxxxxxxxxxxxxx
Two questions:
1. I could not see how to *move* it, just how to set the min/max size.
2. I am worried about *why* it needs to increase the page file to begin
with
considering that we have 3 Gb of RAM and maybe only 10 concurrent
users.
I
am concerned that some component of SBS is not behaving properly and
releasing memory when it should.

--

Regards,

Allan C
"Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:%23S%23h9r5cGHA.3556@xxxxxxxxxxxxxxxxxxxxxxx
This is a normal thing. If you go to CP -> System -> Advanced tab ->
Performance -> Advanced again, you'll see the Page File settings. If
you
have an initial size that's smaller than the maximum size, when the
system
wants to use a bigger page file than the initial setting, it'll
dynamically
increase the size of the page file, and you'll get that message.

You can avoid that by setting the initial and maximum settings both to
equal
the recommended size indicated at the bottom of the window. This
avoids
a
(probably brief and minor) performance hit while the page file is
dynamically adjusted, and more importantly avoids page file
fragmentation.
IMO on systems with a lot of RAM this may generally not be worth
bothering
with, but if you're getting size adjustment messages frequently, I'd
do
it.
Keep in mind that on a system with 3 GB RAM the recommended setting is
going
to result in 4.5 GB being dedicated to page file, so you may need to
move
it
off C. Also, page file changes don't take effect until you reboot.


"Allan C" <proven_solutions@xxxxxxxxxxx> wrote in message
news:OUSWLo5cGHA.4312@xxxxxxxxxxxxxxxxxxxxxxx
A client with SBS 2003 is receiving the message below on the server
display.
They have 3 Gb of RAM.
The server was installed about 6 months ago.
Although the SQL Server has been running since the first day, we
only
actually started putting transactions thru about a month ago.
According to the client, the error message below seems to occur over
the
weekend as it is on the server display on Monday morning.
The SQL server logs seem to be clean and I am not sure what to look
for
in
the Event Viewers (or anywhere else).

Thank you in advance.

The message is:"
"Your system is low on virtual memory. Windows is increasing the
size
of
your virtual memory paging
file. During this process, memory requests for some applications may
be
denied. For more information,
see Help."

--

Regards,

Allan C












.

Relevant Pages

  • Re: Locking pages in memory
    ... So I think the 64-bit Standard does not support locked pages in memory. ... Rick Byham, SQL Server Books Online ...
    (microsoft.public.sqlserver.setup)
  • Re: Another SQL Memory Issue
    ... IMO these still do not explain the large allocation of SQL resources. ... It seems to me that some people with SBS throttle the maximum memory ... My SBS has 4 GB of RAM, and it was bugging me to have WSUS using a ...
    (microsoft.public.windows.server.sbs)
  • Re: Large Amount of Memory Message
    ... But wasn't really sure how to match each instance of SQL with a specific ... physical RAM - in other words, if it's using the page file. ... Memory Properties) means so I don't want to necessarily change the alert: ...
    (microsoft.public.windows.server.sbs)
  • Re: Locking pages in memory
    ... the account SQL runs under) the permission to lock pages in memory. ... Server Standard, Enterprise, and Developer editions: Required for SQL Server ...
    (microsoft.public.sqlserver.setup)
  • Re: 300MB DB uses 1.4GB RAM!?
    ... DBCC MEMORYSTATUS will tell you how SQL Server memory manager has ... So, if every page was in memory, there's 300mb. ... the more ram SQL takes the better!! ... allocation for SQL Server. ...
    (microsoft.public.sqlserver.clustering)
Loading