SQL 2005 STD EDITION error log

  • We have sql 2005 std editon SP2 installed on win 2003 enterprise edition sp1 on 32-bit platform.

    We have 4 Physical Processor (16 logical processor)and 16 GB RAM and 6 hdd with RAID 6 Technologies. We have also enabled AWE to access ram more than 4 GB FOR SQL.

    In SQL Error Log it is showing that --

    "16 processor and 4096 mb ram detected"

    Also in DBCC MEMORYSTATUS it shows the AWE ALLOCATED : 13 GB

    and Physical Memory Available in task manager is around 1.96 GB out of 16 GB RAM.Also all the threads of CPU is allocatd to CPU, still it is going very high when small querry runs.

    We would like to know that the above error is due to my improper memory setting or what ?

    Please guide on the above.

    vrijesh

  • Do you have PAE enabled?

    Is this 32 bit and 2005? You posted in a 2000 forum, please be aware of where you are posting. (moved).

    http://www.sql-server-performance.com/articles/per/awe_memory_sql2000_p1.aspx should help you.

    Also, are the min/max settings of SQL Server set to the max available (and min)?

  • Hi Vrijesh,

    PAE is enabled by default in Win2K3 SP1 so unless you find a /NOPAE entry in boot.ini you are fine from OS perspective.

    Do you find a "Address Windowing Extensions enabled" message in the errorlog as well?

    If 1. sp_configure 'AWE' returns 1 for run_value 2. "Lock Pages in Memory" has been granted to the SQL Server service account and 3. the service was restarted after it was set, you should be good to go.

    If DBCC MEMORYSTATUS reports AWE ALLOCATED 13 GB then I'm quite sure that's how it is but double-check the above 3 things (The perfcounter SQL Server Memory Manager: Total server memory should report everything in the bufferpool including AWE as well).

    Oh, and as Steve points out, do NOT forget to set Max server memory for SQL Server (sp_configure 'max server memory', 14 GB or whatever number, no too high, you had in mind).

    HTH!

    /Elisabeth

    elisabeth@sqlserverland.com
    MCITP | MCT
    http://sqlblog.com/blogs/elisabeth_redei/
    http://linkedin.com/in/elisabethredei

  • Just a quick comment -

    Looks like a Quad core machine - 4 proc, 4 cores each. Any particular reason you didn't go with x64 bit?

    It is meant to address more memory. Might be worth looking at.

    Greg E

Viewing 4 posts - 1 through 3 (of 3 total)

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