Home Forums SQL Server 2005 SQL Server 2005 Performance Tuning "A significant part of sql server process memory has been paged out. This may result in a performance degradation" RE: "A significant part of sql server process memory has been paged out. This may result in a performance degradation"

  • January 19, 2010 at 10:00 pm

    #1105823

    muruecos (1/18/2010)

    Hello, I have the following problem:

    "A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 92984, committed (KB): 1688060, memory utilization: 5%."

    I get this error every two-three minutes aproximatly, since 10 days ago. My server has the following caracteristics:

    Windows server 2003 Standar Edition SP2 (32bits)

    intel(R) Xeon(TM) CPU 3.6GHz and 3.5GB de RAM.

    SQL Server 2005 Standar Edition 9.00.3068.00 SP2 (32bits).

    SQL Server hasn´t allocated MIN nor MAX memory.

    I enclose two files with performance and administration task.

    I check the counter 'SQL Server Buffer: Buffer Cache Hit Ratio' for half an hour and the average value

    is 99% aproximatly.

    Now, my sql server doesn´t response, it´s very very very slow.

    How can I solve this problem??, which causes are??. It`s emergency. I need help.

    Thanks!!.

    What changed 10 days ago? Answer that and you'll have the solution to your problem. Do you have a "runaway" query running? Did someone install some new software or hardware on the server? Did someone promote some code or a change to the code?

    If it hasn't been overwritten yet, check the default trace file... IIRC, it's in the same directory as the SQL Server log files which you might also want to check. Also, check the Windows Server error logs...

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)