Post reply

memory utilization

  • January 3, 2011 at 2:27 am

    #230005

    A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 329 seconds. Working set (KB): 71796, committed (KB): 354792, memory utilization: 20%.

    i am getting the above error in the sql logs due to which a cluster failover happened. can any one suggest me why this issue has happened?

  • January 3, 2011 at 3:29 am

    #1268393

    I think the following KB article is worth a read:

    http://support.microsoft.com/kb/918483

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • January 3, 2011 at 11:41 am

    #1268594

    Please post your memory configuration and SQL Server information , 32 bit 64 bit etc

    Thank You,

    Best Regards,

    SQLBuddy

  • January 4, 2011 at 3:48 am

    #1268840

    At a guess: need to adjust your memory settings as per the kb mentioned.

    Tricky thing to diagnose in some cases, but you may benefit from trying to trace what event has caused this to happen.

    Carlton..

  • January 4, 2011 at 8:29 am

    #1269001

    1) the cause is often due to bugs, especially in drivers. windows 2003 had a large file copy bug that did this and HP's ILO stuff likewise. I had a client that got hit by BOTH of those and it was ugly.

    2) do you have your max memory set for sql server and if so to what value and how much ram on the system? 32 bit or 64 bit?

    3) beware locking pages in memory. if you do this and don't know what you are doing you can really screw yourself. http://support.microsoft.com/kb/918483 has this statement: “You should make additional considerations before you assign the ‘Lock pages in memory’ user right. If you assign this user right on systems that are configured incorrectly, the system may become unstable or experience a performance decrease of the whole system. Additionally, event ID 333 may be logged in the event log.”

    4) what else besides SQL Server is running on the box?

    Best,
    Kevin G. Boles
    SQL Server Consultant
    SQL MVP 2007-2012
    TheSQLGuru on googles mail service

  • January 5, 2011 at 3:17 am

    #1269377

    I have totally 8GB of memory and out of which 6GB is allocated for SQL(Max setting for SQL)

    no other application is running in that box other than SQL

  • January 5, 2011 at 4:57 am

    #1269413

    - 32 or 64 bit?

    - have you got lock pages in memory set?

    - version of SQL?

    Carlton.

  • January 5, 2011 at 6:39 am

    #1269457

    6 out of 8 is likely a tad too high, but not enough to cause you problems like you are seeing. Only SQL - so you are not using SSIS, SSAS, SSRS then, right? If not, then whether or not you are 32 bit or 64bit (which it would still be nice to know) the cause is likely what I said - a bad driver or firmware.

    Oh, one other thing - exactly what build of SQL Server are you on? (SELECT @@VERSION)

    Best,
    Kevin G. Boles
    SQL Server Consultant
    SQL MVP 2007-2012
    TheSQLGuru on googles mail service

  • January 6, 2011 at 5:31 am

    #1270023

    I experienced this issue a few weeks back. Turns out I was doing a large file copy in windows and it was depleting sql memory. Turns out this bug 'Runaway System Cache Increase Kills SQL'

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

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