Counters showing wrong memory usage

  • Hi Experts,

    I have a server with 5 installation all are active\passive cluster having 16GB RAM. Now the server is experiencing memory pressure . All the installations are 32bit and AWE enabled. I tried to figure out the issue by using the counter working set but its showing 100MB usage by each installation.

    Please let me know if I am doing anything wrong.

    TIA

  • The issue was due to server memory setting in which the min and max server memory were configured as 2000MB and SQL server was using this much memory was not releasing. In working set the value seems to be aroung 100MB.

  • select * from sys.dm_os_performance_counters

    where counter_name like 'page life%'

    Result of this query?

    Regards,
    Syed Jahanzaib Bin Hassan
    BSCS | MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA

    My Blog
    www.aureus-salah.com

  • the issue with x32 and awe is that memory is not released, I'd suggest you consider x64. You should also realise that the 2gb you allocate to each instance is only for the buffer/data cache, this does not include the procedure cache, various other memory pools, sql server engine, sql server agent, ssis and so on.

    Download process explorer ( from microsoft ) , this will show you what's using what on your server.

    http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

    [font="Comic Sans MS"]The GrumpyOldDBA[/font]
    www.grumpyolddba.co.uk
    http://sqlblogcasts.com/blogs/grumpyolddba/

  • Use the SQL Memory manager total server memory counter to see what SQL has allocated.

    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
  • Please post output of DBCC MEMORYSTATUS. Also, what is the average pages/sec and target server memory?

    Working set does not consider VAS and is not right to check memory pressure looking at workingg set.

  • First of all just check server required more RAM or not with the help of this query

    select * from sys.dm_os_performance_counters

    where counter_name like 'page life%'

    Regards,
    Syed Jahanzaib Bin Hassan
    BSCS | MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA

    My Blog
    www.aureus-salah.com

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

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