We are using both 2005 X64 bit Standard edition as well as 1 X64 bit
Enterprise edition. Both have 8 GB of physical RAM.

In the Enterprise edition, I grant the SQL Service account 'Lock Pages in
Memory' and set the Min Memory amount to 5 GB and Max to 6 GB. Looking in the
results of DBCC MemoryStatus, I can see that AWE is set to 1 (On) and once
the mem usage gets past 5 it never drops below the min memory setting.

In the Standard X64 edition, I do exactly the same, reboot, but AWE in DBCC
Memory Status is still 0. Memory goes above the 5 GB mark but is released to
sometimes below 100 MB. Then performance seems to slow down when it has to
reallocate this memory.

Would anyone know why the behavior is different or have any additional
recommendations on what else to check. Do I explicitly have to set AWE on in
x64 Standard. I was under the impression I didn't have to.

Thanks

What OS is being used on both machines?

--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous


"DSeifried" <dseifried@discussions.microsoft.com> wrote in message
news:43F54DFF-3D2B-4CD8-8785-D4AA8882E176@microsoft.com...
> We are using both 2005 X64 bit Standard edition as well as 1 X64 bit
> Enterprise edition. Both have 8 GB of physical RAM.
>
> In the Enterprise edition, I grant the SQL Service account 'Lock Pages in
> Memory' and set the Min Memory amount to 5 GB and Max to 6 GB. Looking in
> the
> results of DBCC MemoryStatus, I can see that AWE is set to 1 (On) and once
> the mem usage gets past 5 it never drops below the min memory setting.
>
> In the Standard X64 edition, I do exactly the same, reboot, but AWE in
> DBCC
> Memory Status is still 0. Memory goes above the 5 GB mark but is released
> to
> sometimes below 100 MB. Then performance seems to slow down when it has to
> reallocate this memory.
>
> Would anyone know why the behavior is different or have any additional
> recommendations on what else to check. Do I explicitly have to set AWE on
> in
> x64 Standard. I was under the impression I didn't have to.
>
> Thanks

For SQL 2005 Enterprise, it is Windows 2003 x64 Enterprise. On the Standard,
it is Windows 2003 x64 Standard. Thanks

"Arnie Rowland" wrote:

> What OS is being used on both machines?
>
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
>
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
>
> "DSeifried" <dseifried@discussions.microsoft.com> wrote in message
> news:43F54DFF-3D2B-4CD8-8785-D4AA8882E176@microsoft.com...
> > We are using both 2005 X64 bit Standard edition as well as 1 X64 bit
> > Enterprise edition. Both have 8 GB of physical RAM.
> >
> > In the Enterprise edition, I grant the SQL Service account 'Lock Pages in
> > Memory' and set the Min Memory amount to 5 GB and Max to 6 GB. Looking in
> > the
> > results of DBCC MemoryStatus, I can see that AWE is set to 1 (On) and once
> > the mem usage gets past 5 it never drops below the min memory setting.
> >
> > In the Standard X64 edition, I do exactly the same, reboot, but AWE in
> > DBCC
> > Memory Status is still 0. Memory goes above the 5 GB mark but is released
> > to
> > sometimes below 100 MB. Then performance seems to slow down when it has to
> > reallocate this memory.
> >
> > Would anyone know why the behavior is different or have any additional
> > recommendations on what else to check. Do I explicitly have to set AWE on
> > in
> > x64 Standard. I was under the impression I didn't have to.
> >
> > Thanks
>
>
>