Re: MSSQL 2000 Standard Edition not utilizing Maximum Memory!!!

From: Dan Guzman (danguzman_at_nospam-earthlink.net)
Date: 04/30/04 

Date: Fri, 30 Apr 2004 07:39:35 -0500

Are you running other applications on the server besides SQL Server? SQL
Server will manage memory based on amount of free memory available.
Consequently, if other apps running on the same box (e.g. IIS) consume
significant amounts of memory, SQL Server won't acquire additional memory
because this would negatively impact performance. 

-- 
Hope this helps.
Dan Guzman
SQL Server MVP
"vasum" <anonymous@discussions.microsoft.com> wrote in message
news:E2239F3D-53B5-4DA7-B7AC-280DC8B54ED7@microsoft.com...
> Hi All,
>
> Can anybody tell me why Memory is not utilized by MSSQL Service. The
Environment as follows...
>
> It is an Critical Web based Application with SQL 2000 Standard Edition +
SP3 as backend .
> OS: Win 2000 Advanced Server + 3GB Memory + 2 CPU
>
> MSSQL Memory Configured as Dynamic with Maximum Memory has been set as "2
GB". This Server has Replication
> Configuration also. During peak time or non-peak time, it always use 1 GB
Memory only. Why MSSQL is not taking more than 1 GB, even though server has
got 3 GB and database's max. memory configured as 2 GB.
>
> In SQL 2000 Enterprise Edition, to utilize more than 2 GB for database, we
will give /3GB in boot.ini. Similarly anything should be given for SQL 2000
Standard Edition. Right now, boot.ini doesn't contain this option.
>
> Appreciate your help on this.
>
> tks in advance,
> vasum
>

Relevant Pages

  • 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: Memory issues with 64-bit SQL Server 2005 on 64-bit Win 2003 Clust
    ... The Paging File usage is due to how the large memory allocation APIs work. ... Swap files for SQL do not need to be more than about 2-4 GB regardless of physical memory on the box. ... If you use Performance Monitor to track actual paging activity, you will see very little on a properly tuned SQL Server. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Memory issues with 64-bit SQL Server 2005 on 64-bit Win 2003 C
    ... Manager nusance has been around, and yet they somehow could never find time ... counter Total Server Mmeory shows 18GB. ... due to how the large memory allocation APIs work. ... Swap files for SQL do not need to be more than about 2-4 GB ...
    (microsoft.public.sqlserver.clustering)
  • Re: Allocating more memory to sql server
    ... Are you sure you have Windows 2000 Advanced Server and not just Server? ... SQL Server. ... memory used by SQL Server that will give a better idea of the actual usage. ... You also need to restart SQL Server after enabling AWE for it to take ...
    (microsoft.public.sqlserver.setup)