Re: SQL server memory usage on new server

What are you using to measure the memory usage? How large is your database
and are you accessing more than 3.5GB of data? I am not sure there is a 64
bit eval edition so I bet you are using a 32 bit one. If so then you are
getting all you can without using AWE. You need the x64 bit edition to
directly access more than 4GB of memory.

--
Andrew J. Kelly SQL MVP

"Ryan S." <Ryan S.@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0E874815-D1A9-48C6-BB1A-BB34040971B6@xxxxxxxxxxxxxxxx
We just purchased a new server as a sole DB server for our company. We
are
running Server 2k3 R2 64-bit, and SQL Server 2k5 evaluation (we are
currently
deciding which version would work best for us). Our new server is a Dell
PowerEdge 2950, dual quad core, 16 GB ram, 6 SAS 15k-rpm drives (two
volumes
configured; two disks raid 1 for OS, and four disks configured raid 10 for
sql data).

After our initial testing, we installed the server in production on
Friday.
We are starting to see some bottlenecks today. Our main problem is the
amount of memory that SQL is using. We are currently using around 3.5 GB
of
memory, and we currently have over 11 GB free physical memory. The
concern
with this is we were using a server from our software development firm
with
the same data in use, their server was using over 6.5 GB of memory (our
server is using 3,553,280kb for SQL, and that number hasnâ?Tt changed
since
Friday when the server went live).

What would cause SQL to not take more memory? The server was setup to use
dynamic memory allocation, should this be changed to a static size? With
the
lack of memory allocation our disk queue times have been average around
15 -
20, with the peaks in the mid 300 range.



.

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)