Re: Seems like only 1GB RAM being used even when higher MAX RAM is

Well something certainly isn't adding up here. What are the values of both the target and total server memory for the SQL Server memory counters? How much free memory does Perfmon show? If you really are querying more than 2GB worth of different data you should see the memory usage go to about 1.7GB with that configuration. I see the Max Memory was set to ~3GB which is more than what you have but just to rule it out you may want to rest that back to the default of the max as well. Are you sure there isn't some other app on the server that may be eating up memory? Are there any settings in the boot.ini that are not default? You should really think about upgrading the OS and SQL Server in the near future anyway. Std edition in 2005 & 2008 can use the max memory that the OS can access and if there was anything funky with the OS or SQL builds an upgrade should surely fix that.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Larry Epn" <larryepn@xxxxxxxxxxxxxxx> wrote in message news:A2B07884-5E2B-48EC-AA5B-897523AAD809@xxxxxxxxxxxxxxxx
Thanks,
I made that change:
sp_configure 'set working set size',0
reconfigure
(restarted sqlserver.exe)
confirmed current runtime setting = 0
Ran a bunch of huge queries, large transactions, beat up the server, etc...
Memory usage still seems stuck at right at 1,062Mb.

Anyone, anyone, anyone ? :)
Larry

"Andrew J. Kelly" wrote:

No you don't have AWE enabled but you do the the "set working set size"
enabled and it should be off. Change that back to the default and you
probably have to restart but I bet that will fix it.


--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Larry Epn" <larryepn@xxxxxxxxxxxxxxx> wrote in message
news:79448FCB-7570-4837-B5D4-AB2195C9FE4A@xxxxxxxxxxxxxxxx
> Man, you had me going for a minute, unfortunately it does not apply
> because
> AWE is not configured on this server:
> name minimum maximum config_value run_value
> awe enabled 0 1 0 0
>
> Also, this computer has 4Gb, and I am just trying to get it to use 2Gb
> instead of the 1Gb it is using, so even 50% of the available memory > would
> be
> a "good thing" in my particular case. Right now it will only use 25%.
>
> Larry
>
>



.

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: 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)
  • 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)
Loading