February 14, 2005 at 6:26 am
Hai,
I was just observing the SQL Server Memory utilisation.
In the system Monitor -->SQL Server Memory Object -->Target Server Memory (Maximum memory SQL Server can use), it is showing around 6.6 GB
But i had given the Max Memory Parameter as 8 GB.
Why it is not showing 8 Gb in the Target Server Memory, it is supposed to be 8 Gb right ?
Can anybody tell me why and what this difference means ?
----------------------------------------------------------------
Similarly i am seeing conflicts in the following areas also,
System Monitor --> Sql Server Memory Object --> Total Server Memory (memory sql server is using) as 70 MB
In the Windows Task Manager --> SQLServer.exe is cousiming 160 MB
--------------------------------------------------------------------
Is it problem with my understaing the terminologies ? pls correct me
subban
February 15, 2005 at 3:03 am
Target Server Memory is what SQL wants to use.
Total Server memory is what SQL is actually using.
I can't remember off-hand, but as you must be using AWE then some of these counters are not reliable as SQL uses physical memory directly rather than it's virtual address space.
Why have you set "Max memory" to 8 GB?
When using AWE memory, SQL doesn't dynamically manage memory, it uses the value set by "Max memory", so you are telling SQL to use ALL memory on the server...
Unless you're using datacenter edition of the OS and you have more than 8Gb RAM in your server...
If I had 8Gb RAM, I'd set max memory to 6.5 or 7 GB...
February 16, 2005 at 8:32 am
Hai gbn,
No, i am not using AWE (run value is '0'). infact my OS is Windows 2003 Enterprise Edition (64 bit) running on Itanium based processor machine , in this case i don't think of any memory addressing problem to use /PAE or AWE , am i right ?
subban
February 16, 2005 at 8:35 am
Oh.
In that case, I'm sorry but I have no experience of 64 bit and wouldn;t know if there are any issues or differences with plain old 32 bit.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply