AWE settings.

Tech-Archive recommends: Fix windows errors by optimizing your registry



Present Server configuration 32 bit.

4 cpus, 6 gb ram. WINDOWS 2003 enterprise with
service pack 1

Sql 2000 Enterprise edition Service pack 3

SQL configured for maxium server memory is 4.5 gb
with awe enabled.

The startup switches used are /3GB and /PAE.

Local Security Settings window/Local Policies/User
Rights
Assignment/Lock Pages in Memory is set for sql
server start up user
account.

ISSUE

O.S is showing low available memory like 200 MB

PF is 5.5 GB all the time.

Presently if we remove the setting Local Security
Settings window/Local
Policies/User Rights Assignment/Lock Pages in Memory
it shows around
3GB available memory. If this policy setting is
enabled the available
memory is too low around in the range of 140 MB to
260 MB.

There is no heavy load on the system and it is a
dedicated SQL server
box. Memory used by SQL server engine is around 1.6
GB most of the
time.

I was under the impression the sql server memory
usage is on demand
based upon the load and the memory configuration.
Looks like by enabling
this option in the policy it reserves more memory
and leaves very less
memory for the O.S.


If there is any article or document supporting if
the policy setting needs to be there will be of great
help.


Thanks in advance.


Don







.

Relevant Pages

  • Re: /PAE Switch Config
    ... you're mixing memory up. ... If SQL can ... If you use the /3GB switch, SQL Server can take up to 3GB, leaving only ... But (from a discussion of Windows XP): ...
    (microsoft.public.windows.server.sbs)
  • [NT] NNTP Service in Windows Contains Memory Leak
    ... NNTP Service in Windows Contains Memory Leak ... An affected server could be restored to normal service by ...
    (Securiteam)
  • Re: Performance problems -- need guidance on scaling
    ... Thanks for the update on the FT Catalog corruption, ... will use, up to a max of 512Mb, if this memory is available. ... a server with 512 MB of RAM and a resource_usage value of 5 ... the data, you could, detach your SQL 2000 mdf & ldf files ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Memory Issues
    ... Exchange and SQL Server. ... you identified memory problems and large amounts of paging. ...
    (microsoft.public.sqlserver.setup)
  • Re: Windows 2000 Server StandardEdition /PAE Question
    ... specifically the SQL Server 2000 Standard Edition on that server. ... His point is that applications can only use up to 2 GB or RAM on ... a process running under Windows 2000 or Windows Server 2003 can ... used) with some of the memory being physical memory and some being virtual ...
    (microsoft.public.win2000.general)