AWE on 2003 x64 with SP4 and 8 gigs of memory.

I just bought a nice new server with EMT64 ( we have to buy Dell ). It has
8 gigs of memory. It is running Windows 2003 Std x64 edition and the OS
detects all of the 8 gigs.
I installed SQL 2000 SP4 Enterprise edition and applied SP4. I restored a
decent sized database of 60+ gigs to it. I wanted to see just how much memory
SQL could use for its buffers versus going off toe the SCSI drives.
I stared selecting all the data out of my database to move the data in
their. I top 3 gigs, but shortly after SQL seemed to stop using more memory.
I was guessing this was the limit.
At this point I thought, maybe I should turn on AWE. I then went and applied
the patch for SP4 that fixes the half memory utilization issue.
Turned it on and restarted the machine and SQL just to be safe. I have SQL
setup to use roughly 7+ gigs of memory and to reserve physical memory. I'm
not using dynamic allocation.
If I pull up taskmgr I see the process for SQL is only using around 190 megs
of memory, however, if I switch to the performance tab I see that I have
almost all the memory allocated.
After selecting a ton of data and doing some tests it is clear that way more
then 190 megs of 8k pages are in memory. Mostly from selecting all the rows
from a large table, and then watching the disk io on future requests which is
virtually zero.
I select * from master.dbo.sysperfinfo, but I can't seem to be able to find
the number that would indicate that I have gigs of pages in the buffer.
Is there a know issue with SQL server or TaskMgr on the x64 edition where it
would report the memory usage wrong like this?
Lastly we have Software Assurance for this product, does that give me free
access to support to ask this question?
thanks,
et
"et" <et@.discussions.microsoft.com> wrote in message
news:44C118C0-DF0A-4F0E-9752-BC198B40B425@.microsoft.com...
>I just bought a nice new server with EMT64 ( we have to buy Dell ). It
>has
> 8 gigs of memory. It is running Windows 2003 Std x64 edition and the OS
> detects all of the 8 gigs.
> I installed SQL 2000 SP4 Enterprise edition and applied SP4. I restored a
> decent sized database of 60+ gigs to it. I wanted to see just how much
> memory
> SQL could use for its buffers versus going off toe the SCSI drives.
> I stared selecting all the data out of my database to move the data in
> their. I top 3 gigs, but shortly after SQL seemed to stop using more
> memory.
> I was guessing this was the limit.
>
Yes. 4 gigs is the limit in this configuration (SQL 2000 EE 32bit on
Windows 2003 x64 edition).

> At this point I thought, maybe I should turn on AWE. I then went and
> applied
> the patch for SP4 that fixes the half memory utilization issue.
> Turned it on and restarted the machine and SQL just to be safe. I have SQL
> setup to use roughly 7+ gigs of memory and to reserve physical memory. I'm
> not using dynamic allocation.
> If I pull up taskmgr I see the process for SQL is only using around 190
> megs
> of memory, however, if I switch to the performance tab I see that I have
> almost all the memory allocated.
> After selecting a ton of data and doing some tests it is clear that way
> more
> then 190 megs of 8k pages are in memory. Mostly from selecting all the
> rows
> from a large table, and then watching the disk io on future requests which
> is
> virtually zero.
> I select * from master.dbo.sysperfinfo, but I can't seem to be able to
> find
> the number that would indicate that I have gigs of pages in the buffer.
> Is there a know issue with SQL server or TaskMgr on the x64 edition where
> it
> would report the memory usage wrong like this?
>
Not an x64 issue. AWE usage is not visible in Task Manager:
From BOL topic "Managing AWE Memory"
Use System Monitor (Performance Monitor in Microsoft Windows NT 4.0) to
retrieve information on SQL Server memory usage and available memory. Task
Manager does not provide accurate memory usage information for AWE.
Therefore, the memory quoted for sqlservr.exe is not correct. To obtain the
correct amount of SQL Server memory usage, you can use the Total Server
Memory (KB) performance counter, activated through System Monitor, or select
the memory usage from sysperfinfo. For more information, see Monitoring
Memory Usage.
http://msdn.microsoft.com/library/de...erver_1fnd.asp

> Lastly we have Software Assurance for this product, does that give me free
> access to support to ask this question?
>
The short answer is Yes, Software Assurance for server products includes
some free phone support, as well as free upgrades to new versions. The
number of incidents and hours of support vary by product and SKU, and total
amount of money spent. Also new stuff is included Software Assurance as of
March 2006. See generally:
http://www.microsoft.com/licensing/p...a/default.mspx .
David
|||When you call in for support, the tech router will tell you if your call is
free or not :-)
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:ONfOaFWGGHA.2680@.TK2MSFTNGP09.phx.gbl...
> "et" <et@.discussions.microsoft.com> wrote in message
> news:44C118C0-DF0A-4F0E-9752-BC198B40B425@.microsoft.com...
> Yes. 4 gigs is the limit in this configuration (SQL 2000 EE 32bit on
> Windows 2003 x64 edition).
>
> Not an x64 issue. AWE usage is not visible in Task Manager:
> From BOL topic "Managing AWE Memory"
> Use System Monitor (Performance Monitor in Microsoft Windows NT 4.0) to
> retrieve information on SQL Server memory usage and available memory. Task
> Manager does not provide accurate memory usage information for AWE.
> Therefore, the memory quoted for sqlservr.exe is not correct. To obtain
> the correct amount of SQL Server memory usage, you can use the Total
> Server Memory (KB) performance counter, activated through System Monitor,
> or select the memory usage from sysperfinfo. For more information, see
> Monitoring Memory Usage.
> http://msdn.microsoft.com/library/de...erver_1fnd.asp
>
> The short answer is Yes, Software Assurance for server products includes
> some free phone support, as well as free upgrades to new versions. The
> number of incidents and hours of support vary by product and SKU, and
> total amount of money spent. Also new stuff is included Software
> Assurance as of March 2006. See generally:
> http://www.microsoft.com/licensing/p...a/default.mspx .
>
> David
>
>
|||maybe i am beating dead horses but
if this is a brand new machine i do not understand why you did not install
sql 2005 64 bit ,,,,
regards
Michel Posseth [MCP]
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:ONfOaFWGGHA.2680@.TK2MSFTNGP09.phx.gbl...
> "et" <et@.discussions.microsoft.com> wrote in message
> news:44C118C0-DF0A-4F0E-9752-BC198B40B425@.microsoft.com...
> Yes. 4 gigs is the limit in this configuration (SQL 2000 EE 32bit on
> Windows 2003 x64 edition).
>
> Not an x64 issue. AWE usage is not visible in Task Manager:
> From BOL topic "Managing AWE Memory"
> Use System Monitor (Performance Monitor in Microsoft Windows NT 4.0) to
> retrieve information on SQL Server memory usage and available memory. Task
> Manager does not provide accurate memory usage information for AWE.
> Therefore, the memory quoted for sqlservr.exe is not correct. To obtain
> the correct amount of SQL Server memory usage, you can use the Total
> Server Memory (KB) performance counter, activated through System Monitor,
> or select the memory usage from sysperfinfo. For more information, see
> Monitoring Memory Usage.
> http://msdn.microsoft.com/library/de...erver_1fnd.asp
>
> The short answer is Yes, Software Assurance for server products includes
> some free phone support, as well as free upgrades to new versions. The
> number of incidents and hours of support vary by product and SKU, and
> total amount of money spent. Also new stuff is included Software
> Assurance as of March 2006. See generally:
> http://www.microsoft.com/licensing/p...a/default.mspx .
>
> David
>
>