Re: Allocated Memory Alert



Subhas - welcome to SBS. Don't get discouraged. You can get all the help
you need right here.

For the allocated memory alert, please go to
http://blogs.technet.com/sbs/default.aspx and see the section on allocated
memory errors. It gives step by step instructions on how to change the
alert level so you don't get the errors unnecessarily. You may want to
bookmark this page as it's the official blog of the SBS support group at
Microsoft.

It's normal for Exchange Server to use a lot of RAM. By default, it takes
whatever RAM is available to cache mailbox items in memory for faster
performance, then it gives RAM back as needed by other applications. Unless
you are having specific symptoms or actual problems, you can safely ignore
the amount of RAM used by Exchange no matter how much it grabs.

Exchange RAM usage is not related to storage, which is where the mailbox
quota comes in. You can give your users whatever quota you wish, or no
quota at all. It's been reported that you can't set a quota above 2 GB, but
you can just take the quota off the boss's mailbox if you prefer. That's
what I do - I don't use quotas, and I occasionally monitor to make sure that
no one's mailbox is getting too big.




"Subhas" <Subhas@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5687D0D9-E812-49B9-A7A2-7BC627D1EB21@xxxxxxxxxxxxxxxx
I get a email sayin that a large amount of memor y is committed to
applications and processes. When i look at the task manager and sort the
processes by memory, i notice that store.exe has 400mb and sqlserv.exe has
325mb. Is this normal? so far i have only converted one of the 7 users
onto
the SBS system and his exchange account is using 200mb right now. That
user
could not send/receive emails because his account was too large so i
increased his account size to 2Gigs, since he is the boss, and well, the
boss
doesn't like limits. Is this activity normal? because i've only migrated
one
user from our network onto the SBS so far, i plan to migrate everyone
else,
but so far it doesn't look too good.


.



Relevant Pages

  • Re: Alocated Memory Error (SQLSERVR)
    ... FWIW I am not using sbs 2003 premium, ... non ever going about 200mb of memory usage. ... on what you should throttle the RAM to. ... Server 2000 SP4, ...
    (microsoft.public.windows.server.sbs)
  • Re: Low on Virual Memory in SBS 2003
    ... is the only box I've got with 4 GB RAM, but it's showing a recommended page ... I don't think a memory leak is the only explanation for this. ... Also SBS SP1. ... Although the SQL Server has been running since the first day, ...
    (microsoft.public.windows.server.sbs)
  • Re: 4GBs of RAM Miscount
    ... OS still shows RAM to 2.87 GB ... Most of my sites are <20 users and the only heavy SQL site is still on SBS ... have you ever applied the switch to a SBS 2003 box? ... increases the 'pointers' for memory handling to allow 32b systems to ...
    (microsoft.public.windows.server.sbs)
  • Re: Server running RREEAAALLL slow!
    ... With 1 gb of ram or more, you need the /3gb switch for sure. ... Les Connor [SBS MVP] ... >> If you install ISA on SBS 2003 the default setting for caching memory is ...
    (microsoft.public.windows.server.sbs)
  • RE: 2003 SBS stalling randomly
    ... and I am experiencing the same stalling of SBS 2003 ... memory and Store using upwards of 750 MB of memory. ... The server was unable to allocate from the system nonpaged pool because the ... Press P twice to display allocations from only the paged pool. ...
    (microsoft.public.windows.server.sbs)