Solved

SQL Server Windows 2003 AWE PAE 3GB

Posted on 2004-09-19
5
1,617 Views
Last Modified: 2012-05-05
I just upgraded the RAM in our SQL server from 2GB to 10GB and the SQL DB is only using 2.7GB of RAM.  I have read many places things like:

"AWE memory cannot be dynamically managed, like memory is normally managed in SQL Server. This means that SQL Server will automatically grab all the RAM it can when it starts (except for about 128MB, which is reserved for the operating system), but it will not release any of this RAM until SQL Server is turned off. "
http://www.sql-server-performance.com/awe_memory.asp

I set BOTH the /3GB and /PAE switch in my boot.ini file, and I enabled AWE in SQL server via the following commands:

SP_CONFIGURE 'show advanced options', 1
RECONFIGURE                              
GO

SP_CONFIGURE 'awe enabled', 1
RECONFIGURE
GO

SP_CONFIGURE 'max server memory', 9216
RECONFIGURE
GO

From what I had gathered I assumed the SQL server would use 9GB of RAM and leave 1GB for the system. I look in Perfmon->SQL Server:MemoryManager->Target Server Memory(KB) and it is saying roughly 2.7GB

What am I missing?
0
Comment
Question by:SpreadTheWord
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
5 Comments
 
LVL 43

Expert Comment

by:Eugene Z
ID: 12098195
What edition of Windows 2003 do you have?
And what sql server 2k edition?


please read the Maximum Capacity Specifications for sql server 2000
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_8dbn.asp

0
 

Author Comment

by:SpreadTheWord
ID: 12099104
SQL Server 2000 Ent. Ed.
Windows 2003 Ent Ed.

The 10 GB of RAM is seen by windows.
0
 

Author Comment

by:SpreadTheWord
ID: 12102617
BTW - the SQL server memory consumption climbed up to 2.7GB over time and then stuck there.
0
 
LVL 34

Accepted Solution

by:
arbert earned 500 total points
ID: 12109051
This is how SQL works (even with AWE).  Unless you put a minimum memory setting, SQL will grow to your maximum memory amount...
0
 

Author Comment

by:SpreadTheWord
ID: 12118265
arbert--

I am completely new to this stuff - so it seems normal for my memory usage to slowly climb to 2,792,540K exactly and then stay there?

-Sam
0

Featured Post

Webinar: Aligning, Automating, Winning

Join Dan Russo, Senior Manager of Operations Intelligence, for an in-depth discussion on how Dealertrack, leading provider of integrated digital solutions for the automotive industry, transformed their DevOps processes to increase collaboration and move with greater velocity.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In the first part of this tutorial we will cover the prerequisites for installing SQL Server vNext on Linux.
Recently we ran in to an issue while running some SQL jobs where we were trying to process the cubes.  We got an error saying failure stating 'NT SERVICE\SQLSERVERAGENT does not have access to Analysis Services. So this is a way to automate that wit…
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
Via a live example, show how to extract information from SQL Server on Database, Connection and Server properties

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question