Memory Utilization is very low 13.8 GB out of 20 GB

  • Everyday I experience block in the database but checked query plan is ok ,all indexes already in place,no fragmentation issue..

    When i was looking into memory some thing is wrong:

    This a SQL dedicated server,it has sqlserver 2000 ent edition 32 bit installed

    Total memory: 25 GB

    max memory setting--20 GB

    But sql always using only 13.8 GB.AWE is enabled.Should i migrate to SQLSERVER 2000 ent 64 bit.

    I can't migrate 2005/2008 as application won't support..

    Pls suggest..

  • The only 64-bit version of SQL 2000 is the Itanium, and I doubt you have one of those lying around, or want one for that matter.

    Is there actually a problem resulting from the low memory?

    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
  • I am not sure whether there in any memory issue but i can see SQL only using 13.8 GB memory constantly but i have configured max memory 20GB.

    I was suggested if i can use sqlserver 2000 EE 64 bit the issue could be solved.

    Please suggest how can i confirmed what the actual issue.I can see daily 6/7 times temp blocking occurred.

  • Alone (11/12/2011)


    I am not sure whether there in any memory issue but i can see SQL only using 13.8 GB memory constantly but i have configured max memory 20GB.

    Ok, again, is that a problem? Are you seeing signs of memory pressure in SQL Server?

    I was suggested if i can use sqlserver 2000 EE 64 bit the issue could be solved.

    If you bought an Itanium server. SQL 2000 does not have an x64 version, only IA64. It's a completely different processor architecture and, as far as I know, they've been discontinued for a few years.

    I can see daily 6/7 times temp blocking occurred.

    Which may or maynot, but probably doesn't, have anything to do with memory. Blocking is often poor indexing or poor code.

    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
  • Thanks for this information.

    Main issue is slowness and when ever slowness occurs i see temp block in databases ,so when i kill the culprit blocker the issue resolved.I was able to trace culprit stored procedure but it is tuned.

    How to check memory pressure?

  • If it's causing blocking, it's probably not tuned.

    http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-1/

    http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-2/

    or http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

    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 6 posts - 1 through 5 (of 5 total)

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