Windows 2003 SP1 won"t let me set the lock pages in memory

Windows 2003 SP1 won"t let me set the lock pages in memory

am 30.11.2007 00:21:50 von Sanctus

Is there a way around this?

I have a SQL 2005 with 8 GB of memory that I want to set AWE on.
But the local security policy won't let me, it says:

This setting is not comaptiple with computers running Windows 2000
Service Pack 1 or earlier.
Apply group Policy objects containing this setting only to computers
running a later version of the operating system.

Why does it say Windows 2000 SP1 or earlier? I'm running on Windows
2003, sp1.

Re: Windows 2003 SP1 won"t let me set the lock pages in memory

am 30.11.2007 04:19:10 von Nick Chan

i think u dont need to set awe in win2k3.i also think that if u wanna
use more than 4gb ram, u need enterprise version of win2k3 and sql
On Nov 30, 7:21 am, Sanctus wrote:
> Is there a way around this?
>
> I have a SQL 2005 with 8 GB of memory that I want to set AWE on.
> But the local security policy won't let me, it says:
>
> This setting is not comaptiple with computers running Windows 2000
> Service Pack 1 or earlier.
> Apply group Policy objects containing this setting only to computers
> running a later version of the operating system.
>
> Why does it say Windows 2000 SP1 or earlier? I'm running on Windows
> 2003, sp1.

Re: Windows 2003 SP1 won"t let me set the lock pages in memory option...it says I need Sp2.

am 30.11.2007 23:22:40 von Erland Sommarskog

Sanctus (mchi55@hotmail.com) writes:
> Is there a way around this?
>
> I have a SQL 2005 with 8 GB of memory that I want to set AWE on.
> But the local security policy won't let me, it says:
>
> This setting is not comaptiple with computers running Windows 2000
> Service Pack 1 or earlier.
> Apply group Policy objects containing this setting only to computers
> running a later version of the operating system.
>
> Why does it say Windows 2000 SP1 or earlier? I'm running on Windows
> 2003, sp1.

Don't know what that means, but it seems that some version information
in Windows have been corrupted. I think you should ask in a Windows
forum.

--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downlo ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books .mspx