Re: Set Working Set Size / AWE

From: Andrew J. Kelly (sqlmvpnoooospam_at_shadhawk.com)
Date: 05/09/04 

Date: Sun, 9 May 2004 14:31:20 -0500

OK but SQL Std can only access 2GB so dump the /3GB and absolutely remove
the SET Working set size. 

--
Andrew J. Kelly  SQL MVP
"James Hokes" <noemail@noway.com> wrote in message
news:uOKYRKeNEHA.740@TK2MSFTNGP12.phx.gbl...
> Andrew,
>
> Win2k3 Enterprise, which is what we're running, can address up to 32GB of
> RAM in its 32-bit version.
>
> James Hokes
>
> "Andrew J. Kelly" <sqlmvpnoooospam@shadhawk.com> wrote in message
> news:Oh2Oi3KNEHA.1340@TK2MSFTNGP12.phx.gbl...
> > James,
> >
> > SQL Server reserves approximately 256MB of memory on startup for what is
> > called the MemoryToLeave area.  The rest is left for the memory pool if
it
> > needs it.  So from task manager it may look like sql server is not using
> all
> > the ram.  You should really use the perfmon counters to see how sql
server
> > is using the ram.   Not sure where that number is coming from but you
> should
> > do a few things.  One is to remove the /3GB setting since it is useless
> > anyway with STD edition.  Does Win2K3 Server support 6GB?  If not then
> dump
> > the /PAE as well and use that other 2 GB elsewhere.  Next remove the SET
> > Working Set Size.
> >
> > --
> > Andrew J. Kelly  SQL MVP
> >
> >
> > "James Hokes" <nospam_nothanks_@nospamforme_nothanks.com> wrote in
message
> > news:eWevUAENEHA.892@TK2MSFTNGP09.phx.gbl...
> > > Andrew,
> > >
> > > It's Standard Edition, and yes, we're aware of the 2GB limit.
> > > That's one reason why we went with 2000MB memory setting, figuring
that
> > the
> > > full 2GB would be 2048MB.
> > >
> > > However, we're getting this weird message stating:
> > > "Could not set working set size to 843776".
> > >
> > > Any idea why this strange error message? And where could it be getting
a
> > > strange value like 843776? It's got us concerned that perhaps because
it
> > > couldn't "Set Working Set Size" that it's using some default value,
> > although
> > > it does appear to consume 1.7GB of memory eventually (according to
Task
> > > Manager, but it never reaches 2000MB like we told it to.)
> > >
> > > Thanks,
> > > James Hokes
> > >
> > > "Andrew J. Kelly" <sqlmvpnoooospam@shadhawk.com> wrote in message
> > > news:uptsa79MEHA.2644@TK2MSFTNGP11.phx.gbl...
> > > > James,
> > > >
> > > > What edition of SQL Server are you using?  If it's not Enterprise
then
> > you
> > > > can only use 2GB no matter what switches you set.
> > > >
> > > > --
> > > > Andrew J. Kelly  SQL MVP
> > > >
> > > >
> > > > "James Hokes" <nospam_nothanks_@nospamforme_nothanks.com> wrote in
> > message
> > > > news:eWhm4I6MEHA.3636@TK2MSFTNGP09.phx.gbl...
> > > > > Hi all.
> > > > >
> > > > > We are confused. (or confoozed, not sure which).
> > > > >
> > > > > System:
> > > > > Win2K3 Server
> > > > > SQL 2000 SP3a
> > > > > System has 6GB RAM.
> > > > > We have both PAE AND 3GB switches in boot.ini
> > > > >
> > > > > SQL Server is set to use 2000MB RAM and to use Set Working Set
Size.
> > > > >
> > > > > However, we get the error in the log:
> > > > > "Could not set working set size to 843776".
> > > > >
> > > > > Task Manager shows SQL Server using 1.7 GB approximately, with
about
> > > > > 15million page faults.
> > > > >
> > > > > Does this error mean that the wrong memory configuration gets
used?
> > What
> > > > is
> > > > > 843776 coming from? Certainly not anything we set up.
> > > > >
> > > > > How can we tell the true memory usage, and is this error causing
any
> > > > > problems?
> > > > >
> > > > > Thanks,
> > > > > James Hokes
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Relevant Pages