awe on sql 2005 on win 2003

[timscronin]

I have a win 2003 box running sql 2005 enterprise edition. I have the sql server set to use the 16 gig it has and have awe configured. However I have queries which tell me I have hit memory limit. I have this in the boot.ini file

[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003, Enterprise" /noexecute=optout /fastdetect

is this incorrect

 

[ptheriault]

is this a 32 or 64bit install?
If it is 32 bit you need to enable AWE if it is 64 bit you don't need it.

- Paul
- Database performance looks fine, it must be the Network!

 

[mrdenny]

You need to tell Windows to use the /3GB and /PAE switches in the boot.ini. That's in addition to having AWE enabled.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[timscronin]

I now have the following for my boot.ini
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003, Enterprise" /fastdetect /PAE /NoExecute=OptIn


This is the same I have for a sql 2000 server with 16 gig and it is running with the 16 gig being utilized. Is there a way with a dbcc command I can see if sql 2005 is using the 15 gig I have it set to?

 

[mrdenny]

You can use Perfmon to see how much memory SQL is using. Check the "SQL Server: Memory Manager: Total Server Memory (KB)" counter.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[timscronin]

I show only 2568448 bytes 2 gig. the machine has 16 gig physical. When I run sp_configure my memory shows
12288 meg as configured.

 

[mrdenny]

Try adding the /3GB switch to the boot.ini and rebooting.

You did reboot after adding the /PAE switch correct?

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[timscronin]

Yes, did reboot. Where does the /3GB go on that line?

 

[mrdenny]

You can put it at the end.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[timscronin]

boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003, Enterprise" /fastdetect /PAE /NoExecute=OptIn /3GB

 

[mrdenny]

Try changing the timeout from 0 to 30, and manually selecting the correct line from the list. You "MAY" need to edit the default line as well.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[timscronin]

Thanks, so the /3GB where it is at is fine? I have looked forever at several MS articles, but there seems no clear reference to the /3GB switch

 

[timscronin]

Put the 3GB in, total memory unchanged, calling MS in the morning

 

[micha123]

Have the same problem. How did you fix it?

Thanks...

"A long life is when each day is full and every hour wide!"
(A Jewish Mentor)
M.

 

[timscronin]

Rebooted, the last boot.ini file was right and I made sure awe was set on and the memory correct. I now have 15 gig of memory. When you run permon/sql memory, what is your target server memory showing?

 

[micha123]

The target memory is 3913259.

I am not sure if the SAs rebooted the server. They were suppose to but it might be the problem...

I guess I will be back if they did...

"A long life is when each day is full and every hour wide!"
(A Jewish Mentor)
M.

 

[timscronin]

In converting that it's only 3.7 gig