I see that memory is pegged, and the display shows a memory alert (yellow
color instead of green). Actual ram shows usage as 5.67 gig of 5.75 gig.
Virtual shows 2gig free.
All other process look low.
This server is a manufacturing system that takes job requests from the web.
We are a check printing house so we crunch allot of postscript as a "job"
that gets sent to one of our big Xerox printers.
Is this something to be concerned with? System has been up for weeks with
out a reboot and I like it that way.
Stephen Russell wrote:
> I am using Spotlight to monitor my servers.
> I see that memory is pegged, and the display shows a memory alert
> (yellow color instead of green). Actual ram shows usage as 5.67 gig
> of 5.75 gig. Virtual shows 2gig free.
> All other process look low.
> This server is a manufacturing system that takes job requests from
> the web. We are a check printing house so we crunch allot of
> postscript as a "job" that gets sent to one of our big Xerox printers.
> Is this something to be concerned with? System has been up for weeks
> with out a reboot and I like it that way.
If you are using the AWE ENabled option with SQL Server, you need to
specify the "Max Server Memory" for SQL Server to prevent it from using
all available RAM on the server. Make sure you leave enough RAM for the
OS and any other services running on the server.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:OUmBtxnoFHA.3696@.TK2MSFTNGP12.phx.gbl...
> If you are using the AWE ENabled option with SQL Server, you need to
> specify the "Max Server Memory" for SQL Server to prevent it from using
> all available RAM on the server. Make sure you leave enough RAM for the
OS
> and any other services running on the server.
Thanks David. I am going to drop SQL Max to only 5.5 gig of total 6 on
machine. My event log has allot of messages for paging errors. I can
restart the server tomorrow before start of business day. I have to give
my
b2b client 12 hrs notice, and that has been delivered.
|||If you really are using AWE then that is still not enough left for the OS.
SQL Server MemToLeave needs up to 384MB by default and that is on top of the
MAX memory setting which is only for the memory pool. Then you need memory
for the OS and any other apps that may be running on the machine. If you
have 6GB total then I would not set the Max memory any higher than 5.0GB.
Maybe even less if there are other apps on the server.
Andrew J. Kelly SQL MVP
"Stephen Russell" <srussell@.lotmate.com> wrote in message
news:%235FY6OpoFHA.3984@.TK2MSFTNGP10.phx.gbl...
> "David Gugick" <david.gugick-nospam@.quest.com> wrote in message
> news:OUmBtxnoFHA.3696@.TK2MSFTNGP12.phx.gbl...
> OS
> Thanks David. I am going to drop SQL Max to only 5.5 gig of total 6 on
> machine. My event log has allot of messages for paging errors. I can
> restart the server tomorrow before start of business day. I have to give
> my
> b2b client 12 hrs notice, and that has been delivered.
>
>
|||"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23mwUbdpoFHA.420@.TK2MSFTNGP09.phx.gbl...
> If you really are using AWE then that is still not enough left for the OS.
> SQL Server MemToLeave needs up to 384MB by default and that is on top of
> the MAX memory setting which is only for the memory pool. Then you need
> memory for the OS and any other apps that may be running on the machine.
> If you have 6GB total then I would not set the Max memory any higher than
> 5.0GB. Maybe even less if there are other apps on the server.
Thanks. I have the max memory usage set to 5 gig. This server is only a
SQL Server box, with nothing else on it.
