April 3, 2009 at 6:53 am
The server is DL380 with 8GB physical memory. It has Windows 2003 with SP2 EE and SQL 2005 SP3 EE installed on it.
So does this mean that I need to enable the /3GB switch as well?
April 3, 2009 at 7:10 am
Afternoon,
I believe some of the more recent posts, although naturally only trying to assist, are instead confusing the issue somewhat.
To my understanding the original problem was AWE had not been enabled by the poster. This has since been addressed, i.e. been enabled however the SQL Server Service for the server in question has yet to be restarted.
To reiterate then, once the SQL Server Service has been restarted the AWE memory allocation will take affect.
and then........ the problem is solved, hopefully 🙂
Whether or not the poster should decide to use the /3GB switch is a seperate consideration, to the actual problem at hand and will not influence whether or not this particular configuration can use AWE.
April 3, 2009 at 7:16 am
Just to re-iterate, the SQL Server box was bounced after PAE and AWE was enabled. Even though the OS now recognizes the 8GB memory, Total Server Memory for the SQL counter still shows 1.6GB
April 3, 2009 at 7:29 am
SA (4/3/2009)
Just to re-iterate, the SQL Server box was bounced after PAE and AWE was enabled. Even though the OS now recognizes the 8GB memory, Total Server Memory for the SQL counter still shows 1.6GB
Ah my mistake, for some reason I had thought that this had yet to be done.
I assume that you have performed what Rammesh suggested in order to validate the AWE is indeed enabled, since restarting the SQL Server Service?
EXECUTE sp_configure 'awe enabled'
GO
It should have the values 0, 1, 1, 1
April 3, 2009 at 7:35 am
EXECUTE sp_configure 'awe enabled'
GO
This has the values 0, 1, 1, 0
April 3, 2009 at 7:44 am
Total Server Memory for the SQL counter still shows 1.6GB
Did you see the bit in my post about Task Manager not showing memory use above the 4GB line? You need to look at what SQL Server says it is using to see the impact of AWE.
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
April 3, 2009 at 7:55 am
Did you see the bit in my post about Task Manager not showing memory use above the 4GB line? You need to look at what SQL Server says it is using to see the impact of AWE.
Yes, the total server memory is from the performance counter not from Task Manager.
DBCC MemoryStatus output
Memory Manager
VM Reserved1695112
VM Committed1691656
AWE Allocated0
Memory Node Id = 0
VM Reserved1690952
VM Committed1687648
AWE Allocated0
MemoryClerk_SQLBufferPool (Total)
VM Reserved1654624
VM Committed1654624
AWE Allocated0
It's clearly not using AWE. The only thing that's not setup correctly is the fact that the run_value output from sp_configure 'AWE Enabled' is 0 while the config_value is 1.
April 3, 2009 at 8:06 am
Hi,
Do yo have any other applications installed on server?
Thanks,
Phillip Cox
SQL Server Consultant
MCITP - SQL Server 2008|DBAdmin
MCITP - SQL Server 2005|DBAdmin
MCTS - SQL Server 2008
MCTS - SQL Server 2005
MCP - SQL Server 2000
April 3, 2009 at 8:12 am
I'm currently on SP3 and I understand this is equivalent to SP2 + CU 10. So i don't believe this is what the issue is.
Thanks anyways...
April 3, 2009 at 8:13 am
Try asking for less memory when you start SQL Server. If you ask for more AWE memory than what is available to don't get any of it.
Also make sure you have the fix for SP2 applied. A good fix level is SP3.
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
April 3, 2009 at 8:21 am
EdVassie (4/3/2009)
Try asking for less memory when you start SQL Server. If you ask for more AWE memory than what is available to don't get any of it.Also make sure you have the fix for SP2 applied. A good fix level is SP3.
Ed what fix are you refering to?
We are currently running a number of servers on the base SP2, using AWE without issue?
April 3, 2009 at 8:26 am
SA (4/3/2009)
It's clearly not using AWE. The only thing that's not setup correctly is the fact that the run_value output from sp_configure 'AWE Enabled' is 0 while the config_value is 1.
I agree with you. For some reason, it would appear that you have requested for AWE to be enabled but the grant could not be applied.
If AWE were enabled, you would see a message in the SQL Server log, as described in one of my prior posts.
Have you reviewed the SQL Server logs since you restarted the server, as there may be messages in there that point to a reason for AWE not being enabled?
Also, it may be worth double checking that the 'lock pages in memory' permission has been granted to the SQL Server Service Account, and that the SQL Server Service Account is indeed using the account which it should be.
April 3, 2009 at 8:26 am
Hi,
Have you made sure "Lock Pages in Memory" setting has been configured for correct service account?
Thanks,
Phillip Cox
April 3, 2009 at 8:43 am
I've set the Lock Pages in Memory before configuring AWE. sp_configure 'awe enabled', 1 gave an error without this privilege.
I suspect that reboot the server in the same breadth as configuration of PAE and Lock Pages in memory and AWE may be the reason the AWE setting didn't take effect.
The log has this output in it.
Set AWE Enabled to 1 in the configuration parameters to allow use of more memory.
I read online this indicates that AWE hasn't been enabled for the instance which is apparent from the output of sp_configure (0,1,1,0)
April 3, 2009 at 9:32 am
Ed what fix are you refering to?
Apologies, I got my SQL versions mixed up. However, there are fixes for AWE issues post SP2, but nothing that is pervasive.
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
Viewing 15 posts - 16 through 30 (of 44 total)
You must be logged in to reply to this topic. Login to reply