Hi.. I'm trying to set up AWE in a Server with 8 GB of RAM, Windows 2003
Enterprise and SQL 2005 Standard

my Boot.ini is like this:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows Server 2003, Enterprise"
/noexecute=optout /fastdetect /PAE

I've set up the permission for the user executing SQL Server with permissons
in group policy to alocatte pages.. And then I've set up AWE to on, minimum
memory to 4 GB and maximum to 6 GB

Then I rebooted the server..

Now, I can see AWE value is set to 1, but value_in_use is set to 0.. and SQL
Server process is not using more than 2GB of memory.. so I guess AWE is not
enabled..

Any ideas what can be wrong??

Don't you also need /3GB in the line in boot.ini ? I have similarly
configured servers but unfortunately I am on a train and don't have direct
access to them at the moment to verify.

A




On 5/22/08 12:22 PM, in article
D1C102E8-2239-4C0B-A9E7-05A28813BA36@microsoft.com, "averied"
<averied@discussions.microsoft.com> wrote:

> Hi.. I'm trying to set up AWE in a Server with 8 GB of RAM, Windows 2003
> Enterprise and SQL 2005 Standard
>
> my Boot.ini is like this:
> [boot loader]
> timeout=30
> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows Server 2003, Enterprise"
> /noexecute=optout /fastdetect /PAE
>
> I've set up the permission for the user executing SQL Server with permissons
> in group policy to alocatte pages.. And then I've set up AWE to on, minimum
> memory to 4 GB and maximum to 6 GB
>
> Then I rebooted the server..
>
> Now, I can see AWE value is set to 1, but value_in_use is set to 0.. and SQL
> Server process is not using more than 2GB of memory.. so I guess AWE is not
> enabled..
>
> Any ideas what can be wrong??
>
>
>

Exactly how are you determining how much memory SQL Server is using? Task
manager isn't the tool to use here. Try dbcc memorystatus or the
performance monitor memory counters.

--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net


"averied" <averied@discussions.microsoft.com> wrote in message
news1C102E8-2239-4C0B-A9E7-05A28813BA36@microsoft.com...
> Hi.. I'm trying to set up AWE in a Server with 8 GB of RAM, Windows 2003
> Enterprise and SQL 2005 Standard
>
> my Boot.ini is like this:
> [boot loader]
> timeout=30
> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows Server 2003,
> Enterprise"
> /noexecute=optout /fastdetect /PAE
>
> I've set up the permission for the user executing SQL Server with
> permissons
> in group policy to alocatte pages.. And then I've set up AWE to on,
> minimum
> memory to 4 GB and maximum to 6 GB
>
> Then I rebooted the server..
>
> Now, I can see AWE value is set to 1, but value_in_use is set to 0.. and
> SQL
> Server process is not using more than 2GB of memory.. so I guess AWE is
> not
> enabled..
>
> Any ideas what can be wrong??
>
>
>

You don't need or have to use /3GB.

Linchi

"Aaron Bertrand [SQL Server MVP]" wrote:

> Don't you also need /3GB in the line in boot.ini ? I have similarly
> configured servers but unfortunately I am on a train and don't have direct
> access to them at the moment to verify.
>
> A
>
>
>
>
> On 5/22/08 12:22 PM, in article
> D1C102E8-2239-4C0B-A9E7-05A28813BA36@microsoft.com, "averied"
> <averied@discussions.microsoft.com> wrote:
>
> > Hi.. I'm trying to set up AWE in a Server with 8 GB of RAM, Windows 2003
> > Enterprise and SQL 2005 Standard
> >
> > my Boot.ini is like this:
> > [boot loader]
> > timeout=30
> > default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> > [operating systems]
> > multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows Server 2003, Enterprise"
> > /noexecute=optout /fastdetect /PAE
> >
> > I've set up the permission for the user executing SQL Server with permissons
> > in group policy to alocatte pages.. And then I've set up AWE to on, minimum
> > memory to 4 GB and maximum to 6 GB
> >
> > Then I rebooted the server..
> >
> > Now, I can see AWE value is set to 1, but value_in_use is set to 0.. and SQL
> > Server process is not using more than 2GB of memory.. so I guess AWE is not
> > enabled..
> >
> > Any ideas what can be wrong??
> >
> >
> >
>
>

> value_in_use is set to 0

Where did you read that value? Is it under the run_value column from
sp_configure?

Linchi

"averied" wrote:

> Hi.. I'm trying to set up AWE in a Server with 8 GB of RAM, Windows 2003
> Enterprise and SQL 2005 Standard
>
> my Boot.ini is like this:
> [boot loader]
> timeout=30
> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows Server 2003, Enterprise"
> /noexecute=optout /fastdetect /PAE
>
> I've set up the permission for the user executing SQL Server with permissons
> in group policy to alocatte pages.. And then I've set up AWE to on, minimum
> memory to 4 GB and maximum to 6 GB
>
> Then I rebooted the server..
>
> Now, I can see AWE value is set to 1, but value_in_use is set to 0.. and SQL
> Server process is not using more than 2GB of memory.. so I guess AWE is not
> enabled..
>
> Any ideas what can be wrong??
>
>
>

Hi.. sorry for the delay and thanks for the answers...

Indeed, the run_value is the one I get when I executed:

exec sp_configure 'awe enabled'

Config_value is set to 1, but run_value is 0

Also if I run:

select name, value, minimum, maximum, value_in_use
from sys.configurations
where name = N'awe enabled'

I get value 1 but value_in_use 0

Very strange behaviour here..




"Linchi Shea" wrote:

> > value_in_use is set to 0
>
> Where did you read that value? Is it under the run_value column from
> sp_configure?
>
> Linchi
>
> "averied" wrote:
>
> > Hi.. I'm trying to set up AWE in a Server with 8 GB of RAM, Windows 2003
> > Enterprise and SQL 2005 Standard
> >
> > my Boot.ini is like this:
> > [boot loader]
> > timeout=30
> > default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> > [operating systems]
> > multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows Server 2003, Enterprise"
> > /noexecute=optout /fastdetect /PAE
> >
> > I've set up the permission for the user executing SQL Server with permissons
> > in group policy to alocatte pages.. And then I've set up AWE to on, minimum
> > memory to 4 GB and maximum to 6 GB
> >
> > Then I rebooted the server..
> >
> > Now, I can see AWE value is set to 1, but value_in_use is set to 0.. and SQL
> > Server process is not using more than 2GB of memory.. so I guess AWE is not
> > enabled..
> >
> > Any ideas what can be wrong??
> >
> >
> >

Did you reboot after setting AWE on?

--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net


"averied" <averied@discussions.microsoft.com> wrote in message
news:86D2B97D-4579-4F3C-B981-C5AD3E480E2A@microsoft.com...
> Hi.. sorry for the delay and thanks for the answers...
>
> Indeed, the run_value is the one I get when I executed:
>
> exec sp_configure 'awe enabled'
>
> Config_value is set to 1, but run_value is 0
>
> Also if I run:
>
> select name, value, minimum, maximum, value_in_use
> from sys.configurations
> where name = N'awe enabled'
>
> I get value 1 but value_in_use 0
>
> Very strange behaviour here..
>
>
>
>
> "Linchi Shea" wrote:
>
>> > value_in_use is set to 0
>>
>> Where did you read that value? Is it under the run_value column from
>> sp_configure?
>>
>> Linchi
>>
>> "averied" wrote:
>>
>> > Hi.. I'm trying to set up AWE in a Server with 8 GB of RAM, Windows
>> > 2003
>> > Enterprise and SQL 2005 Standard
>> >
>> > my Boot.ini is like this:
>> > [boot loader]
>> > timeout=30
>> > default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
>> > [operating systems]
>> > multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows Server 2003,
>> > Enterprise"
>> > /noexecute=optout /fastdetect /PAE
>> >
>> > I've set up the permission for the user executing SQL Server with
>> > permissons
>> > in group policy to alocatte pages.. And then I've set up AWE to on,
>> > minimum
>> > memory to 4 GB and maximum to 6 GB
>> >
>> > Then I rebooted the server..
>> >
>> > Now, I can see AWE value is set to 1, but value_in_use is set to 0..
>> > and SQL
>> > Server process is not using more than 2GB of memory.. so I guess AWE is
>> > not
>> > enabled..
>> >
>> > Any ideas what can be wrong??
>> >
>> >
>> >

averied wrote:


>>> Any ideas what can be wrong??

Does the service account have "Lock pages in memory" privilege?

> You don't need or have to use /3GB.

Can you envision any other reason why SQL Server is not able to run AWE?
I'm not clear on whether or not SQL Server is actually *using* the right
amount of memory in this case, but that run_value should be 1, no? Not that
this is empirical evidence, but I have /3GB /PAE on one server with 16GB of
RAM, where I've allocated 14.5GB to SQL Server, and the run_value is 1 (and
SQL Server is definitely using the memory).

This may be a strange problem, as I have never seen an sp_configure setting
like this fail to take. Maybe the setting was applied after the reboot as
opposed to before the reboot.

Anyway maybe we could find out what is actually in use at the moment.
avaried, can you show us the results of:

SELECT counter_name, cntr_value
FROM sys.dm_os_performance_counters
WHERE RTRIM(counter_name) LIKE 'T%Server Memory (KB)';

SELECT [type], awe_allocated_kb, shared_memory_reserved_kb,
shared_memory_committed_kb,
virtual_memory_reserved_kb, virtual_memory_committed_kb
FROM sys.dm_os_memory_clerks
WHERE awe_allocated_kb + shared_memory_reserved_kb +
shared_memory_committed_kb +
virtual_memory_reserved_kb + virtual_memory_committed_kb > 0;

Also despite Linchi's assurance that you don't need it, you can try adding
/3GB to the boot.ini and rebooting, and comparing the results.

Yes.. rebooted the server and set the permissons.. that's why I dont
understand what can be wrong..

"Ed Enstrom" wrote:

> averied wrote:
>
>
> >>> Any ideas what can be wrong??
>
> Does the service account have "Lock pages in memory" privilege?
>

Hi again..

sorry guys.. I just rebooted again and suddenly AWE got enabled.. I
couldn't reboot before coz the server is in a production enviroment.. Now
let's see tomorrow monday if everything goes all right...

I can see in taskmgr that SQLserver is taking very little memory, altough I
set the minimum memory to 4 GB.. Is this a normal behaviour??

I get this counter values..

Target Server Memory (This is the maximum memory I set for SQL Server)(KB)

6291456
Total Server Memory (KB)
111872

"averied" wrote:

> Yes.. rebooted the server and set the permissons.. that's why I dont
> understand what can be wrong..
>
> "Ed Enstrom" wrote:
>
> > averied wrote:
> >
> >
> > >>> Any ideas what can be wrong??
> >
> > Does the service account have "Lock pages in memory" privilege?
> >

Hi
Yes it is normal as Task Manager does not show memory used by SQL Server
with AWE enabled and defined.




"averied" <averied@discussions.microsoft.com> wrote in message
news:4472B708-D128-420B-8CF0-D41653356157@microsoft.com...
> Hi again..
>
> sorry guys.. I just rebooted again and suddenly AWE got enabled.. I
> couldn't reboot before coz the server is in a production enviroment.. Now
> let's see tomorrow monday if everything goes all right...
>
> I can see in taskmgr that SQLserver is taking very little memory, altough
> I
> set the minimum memory to 4 GB.. Is this a normal behaviour??
>
> I get this counter values..
>
> Target Server Memory (This is the maximum memory I set for SQL
> Server)(KB)
>
> 6291456
> Total Server Memory (KB)
> 111872
>
> "averied" wrote:
>
>> Yes.. rebooted the server and set the permissons.. that's why I dont
>> understand what can be wrong..
>>
>> "Ed Enstrom" wrote:
>>
>> > averied wrote:
>> >
>> >
>> > >>> Any ideas what can be wrong??
>> >
>> > Does the service account have "Lock pages in memory" privilege?
>> >