awe enable?

  • hello experts,

    please go through my server configuration

    windows server 2003 enterprise sdition 32 bit

    sql server 2005 enterprise edition 32 bit

    /pae enabled

    Total RAM 64 GB (i confused in this configuration it dosn't support more than 32 GB RAM please advise)

    should i require to enable awe

    should i require to set max server memory (if yes please tell the value?)

    should i require to set min server memory (if yes please tell the value?)

    please help its urgent

    thanks

  • Server 2003 32bit Enterprise RAM limit = 32GB

    Min Max memory should be set to something reasonable, is this a dedicated server just for SQL or will other apps be running on it?

  • its a dedicated server

  • Set Max memory at 26GB or there abouts, leaves enough for the OS to manage itself OK.

    If its dedicated I wouldnt worry about min memory so much as only SQL and the OS are using RAM so its not like anything else will be wanting the resources, but you could set it at a value if you wanted to.

    And yes I would enable AWE and also give the service account lock pages in memory rights

  • anthony,

    in windows server 2003 Lock pages memory default assigned to Administrator group and option for adding new user is disabled. i guess SQL account user need to add in administrator group right?

  • Configure it by changing Group Policy, ask your AD guys to put all your SQL servers into an OU then assign a GPO to that OU so that accounts can be set to have the LPIM right and it will only take presidence over that OU.

  • hi Anthony,

    can you please describe about OU and GPO as i am not aware about it,

    i already configured AWE enable and max server memory to 24 GB, i dont think its in effect because it shows in task manager only 3.5 GB consume. i doubt whether it is in effect. i guess lock pages memory permission issue, while added service account in administrator group.

  • Zeal-DBA (9/21/2013)


    i already configured AWE enable and max server memory to 24 GB, i dont think its in effect because it shows in task manager only 3.5 GB consume.

    Because locked pages is not enabled. Or because Task Manager is reporting memory usage incorrectly as it usually does.

    Don't add SQL to the administrators group, that's against security best practices. Add the sql server service account to the list of accounts that have lock pages in memory permission. If you can't do it, ask your AD administrator to do it for you.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • how do we confirm whether lock pages enabled or not. does It require server reboot. after adding service account in administrator group.

  • Do Not add SQL Server to the administrators group. That's a bad security practice, SQL does not need to be administrator and should not be administrator.

    After granting the SQL Server service account locked pages permissions, you need to bounce the service (not the server). If you don't have rights to do that permission assignment, ask your AD administrator to set up the correct OUs in Active Directory, add the SQL Server servers to that OU and set up the GPO to assign the required permissions.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 10 posts - 1 through 9 (of 9 total)

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