2005 Standard (x64) memory problems

  • I have a severe problem with my sql server installation. The server:

    Microsoft Windows Serer 2003

    Standard x64 Edition

    Service Pack 2

    12.8GB of Ram

    Sql Server 2005 - 9.00.3054.00 (X64)

    I have 10GB allocated to SQL Server at min and max which leaves 2.8 for the o/s. There are no other applications running on the server.

    What I am seeing in the even log is the following error

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

    The error varies and can log many entries over a variable period of time:

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

    We have already tried adjusting min/max memory lower with even worse results.

    I have looked at various sources and articles.

    (KB): 24484 - maybe trimming (hard)

    920739 - it's not this (copy files > 500mb)

    931308 - It's not SAP 3

    http://msmvps.com/blogs/omar/archive/2007/09/19/a-significant-part-of-sql-server-process-memory-has-been-paged-out-this-may-result-in-performance-degradation.aspx

    Seems to address the problem with ClearCache.

    Anyway, please help if you can!

  • A friend of mine, Jeremy Brown on here, ran into this in production a few months back. Here's what they did to fix the issue:

    - Configure the SQL Server service account to have the right to lock pages in memory.

    - Configure SQL Server for AWE memory support.

    While it doesn't make a whole lot of sense becuse 64-bit shouldn't need AWE support, that's what they ended up doing and seeing a noticeable performance difference.

    K. Brian Kelley
    @kbriankelley

  • Interesting. We have been having this problem for a long time now, so I would say anything is worth a shot. Although this recommendation might be a hard sell to my operations guy.

  • You might private mail Jeremy. He has the charts and performance stats to back up what he is saying.

    K. Brian Kelley
    @kbriankelley

Viewing 4 posts - 1 through 3 (of 3 total)

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