Hello, all.
We've got a 64-bit Windows 2003 Enterprise VM, running SQL 2005 SP2 x64. We initially created this VM with 2GB of RAM and 2 vCPUs. Also, we configured SQL to use only 1024MB of RAM maximum.
We recently upped the virtual hardware for the VM to 8GB of RAM and 4 vCPUs, and also modified SQL Server to use the default maximum (2147483647), in other words, dynamically allocate as much RAM as possible.
After restarting SQL Server, the SQL Server process only ever appears to use ~1.7GB of memory (according to Task Manager's "Mem Usage" column). The PF Usage counter in Task Manager is reporting 7.44GB usage. TM also report 8GB of PHysical memory, and only 145MB Available.
So, given all that, is SQL Server actually using more than 2GB of RAM and TM is just reporting the wrong figure? How can I tell how much RAM SQL Server is using, exactly, if that figure is wrong?
Thanks in advance.
Do you have SQL set to dynamically configure RAM (usually the default). Check the SQL server memory settings, the sliders should indicate how much memory SQL sees and is configured to use.
download process explorer from sysinternals (now microsoft)
freeware, working fine on x64 O/S and way more powerfull than task manager, is self contained: no dll in your windows system, no installation required, just drop the exe somewhere and you're set
then in p.e. add the column "private bytes" to your list and look at the sql process
you'll see the memory allocated by sql
anyway, the memory usage in taskman should evolve once your sql server is stressed (large queries permitting SQL to allocate ram to cache the results)
Message was edited by:
rsa911