SQL 2000 only addressing 8 GB of avail 16 GB memory...why?

Question

SQL 2000 only addressing 8 GB of avail 16 GB memory...why?

Miiiik

Valued Member

Points: 53
More actions
August 15, 2006 at 12:56 pm

#191945

I have a Windows 2003 Enterprise Server with SQL 2000 SP4.
/PAE is set in the boot.ini.
Awe is set in SQL. It has been enabled as verifed in the startup log.
But SQL only sees 8 GB of the 16 GB. I fixed the memory that SQL uses to 15GB. Should it grab the 15 GB? Why is it only grabbing 8GB?

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Jeff Moden SSC Guru Points: 1004406 More actions · Answer 1

Are you using the ENTERPRISE edition of SQL Server? If not, you must be using the STANDARD edition and that would be the reason why...

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Daniel Kast SSC Rookie Points: 42 More actions · Answer 2

Maybe you're having the following issue:

KB899761: Not all memory is available when AWE is enabled on a computer that is running a 32-bit version of SQL Server 2000 SP4

http://support.microsoft.com/kb/899761/en-us

I recommend to install the "Cumulative Hotfix for SQL Server 2000 Service Pack 4 - Build 2187 for x86 and x64 Based Systems" instead, as it contains other fixes as well

http://www.microsoft.com/downloads/details.aspx?FamilyID=9c9ab140-bdee-44df-b7a3-e6849297754a&DisplayLang=en

Jeff Moden SSC Guru Points: 1004406 More actions · Answer 3

Don't ya just love Microsoft? Fixes for their fixes!! Thanks for the tip, Daniel and welcome to SQLServerCentral.com.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)