February 23, 2009 at 12:29 am
Hi,
I want enable AWE and I have little confusion.Please give me ur Suggestions.
( sql-2005 EE and windows server 2003 R2 enterprise-32 bit)
As per Microsoft
(In Windows Server 2003, PAE is automatically enabled only if the server is
using hot-add memory devices. In this case, you do not have to use the /pae
parameter on a system that is configured to use hot-add memory devices.
In all other cases, you must use the /pae parameter in the Boot.ini file
to take advantage of memory over 4 GB.)
http://msdn.microsoft.com/en-us/library/ms175581(SQL.90).aspx
I want know the followings.
1.How do I know Hot-Add memory configured or not in OS
2.Hot-Add memory is configured don't enable /PAE (As per MS)
3.If i enable both (Hot-Add memory and /PAE) means what's the impact.
4.When I enable the both (/PAE and /3GB) in boot.ini
Here Another Question
As per Microsoft before enable the AWE give the SQL account permission to
Lock pages in memory This's for both windows 2000/2003 OS.
Thanks & Regards,
Muthu,
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
February 23, 2009 at 1:49 pm
You have to use 'lock pages in mmory' privilege on 32-bit operating systems.
MJ
February 23, 2009 at 2:06 pm
firstly how much RAM does the server have and how many sql instances?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 23, 2009 at 10:17 pm
Help me,
1.How do I know Hot-Add memory configured or not in OS
Hi,
Thanks for ur replays.I have 2-Question.
Case:1
I have 16 GB RAM and 2-node A/P Cluster.(AWE not enabled) Server running Very Very...slow[server taking 1.5 gb RAM only]
[sql-2005 EE and windows server 2003 R2 enterprise-32 bit,16-RAM]
Case:2
I have Enabled AWE another machine following ways
[sql-2005 EE and windows server 2003 R2 enterprise-32 bit,16-RAM]
Min memroy-1 Gb
Max memory-8 Gb
Enable the Awe And Restart the Server-only.
Here,
I don't know Hot-Add memory configured or not in OS.(So I m not set /PAE and /3GB in boot.ini)
I couldn't give the the sql account permission to Lock pages in memory.
I monitored the server It's taking 8 GB RAM running fine.I don't know any problem occur in future.Please Assist me.
Thanks,
Muthu,
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
February 24, 2009 at 5:07 am
PAE is automatically enabled only if the server is
using hot-add memory devices
This does not prevent you from adding /PAE to BOOT.ini even if you have hot-swap memory. All it is saying is you don't need to add it if you have hot-swap memory.
PAE is also automatically enabled if you have Data Execution Prevention turned on for all programs. DEP uses PAE facilities to do its work. However, no harm will occurr if you have /PAE in BOOT.ini as well as DEP turned on.
One of the functions provided by PAE is the ability for Windows to access memory above the 4GB line. Each 4KB page above the 4GB line is given a number. When a program that can exploit PAE wnts to use the data in one of these pages, it asks Windows to copy the memory below the 4GB line so the program can access it. If the contents of the page get changed then Windows has to copy it back to its original location, otherwise if no changes have ben made it can be discarded when another 4KB page is requested.
SQL Server can exploit PAE, but only for its buffer pool, via the use of the AWE option. If you have PAE turned on (explicitly or implicitly) in Windows and have AWE turned on in SQL Server then SQL can store some of the buffer pool above the 4GB line.
It is easy to see that exploiting PAE is not very efficient, compared to directly accessing the memory in a 64-bit environment. IMHO the standard configuration for new SQL Server installations should be 64-bit Windows 2008 and 64-bit SQL Server 2008. It is only if you are using facilities that are not available on 64-bit that you should consider 32-bit.
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
February 24, 2009 at 7:05 am
no harm will occurr if you have /PAE in BOOT.ini as well as DEP turned on
Hi EdVassie,
Thanks for ur Replay It's Great.
Again one Question
I couldn't give the the sql account permission to Lock pages in memory in OS level.(Win-2003 R2-EE).I didn't face any problem yet now.
I see the following counters,
Please give me ur suggestion which one is showing bad value
counter_nameCntr_valueCntr_Type
Buffer cache hit ratio 6084537003264
Lazy writes/sec 15515272696576
Checkpoint pages/sec 780877272696576
AWE lookup maps/sec 11038909511272696576
AWE stolen maps/sec 57767568272696576
AWE write maps/sec 681938272696576
AWE unmap calls/sec 63530858272696576
AWE unmap pages/sec 11097272533272696576
Page life expectancy 245865792
Page life expectancy 245865792
Connection Memory (KB) 81665792
Target Server Memory (KB) 838860865792
Total Server Memory (KB) 838860865792
Thanks,
Muthu
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
February 24, 2009 at 8:19 am
The counters show that you are successfully using AWE. What problem do you think you have?
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
February 24, 2009 at 10:25 pm
The counters show that you are successfully using AWE
EdVassie,
Thanks for ur Replay,Yes the server now running fast but,
I am not give the the sql account permission to Lock pages in memory in OS level because We didn't restart machine now.(Win-2003 R2-EE).
I got following message in sql-error log
Configuration option 'max server memory (MB)' changed from 2147483647 to 8192.
Run the RECONFIGURE statement to install.
SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans'
cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans'
cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees'
cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
After Restart the sql-server
Address Windowing Extensions is enabled. This is an informational message only; no user action is required.
Here my Question is,
I must give the sql account permission to Lock pages in memory or not.
Thanks,
Muthu...
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
February 25, 2009 at 5:20 am
In your situation you will not get any extra benefits from applying Lock pages in memory.
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
February 25, 2009 at 5:48 am
In your situation you will not get any extra benefits from applying Lock pages in memory.
Hi,
Y i get extra benefit. (May I know the reason)
Thanks,
Muthu,
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
February 25, 2009 at 6:15 am
muthuuu (2/24/2009)
I got following message in sql-error log
Configuration option 'max server memory (MB)' changed from 2147483647 to 8192.
Run the RECONFIGURE statement to install.
SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans'
cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans'
cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees'
cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
the following link
http://support.microsoft.com/kb/917828
details the problem mentioned above
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply