AWE Memory

I am having a problem with SQL using the memory that should be available to it.
I have the following configuration:
Hardware:
CPU: 4 XEON 2.0 GHZ (with HT) - acts like 8
MEMORY: 8 GB RAM
OS: Windows 2003 Advanced Server (PAE is enabled in boot.ini)
SQL: SQL 2000 Enterprise
AWE is enabled
The user account for SQL has Lock Pages in Memory rights
My issue:
I have review the related threads on this site and compared the recommended
settings to my system. I have not found any differences. However the size of
the SQL working memory set will not increase beyond 1.7 GB.
I found a reference on MSDN that stated that when AWE is enabled an entry
"Address Windowing Extension Enabled" is added to the SQL Error Log. I find
no such entry in my log.
I seems as though AWE is not actually running even though all my setting
seem to be ok.
What have I missed?
Atvar
Atvar,
You also have to set the /3GB switch in boot.ini for SQL Server EE to use
the extra 1GB below the 4GB boundary. Even then it will report something
like 2.7GB used.
See KB 274750, "How to configure memory for more than 2 GB in SQL Server"
http://support.microsoft.com/default...b;en-us;274750
Hope this helps,
Ron
Ron Talmage
SQL Server MVP
"Atvar" <Atvar@.discussions.microsoft.com> wrote in message
news:741D40E0-A2C4-4529-9F64-56041A96C704@.microsoft.com...
> I am having a problem with SQL using the memory that should be available
to it.
> I have the following configuration:
> Hardware:
> CPU: 4 XEON 2.0 GHZ (with HT) - acts like 8
> MEMORY: 8 GB RAM
> OS: Windows 2003 Advanced Server (PAE is enabled in boot.ini)
> SQL: SQL 2000 Enterprise
> AWE is enabled
> The user account for SQL has Lock Pages in Memory rights
> My issue:
> I have review the related threads on this site and compared the
recommended
> settings to my system. I have not found any differences. However the size
of
> the SQL working memory set will not increase beyond 1.7 GB.
> I found a reference on MSDN that stated that when AWE is enabled an entry
> "Address Windowing Extension Enabled" is added to the SQL Error Log. I
find
> no such entry in my log.
> I seems as though AWE is not actually running even though all my setting
> seem to be ok.
> What have I missed?
> --
> Atvar
|||I thought the /3GB switch was not required and was just an option. Is this
not correct?
"Ron Talmage" wrote:

> Atvar,
> You also have to set the /3GB switch in boot.ini for SQL Server EE to use
> the extra 1GB below the 4GB boundary. Even then it will report something
> like 2.7GB used.
> See KB 274750, "How to configure memory for more than 2 GB in SQL Server"
> http://support.microsoft.com/default...b;en-us;274750
> Hope this helps,
> Ron
> --
> Ron Talmage
> SQL Server MVP
> "Atvar" <Atvar@.discussions.microsoft.com> wrote in message
> news:741D40E0-A2C4-4529-9F64-56041A96C704@.microsoft.com...
> to it.
> recommended
> of
> find
>
>
|||It is not required but a good idea in this case. It is not the reason you
are seeing what you say though. I would go back and start from scratch and
ensure you really have Enterprise SQL, WIn2003 Advanced, PAE and AWE turned
on and lock pages in memory for the right account. Verify each, don't just
assume.
Andrew J. Kelly SQL MVP
"Atvar" <Atvar@.discussions.microsoft.com> wrote in message
news:97FEA326-585E-460E-AE8D-6910CB4E9345@.microsoft.com...[vbcol=seagreen]
>I thought the /3GB switch was not required and was just an option. Is this
> not correct?
>
> "Ron Talmage" wrote:
|||Thanks for the response.
I did review things as you suggested. The server is running WIn2003
Enterprise (not called advanded in 2003) and the PAE and AWE are set.
However it turn out that the SQL is standard and not Enterprise. This site
uses several SQL servers and the install was done by their IT department.
This server was specified for SQL Enterprise and the license was purchased.
It appears that the wrong license was installed by the IT department. I
think this is my issue as I understand that SQL standard is limited to 2 GB
of memory.
"Andrew J. Kelly" wrote:

> It is not required but a good idea in this case. It is not the reason you
> are seeing what you say though. I would go back and start from scratch and
> ensure you really have Enterprise SQL, WIn2003 Advanced, PAE and AWE turned
> on and lock pages in memory for the right account. Verify each, don't just
> assume.
> --
> Andrew J. Kelly SQL MVP
>
> "Atvar" <Atvar@.discussions.microsoft.com> wrote in message
> news:97FEA326-585E-460E-AE8D-6910CB4E9345@.microsoft.com...
>
>
|||Yes that is it. Standard SQL will only use 2GB regardless of how much the
server has.
Andrew J. Kelly SQL MVP
"Atvar" <Atvar@.discussions.microsoft.com> wrote in message
news:433230CD-B250-4CB0-AEAE-9ED0A3F954C8@.microsoft.com...[vbcol=seagreen]
> Thanks for the response.
> I did review things as you suggested. The server is running WIn2003
> Enterprise (not called advanded in 2003) and the PAE and AWE are set.
> However it turn out that the SQL is standard and not Enterprise. This
> site
> uses several SQL servers and the install was done by their IT department.
> This server was specified for SQL Enterprise and the license was
> purchased.
> It appears that the wrong license was installed by the IT department. I
> think this is my issue as I understand that SQL standard is limited to 2
> GB
> of memory.
>
> "Andrew J. Kelly" wrote: