November 19, 2007 at 6:31 pm
Server configuration : 6Gb ram, Windows 2000 Advanced Server,SP4 Build 2195, SQL Server 2000 Enterprise Edition (sp4).
In boot.ini is set
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Advanced Server" /fastdetect /3GB /PAE
I've set max server memory (MB)Minimum--> 4Maximum--> 2147483647Config_value--> 4096 run_value--> 4096
awe enabledMinimum--> 0Maximum--> 1Config_value-->1run_value-->1
My problem is I allocated 4 GB, but in SQL- SQL Server Memory Manager -- Total Server memory (KB) and Target Server Memory (KB) showing only --> 3127104.
Please help me to resolve this issue.
Regards,
Renju
November 19, 2007 at 9:45 pm
Hi,
Total Server Memory (KB), tells you how much the mssqlserver service is currently using. This includes the total of the buffers committed to the SQL Server BPool and the OS buffers of the type "OS in Use".
Target Server Memory (KB), tells you how much memory SQL Server would like to have in order to operate efficiently. This is based on the number of buffers reserved by SQL Server when it is first started up.
In my opinion, if Target Server Memory (KB) showing only --> 3127104 (it means SQL will work efficiently with about 2.9G of ram) and SQL Sever is conuming just 2.9 because, at this moment he does not need more.
Check the link http://www.sql-server-performance.com/tips/performance_monitor_memory_counter_p1.aspx
Regards,
Ahmed
November 21, 2007 at 3:29 pm
ranjithputhan (11/19/2007)
Server configuration : 6Gb ram, Windows 2000 Advanced Server,SP4 Build 2195, SQL Server 2000 Enterprise Edition (sp4).In boot.ini is set
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Advanced Server" /fastdetect /3GB /PAE
I've set max server memory (MB)Minimum--> 4Maximum--> 2147483647Config_value--> 4096 run_value--> 4096
awe enabledMinimum--> 0Maximum--> 1Config_value-->1run_value-->1
My problem is I allocated 4 GB, but in SQL- SQL Server Memory Manager -- Total Server memory (KB) and Target Server Memory (KB) showing only --> 3127104.
Please help me to resolve this issue.
Regards,
Renju
You need to have the service account running SQL Server have the Lock pages in memory permission to use AWE. See this link: http://msdn2.microsoft.com/en-us/library/ms190730.aspx
November 21, 2007 at 6:22 pm
Hi All,
Thanks for your valuable information, But both Total Server memory (KB) and Target Server Memory (KB) showing same figures (3127104).
Service account running SQL Server also having permission in the Lock pages in memory.
Microsoft support resolution is to apply hotfix for resolving this issue.
http://support.microsoft.com/kb/899761/.
Please let me know your valuable comments on this.
Regards,
Renju
November 22, 2007 at 6:33 am
Task manager, etc, does not show figuers for any memory allocated as AWE memory. The figures you are seeing are the best you will get. As you are at fix level 2195 the fix you mention will do nothing, as you already have it installed as part of 2195.
With AWE, if the memory you ask for is not available when SQL starts, SQL will continue without using AWE. You need to use the performance counters for AWE to confirm that AWE memory is in use.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
November 23, 2007 at 2:28 am
The same had the case with me and i have applied the fix to get use of my memory. I had fixed memory on sql to use 3gb and previously it was doing 1.9gb, even after enabling awe and boot.ini settinigs. After the fix it does started using 3gb. My build is also 2195.
Murali.a
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply