AWE in Windows is beyond the 4GB limit, in the 32bit world each 32bit
application only gets 2GB of Virtual Address Space. I believe you do
need to enable AWE in SQL Server 32bit to allow it to address past the
2GB VAS which would only be used for data caching. This of course does
not apply to x64 or Itanuim editions.

Group policy is the correct place for the lock pages in memory which
should be used for AWE and 64bit systems.

Now if the OS is 32bit don't forget to include the /3GB which will limit
the OS to 1GB in memory that way you can address 3GB of VAS for SQL
Server.

Rich Baumet

-----Original Message-----
From: Davis Ralph
[mailto:mssqldba-ezmlmshield-x29443527.[Email address protected]
Sent: Friday, December 28, 2007 7:04 AM
To: LazyDBA Discussion
Subject: RE: Lock Pages in Memory

Don,

First, AWE won't activate on a server with only 4gb of ram. It
is used for extended RAM above 4gb(up to 16gb on a 32 bit system). If
this server is 64 bit it isn't needed at all.

To alleviate the error message go to the local policies and add
the SQL service account to the 'lock pages in memory' policy.

Thanks,
Ralph W. Davis
*********************************************************
*** CORPORATE DBA group - Houston ***
*********************************************************

-----Original Message-----
From: Kolenda Don
[mailto:mssqldba-ezmlmshield-x58878350.[Email address protected]
Sent: Friday, December 28, 2007 9:01 AM
To: LazyDBA Discussion
Subject: Lock Pages in Memory

Hi, all! I'm attempting to enable AWE memory allocation on one of our
servers. It has 4 gb of RAM, using 4 dual-core processors. My
understanding is that I need to enable AWE memory to take advantage of
all available memory. Is this true?

1.) Here's the script SQL Server produced when I attempted to turn on
AWE:

EXEC sys.sp_configure N'show advanced options', N'1'
RECONFIGURE WITH OVERRIDE
GO
EXEC sys.sp_configure N'awe enabled', N'1'
GO
RECONFIGURE WITH OVERRIDE
GO
EXEC sys.sp_configure N'show advanced options', N'0'
RECONFIGURE WITH OVERRIDE
GO

2.) This produces the same error message for each statement:

Msg 5845, Level 16, State 1, Line 1
Address Windowing Extensions (AWE) requires the 'lock pages in
memory' privilege which is not currently present in the access token of
the process.

Thanks for any suggestions, y'all.


--Don Kolenda




---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
****************************************************************
Confidentiality Note: The information contained in this
message, and any attachments, may contain confidential
and/or privileged material. It is intended solely for the
person(s) or entity to which it is addressed. Any review,
retransmission, dissemination, or taking of any action in
reliance upon this information by persons or entities other
than the intended recipient(s) is prohibited. If you received
this in error, please contact the sender and delete the
material from any computer.
****************************************************************


---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
The information contained in this electronic message is for the exclusive and confidential use of the addressee. Any other distribution, use, reproduction or alteration of the information contained in this electronic message, by the addressee or by any other recipient, without the prior written consent of the sender is strictly prohibited. If you have received this electronic message in error, please notify the sender.


MS Sql Server LazyDBA home page