May 21, 2010 at 5:01 pm
Hi
I need help with awe
i have SQL 2008 installed on windows server 2003. server memory is 8GB. i used in SQL
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'min server memory', 1024
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
but doesn´t work the AWE, what can i do?
May 21, 2010 at 6:03 pm
What do you mean it doesn't work? Do you get an error message?
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
May 21, 2010 at 6:13 pm
sorry for my English but I speak Spanish
I dont get an error message
in another server with the same features, i run a store procedure and the SQL used 2G of memory, but in this server the same sp don´t use the memory
May 21, 2010 at 6:20 pm
How are you determining that the SP isn't using any memory? Does the procedure execute and return the desired results? Does it take less/more time than on the other server?
How are you determining how much memory SQL Server is using?
Is this x86 or x64 machine?
If this is an x86 machine, did you set the lock pages in memory policy? In other words, did you add the user that is running SQL Server to that local security policy?
If it is an x64 machine - then you don't have to do anything for SQL Server to use the additional memory. You don't have to 'enable' AWE on x64 systems - it is already going to be used.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
May 21, 2010 at 6:54 pm
ok i try to explain the situacion
I have two server with this features
Server 1
64 bits
Windows server 2003 32 bits
SQL SERVER 2005
16 G
Server 2
64 bits
Windows Server 2003 32 bits
SQL SERVER 2008
16 g
on both servers y congifured the awe with 14.5 G
i check the uses of memory in the Task Manager
When i run the sp in the Server 1 the task manager show me physical memory usage with 14.5 g
The same sp in the Server 2 the task manager show me physical memory usage 2 g
And the Server 1 never ends to run the sp
Thanks for you help
May 21, 2010 at 7:17 pm
Sorry, but this isn't clear - are you running x64 or x86 versions of the OS and SQL Server?
Run the following in a query window on both servers: SELECT @@VERSION
If I understand correctly, server 1 is currently using 14.5 GB of memory - which is normal since you set the max to that value.
Server 2 is currently only using 2GB of memory, which is probably normal because there hasn't been enough done on that server to increase the memory usage.
Does the proceudre complete on either server?
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
May 21, 2010 at 9:49 pm
Don't worry i know that my english isn't not good
Server 1
OS x86
SQL 2005 x86
RAM 16 G
Server 2
OS x86
SQL 2008 x86
RAM 16 G
In the server 1, in the server properties of SQL 2005 the "maximun server memory" is 14.5 G
In the server 2, in the server properties of SQL 2008 the "maximun server memory" is 14.5 G
In the server 1 the sp complete correctly
In the server 2 the sp don´t finish
In the task manager i saw that the server 1 used all memory reserver 14.5 G
But in the server 2 i saw that only used 2G
May 21, 2010 at 10:43 pm
Okay - so, have you verified that the lock pages in memory policy has been set for the service account running SQL Server? If that is not set, AWE will not be enabled on that server.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
May 22, 2010 at 12:31 am
all the service account running SQL Server are administrator of the OS
but how can i check the lock pages in memory policy?
May 22, 2010 at 2:19 am
Francisco Lopez Lopez (5/22/2010)
all the service account running SQL Server are administrator of the OS but how can i check the lock pages in memory policy?
For the 2008 server, you can look at the DMV sys.dm_os_process_memory - the locked_page_allocations_kb column. This will be non-zero if the server is using locked pages.
If it is SQL Server Standard Edition, you will need at least 2008 SP1 Cumulative Update 2 or 2005 SP3 Cumulative Update 4, and to enable Trace Flag 845 to use locked pages. See http://support.microsoft.com/kb/970070 for details.
The steps required to enable AWE can be found here: Enabling AWE Memory for SQL Server
Also see: How to: Enable the Lock Pages in Memory Option (Windows)
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
May 22, 2010 at 4:29 am
presuming all else has been done as described above to get SQL to us it after you enable the AWE sp_configure option use
reconfigure with override
not just reconfigure
then bounce SQL
---------------------------------------------------------------------
May 23, 2010 at 7:11 pm
Do you make what Jeffrey Williams said?
Verified that the lock pages in memory policy has been set for the service account running SQL Server?
If that is not set, AWE will not be enabled on that server.
It solve my problem!!!!
Try that!!
Fabrício França Lima
MCITP – Database Administrator
https://www.fabriciolima.net/Blog
May 26, 2010 at 8:43 am
HI!!
Thank you for your help but I still have the same problem
i verified the lock pages in memory policy and the service account running SQL is there
I look sys.dm_os_process_memory and the locked_page_allocations_kb column is non-zero
but the SQL server don't use all the memory and the sp don't finish
May 26, 2010 at 9:10 am
in the error log at startup does it say
Set AWE Enabled to 1 in the configuration parameters to allow use of more memory.
or
Address Windowing Extensions is enabled. This is an informational message only; no user action is required.
---------------------------------------------------------------------
May 26, 2010 at 10:37 am
Thank you all for your help
It solved the problem I only starting the service "virtual disk service" and SQL now uses all available memory.
But i don't know what is the relationship of this service with AWE. Someone could explain me?
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply