AWE on SQL 2005 and W 2003 Enterprise Server

I have 8 GB on a Windows 2003 Enterprise Server running SQL 2005. I have
added /PAE to the boot.ini file and changed the max memory on SQL to 6800
MB. I start the SQL Service with a separate account that has Lock Memory
privilege. How can I tell if I have set it up right. When I do a "dbcc
memorystatus" I am not sure what to look for. It seems that I am still only
using 1.7 GB of memory.
Thanks,
TomHello Tom,
It's a x86 system right? If so...
Connect to your Instance using SSMS and go to Server Properties. Go to
Memory from the left pane and click Running Values. Be sure AWE is still
selected. This will make you sure that AWE is being used by SQL Server.
You restarted your Server after adding PAE switch, right?
If you did not add 3GB switch, then your OS is still going to be using 2GB
of RAM. So you can not make your SQL Server use 7GB over 8GB of RAM.
If this stuff is OK and your server is SQL Server dedicated server (which
means there will not be running another application on that server and that
server serves only for queries against databases on SQL Server) then
everything should be fine.
Ekrem Önsoy
"tom" <tom@.pcreducator.com> wrote in message
news:%23tUja9WBIHA.4752@.TK2MSFTNGP04.phx.gbl...
>I have 8 GB on a Windows 2003 Enterprise Server running SQL 2005. I have
>added /PAE to the boot.ini file and changed the max memory on SQL to 6800
>MB. I start the SQL Service with a separate account that has Lock Memory
>privilege. How can I tell if I have set it up right. When I do a "dbcc
>memorystatus" I am not sure what to look for. It seems that I am still only
>using 1.7 GB of memory.
> Thanks,
> Tom
>|||Ekrem,
Thanks for your response.
Yes, it's 32-bit and I did reboot after adding the /PAE switch. It turns out
that after I did some more extensive testing, and watching the performance
monitor of "Total Server Memory" under "SQL Server: Memory Manager", I was
able to see the memory go higher than 1.7 GB.
Tom
"Ekrem Önsoy" <ekrem@.btegitim.com> wrote in message
news:909509D4-D31B-4ABD-9E38-980994F9C58F@.microsoft.com...
> Hello Tom,
>
> It's a x86 system right? If so...
> Connect to your Instance using SSMS and go to Server Properties. Go to
> Memory from the left pane and click Running Values. Be sure AWE is still
> selected. This will make you sure that AWE is being used by SQL Server.
> You restarted your Server after adding PAE switch, right?
> If you did not add 3GB switch, then your OS is still going to be using 2GB
> of RAM. So you can not make your SQL Server use 7GB over 8GB of RAM.
> If this stuff is OK and your server is SQL Server dedicated server (which
> means there will not be running another application on that server and
> that server serves only for queries against databases on SQL Server) then
> everything should be fine.
>
> --
> Ekrem Önsoy
>
> "tom" <tom@.pcreducator.com> wrote in message
> news:%23tUja9WBIHA.4752@.TK2MSFTNGP04.phx.gbl...
>>I have 8 GB on a Windows 2003 Enterprise Server running SQL 2005. I have
>>added /PAE to the boot.ini file and changed the max memory on SQL to 6800
>>MB. I start the SQL Service with a separate account that has Lock Memory
>>privilege. How can I tell if I have set it up right. When I do a "dbcc
>>memorystatus" I am not sure what to look for. It seems that I am still
>>only using 1.7 GB of memory.
>> Thanks,
>> Tom
>