AWE memory on SQL 2005 Standard

Is AWE enabled on SQL 2005 Standard? We currently have it setup using "locked pages in memory" for a domain account and haven't noticed any performance problems.

This article however states that only the SQL2005 Enterprise Edn supports "locked pages in memory". Can anyone confirm this?

http://support.microsoft.com/kb/918483

If I'm mistaken, how should the memory options be set for a server with 8gb ram running on SQL 2005 Standard which runs on Win2003 Enterprise? Should the min and max memory be set or left alone as default?

SQL 2005 does support AWE. However it does not support "locked pages in memory".

SQL 2005 should be set with AWE and the OS should have /3GB and /PAE in the boot.ini. This will allow Standard Edition to use all 8 Gigs of memory. Set the max memory to between 7 and 7.5 Gigs of memory.

|||

Thanks. Our current configuration has the switches /3GB and /PAE, but it wasn't clear on the "locked pages in memory". Do you know the benefit of having this feature? Also, what would you recommend our minimum memory to be set to?

AWE in SQL Cluster

I have a two node cluster with SQL Server 2005 that I am having difficulty
getting AWE to work. I have granted the "lock pages in memory" right to the
domain account that the SQL Server service is running under on both nodes
and run the following commands to setup the AWE memory.
sp_configure 'awe enabled', 1
go
reconfigure with override
go
sp_configure 'max server memory','6144'
go
reconfigure with override
go
I get the following error message when these statements complete:
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.
Don't grant the privilege to the account. Grant it to the domain group you
designated when you installed SQL.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:uREFgcPrHHA.4324@.TK2MSFTNGP04.phx.gbl...
>I have a two node cluster with SQL Server 2005 that I am having difficulty
>getting AWE to work. I have granted the "lock pages in memory" right to
>the domain account that the SQL Server service is running under on both
>nodes and run the following commands to setup the AWE memory.
> sp_configure 'awe enabled', 1
> go
> reconfigure with override
> go
> sp_configure 'max server memory','6144'
> go
> reconfigure with override
> go
> I get the following error message when these statements complete:
> 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.
>
>
>
|||We got the same error, we restarted SQL, went back in and looked - it is now
enabled ;) We are on SP2 of Windows and SQL 2005.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:uREFgcPrHHA.4324@.TK2MSFTNGP04.phx.gbl...
>I have a two node cluster with SQL Server 2005 that I am having difficulty
>getting AWE to work. I have granted the "lock pages in memory" right to
>the domain account that the SQL Server service is running under on both
>nodes and run the following commands to setup the AWE memory.
> sp_configure 'awe enabled', 1
> go
> reconfigure with override
> go
> sp_configure 'max server memory','6144'
> go
> reconfigure with override
> go
> I get the following error message when these statements complete:
> 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.
>
>
>
|||The Microsoft documentation said to add the security account but I did
actually add both the account and the security group before I got the error.
Do you think that I need to reboot to aleviate the error message?
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:eBNxIPQrHHA.1508@.TK2MSFTNGP05.phx.gbl...
> Don't grant the privilege to the account. Grant it to the domain group
> you designated when you installed SQL.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Cgal" <cgallelli@.newsgroups.nospam> wrote in message
> news:uREFgcPrHHA.4324@.TK2MSFTNGP04.phx.gbl...
>
|||A reboot probably won't hurt.
It does seem to fix a lot of things in the Microsoft world.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:OEtitcTrHHA.3248@.TK2MSFTNGP03.phx.gbl...
> The Microsoft documentation said to add the security account but I did
> actually add both the account and the security group before I got the
> error.
> Do you think that I need to reboot to aleviate the error message?
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:eBNxIPQrHHA.1508@.TK2MSFTNGP05.phx.gbl...
>
|||In order for new Windows level security permissions to be active (such as the
lock pages in memory right) the account must log out and back in. As this is
a service account, the services simply need to be restarted.
Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration /
Microsoft Office SharePoint Server 2007: Configuration)
MCITP (dbadmin, dbdev)
"Cgal" wrote:

> The Microsoft documentation said to add the security account but I did
> actually add both the account and the security group before I got the error.
> Do you think that I need to reboot to aleviate the error message?
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:eBNxIPQrHHA.1508@.TK2MSFTNGP05.phx.gbl...
>
>