Re: Memory Usage

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: David Copeland [MSFT] (davidcop_at_online.microsoft.com)
Date: 02/10/05


Date: Wed, 9 Feb 2005 19:10:59 -0600

Brandon,

Keep in mind that by default, Exchange and SQL will both try to use as much
ram as they can, giving back ram when needed. Also, keep in mind that SBS
2003 only supports up to 4gig of RAM.

For SQL memory usage then you might look at
http://support.microsoft.com/?id=321363

If you have more that one SQL instance running on the machine then you can
run

tasklist /svc
to get a list of the process id's for the different instances.
Then use task manager to see which process id is using the ram

For example if it is the sbsmonitoring instance you might then do something
like the following to limit the amount of RAM it should use.

osql -E -S servername\sbsmonitoring
> sp_configure 'show advanced options',1
> reconfigure with override
> go
> sp_configure 'max server memory', nnnn
> reconfigure with override
> go

where nnnn is the maximum amount of ram you want it to use.. (must be at
least 4 which would be 4mb) You would need to determine the value for your
environment/application.

If you have SQL Enterprise Manager you could right click on the
server\instance name and select Properties, then click on the Memory tab.

-- 
Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Newsgroups:
SBS v4.x : microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Brandon" <bsmith@presentationsdirect.nospam.com> wrote in message 
news:eeUbURrDFHA.512@TK2MSFTNGP15.phx.gbl...
>I have an SBS server that was using on average about 2.5 GB of memory when 
>I looked inside Task Manager > Performance.  The server only had 2GB of RAM 
>installed, so it was usually cutting into the paging file.  So I added an 
>additional 2GB of RAM.  Now, when I look in Task Manager it shows that the 
>server is using on average about 3.5 GB of memory!
>
> I'm confused why adding memory caused it to start using more memory.  I 
> would expect it to still show 2.5GB of usage, but now without cutting into 
> the paging file.  SQL server is the biggest memory hog (about 2.5 GB). 
> So, (1) Is this jump normal after adding memory and (2) Is this usage 
> amount normal with SQL server or should I (can I) limit the amount of 
> memory that SQL can use.
>
> -- 
> Brandon Smith
> IT Director
> Presentations Direct - Specialized Office Equipment & Supplies
> http://www.presentationsdirect.com
>
> 


Relevant Pages

  • Re: Alocated Memory Error (SQLSERVR)
    ... but my understanding is that the MSDE instances are designed to ... and you don't want it grabbing all that RAM. ... running but non ever going about 200mb of memory usage. ... Server 2000 SP4, ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows 2000 Server StandardEdition /PAE Question
    ... specifically the SQL Server 2000 Standard Edition on that server. ... His point is that applications can only use up to 2 GB or RAM on ... a process running under Windows 2000 or Windows Server 2003 can ... used) with some of the memory being physical memory and some being virtual ...
    (microsoft.public.win2000.general)
  • 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: Alocated Memory Error (SQLSERVR)
    ... what you should throttle the RAM to. ... Server 2000 SP4, ... The memory problem on my ... shared exchange server address book or anything exchange related). ...
    (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)