dbTalk Databases Forums  

SQL 2005 Std 32-bit A/P cluster will not use AWE

Go Back dbTalk Databases Forums Databases microsoft.public.sqlserver.clustering SQL 2005 Std 32-bit A/P cluster will not use AWE

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering


Discuss SQL 2005 Std 32-bit A/P cluster will not use AWE in the microsoft.public.sqlserver.clustering forum.



Reply
Page 12 of 12 « First < 2 3 4 5 6 7 8 9 10 11 12
 
Thread Tools Display Modes
  #111  
Old   
Bonzer
 
Posts: n/a

Default Re: SQL 2005 Std 32-bit A/P cluster will not use AWE - 02-15-2008 , 09:42 AM





Hi Jeff,

The '/noexecute=optout' option is in both node boot.ini's

Server properties shows 8191MB memory available

dbcc Memorystatus (memory manager) shows:
VM reserved = 2710992 kb
VM committed = 2709888 kb
AWE allocated = 0 kb
resserved memory = 1024 kb
reserved memory in use = 0 kb

It appears to see the memory but is not using anything beyond the 3GB.

I will likely call Dell first and then Microbuddies to get to the bottom of
it, very strange indeed......



"Jeffrey Williams" wrote:

Quote:
The only other thing I can think of is the /noexecute option in the
boot.ini. I have seen issues where having this set to anything other
than /noexecute=optout will cause problems with the system recognizing
all of the memory.

Does SQL Server even see all of the memory? What are the values for the
memory manager from DBCC MEMORYSTATUS? When you look at the properties
for the instance, how much memory does SQL Server say is available?

If all of that looks correct - then I think it is time to get Dell and
Microsoft looking at this.

Bonzer wrote:
As I stated in #3, yes I rebooted both nodes AFTER boot.ini settings were in
place.

"Geoff N. Hiten" wrote:


Doh. You did write that.

I think Jeffrey Williams may be on to something.

The quick and dirty way to check AWE usage is to look at PF usage on the
task manager. AWE maps as Page File.

The correct way is to use perfmon counters.

The wrong way is to use task manager memory usage on the processes page.
That counter cannot see AWE memory usage.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP


"Bonzer" <Bonzer (AT) discussions (DOT) microsoft.com> wrote in message
news:4EF86F58-CE5F-45CB-96F9-FD29D8CA0143 (AT) microsoft (DOT) com...

Yes, what I meant in #1

"Geoff N. Hiten" wrote:


Did you grant the service account "Lock pages in Memory" rights?

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP


"Bonzer" <Bonzer (AT) discussions (DOT) microsoft.com> wrote in message
news:94454B49-178A-4C9C-AB63-D91AAE1A13E5 (AT) microsoft (DOT) com...

Greetings,

I have a SQL2005 32-bit Std A/P cluster that will not use AWE memory
beyond
3GB. The server is running on Server 2003 r2 Enterprise edition, again
32-bit.

1. Added the domain service account to enable 'lock pages in memory'
2. Turned on AWE enabled in memory options
3. Edited the boot.ini with adding both /3GB and /PAE switches,
rebooted
both nodes.

My config value for awe_enabled is 1 and running value is 0 in
sp_configure.

Did I miss something at the OS level? The cluster is running on 2 Dell
blade
servers with 2 dual-cores and 8 GB of ram in each.

I have read and followed:

http://msdn2.microsoft.com/en-us/library/ms190673.aspx

http://msdn2.microsoft.com/en-us/library/ms175581.aspx

But still cant get this thing to use AWE memory, any thoughts much
appreciated.

Reply With Quote
Reply
Page 12 of 12 « First < 2 3 4 5 6 7 8 9 10 11 12

« Previous Thread | Next Thread »



Thread Tools
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.


Contact Us - dbTalk Databases Forums - Archive - Top