How to utilize 4GB of memory in SQL Server

Hello,
I have SQL 2000 developer edition installed on a windows 2003 server
with 4GB. I cant seem to make the server use more than 2.7GB of
memory.
I have the /3GB in the boot.ini file. But what other settings I need
to do windows server and SQL in order to make it start using more RAM.
Thanks,
Hello,
Go to SQL Server Query Anakyzer and execute
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
After this, make the mameory fixed using below commands. The below command
will fix 3250 MB to sql server. You can decide based onr requirement.
After the chnage stp and and start sql server service
sp_configure 'min server memory', 3250
RECONFIGURE
GO
sp_configure 'max server memory', 3250
RECONFIGURE
GOtake a look into the URL:-
http://msdn2.microsoft.com/en-US/library/ms190673.aspx
Thanks
Hari
<omarfk@.gmail.com> wrote in message
news:1170164738.041860.159930@.k78g2000cwa.googlegr oups.com...
> Hello,
> I have SQL 2000 developer edition installed on a windows 2003 server
> with 4GB. I cant seem to make the server use more than 2.7GB of
> memory.
> I have the /3GB in the boot.ini file. But what other settings I need
> to do windows server and SQL in order to make it start using more RAM.
> Thanks,
>
|||Thanks for the replies.
Unfortunatley, they just add to my earlier confusion I got when I did
my initial research.
Everybody immediatley recommends turning AWE on, but I have found a
lot of text that says:
"' If there is 4GB or less of physical memory in the box then SQL
Server ignores the 'AWE enabled' setting."
In this article: http://sqlnerd.blogspot.com/2006/07/memory-use-in-
sql-server.html
So for 4GB, do we turn AWE or not ?
Also from a table in the above article:
RAM/3GB/PAE'awe enabled''max server memory'
0-3 Not necessary
>3-4* Not necessary
>4-12***(Physical RAM) - (RAM needed for other applications & OS)
>12 **(Physical RAM) - (RAM needed for other applications & OS)
It seems for people who have 4GB, its not much different than having
3GB.
Appreciate your input!
On Jan 30, 4:12 pm, <@.> wrote:
> Memory Use in SQL Serverhttp://sqlnerd.blogspot.com/2006/07/memory-use-in-sql-server.html
> ssbhttp://sqlserverbuilds.blogspot.com/
|||<omarfk@.gmail.com> wrote in message
news:1170170428.399556.253070@.a75g2000cwd.googlegr oups.com...
> Thanks for the replies.
> Unfortunatley, they just add to my earlier confusion I got when I did
> my initial research.
> Everybody immediatley recommends turning AWE on, but I have found a
> lot of text that says:
> "' If there is 4GB or less of physical memory in the box then SQL
> Server ignores the 'AWE enabled' setting."
> In this article: http://sqlnerd.blogspot.com/2006/07/memory-use-in-
> sql-server.html
>
> So for 4GB, do we turn AWE or not ?
>
No. With the /3GB switch SQL Server can use 3GB of memory, leaving 1GB for
the OS kernel and other processes. Only for machines with more than 4GB are
you likely to have significant unused memory without AWE.
Performance-wise, AWE is a mixed bag. So for any server, I would not turn
on AWE unless I could demonstrate that my workload benefited from the
additional memory.
David
|||On Tue, 30 Jan 2007 10:07:48 -0600, "David Browne" <davidbaxterbrowne
no potted meat@.hotmail.com> wrote:

>Performance-wise, AWE is a mixed bag.
Could you put any numbers on that?
My current shop has a number of exactly 4gb servers, we are definitely
getting hash bails and sort warnings, but I'm wondering what the net
benefit is of moving up to ... whatever more the servers will support.
Server2003 (32 bit) and SQL2000, upgrading this year to SQLServer
2005.
Once upon a time I was sharp on hardware issues, but recent years the
ops group and the facilities are so far removed from the dev group,
it's hard to keep up!
Thanks.
Josh