AWE setup for SQL Server...

  • Hi,

    If the current buffer hit cache ration is consistently above 99% then, Is it benefit to adding RAM to a server to boost hardware performance of sql server? why?

    And how to manage AWE setting and all, please let me know in deep understanding.

    Thanks in advance

  • You will not achieve a "deep understanding" without putting in some time learning on your own. Feel free to use Google.

    Here are some good articles to get you started:

    PAE and 3GB and AWE oh my[/url]

    AWE and 3GB: An Empirical Picture

    Mysteries of Windows Memory Management Revealed, Part 1 of 2

    Understanding the VAS Reservation (aka MemToLeave) in SQL Server

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • A Buffer Cache Hit Ratio of 99%+ is a good thing. It means that the requested data pages are coming from memory, as opposed to having to be read from disk. That means the opposite of what you're thinking: you don't have memory pressure (at least in that aspect).



    Twitter: @SQLife
    Email: sqlsalt(at)outlook(dot)com

  • Is this x86 (32bit) or x64?

  • x(86) 32 bit only

  • mohan.bndr (5/1/2012)


    Hi,

    If the current buffer hit cache ration is consistently above 99% then, Is it benefit to adding RAM to a server to boost hardware performance of sql server? why?

    And how to manage AWE setting and all, please let me know in deep understanding.

    Thanks in advance

    youo might want to look at a few other metrics as well - i always look at Page life expectancy when i look at buffer cache hit ratio

    MVDBA

  • I would think that you aren't under memory pressure, but you'd have to look at more than this. Check target server memory, check the disk activity for how pressured it is, and how the CPU performs.

    The links that OPC.Three posted should help you with AWE.

Viewing 7 posts - 1 through 7 (of 7 total)

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