A significant part of sql server process memory has been paged out. This may result in performance degradation

If you are using SQL Sever Server standard edition 64 bit on a Windows 2003 64bit, you will frequently encounter this problem where SQL Server says:

A significant part of sql server process memory has been paged out. This may result in performance degradation. Duration 0 seconds. Working set (KB) 25432, committed (KB) 11296912, memory utilization 0%

The number in working set and duration will vary. What happens here is SQL Server is forced to release memory to operating system because some other application or OS itself needs to allocate RAM.

We went through many support articles like:

  • 918483: How to reduce paging of buffer pool memory in the 64-bit version of SQL Server 2005
  • 905865: The sizes of the working sets of all the processes in a console session may be trimmed when you use Terminal Services to log on to or log off from a computer that is running Windows Server 2003
  • 920739: You may experience a decrease in overall system performance when you are copying files that are larger than approximately 500 MB in Windows Server 2003 Service Pack 1

But nothing solved the problem. We still have the page out problem happening every day.

The server has 16 GB RAM where 12 GB is maximum limit allocated to SQL Server. 4 GB is left to OS and and other application. We have also turned off antivirus and any large backup job. 12 GB RAM should be plenty because there's no other app running on the dedicated SQL Server box. But the page out still happens. When this happens, SQL Server becomes very slow. Queries timeout, website throws error, transactions abort. Sometimes this problems goes on for 30 to 40 minutes and website becomes slow/unresponsive during that time.

I have found what causes SQL Server to page out. File System cache somehow gets really high and forces SQL Server to trim down.


You see the System cache resident bytes are very high. During this time SQL Server gets much less RAM than it needs. Queries timeout at very high rate like 15 per sec. Moreover, there's high SQL Lock Timeout/sec (around 15/sec not captured in screen shot).


SQL Server max memory is configured 12 GB. But here it shows it’s getting less than 8 GB.

While the file system cache is really high, there’s no process that’s taking significant RAM.


After I used SysInternal’s CacheSet to reset file system cache and set around 500 MB as max limit, memory started to free up.


SQL Server started to see more RAM free:


Then I hit the “Clear” button to clear file system cache and it came down dramatically.


Paging stopped. System cache was around 175 MB only. SQL Server lock timeout came back to zero. Everything went back to normal.

So, I believe there's either some faulty driver or the OS itself is leaking file system cache in 64bit environment.

What we have done is, we have a dedicated person who goes to production database servers every hour, runs the CacheSet program and clicks "Clear" button. This clears the file system cache and prevents it from growing too high.

There are lots of articles written about this problem. However, the most informative one I have found is from the SQL Server PSS team:



The final solution is to run this program on Windows Startup:

SetSystemFileCacheSize 128 256

This sets the lower and higher limit for the System Cache. You need to run this on every windows startup because a restart will undo the cache setting to unlimited.

You can run the program without any parameter to see what is the current setting.

Download the program from this page:


Go to the end and you will get the link to the SetSystemFileCacheSize.zip


  • Thanks for such a well thought out and presented article.

    We have a customer with SQL 2005 Std Ed x64 with 32GB of RAM. This issue is killing their performance.

    Based on this issue I cannot see how x64 Std Ed is even a viable and stable production platform.

    We'll try a few options and further research.

    Thanks again.

  • I second what Rolf said. I just walked into a customer today after they moved to x64 Standard Edition over the weekend, and they now have the very same problem. Is there a command line version of the CacheSet tool? Upgrading to Ent. Ed. is out of the question, but having a person hit a 'clear' button every hour is not practical.

  • We had this exact problem, and it was solved via premium MS support with a hotfix related to Broadcom drivers....a bug, plain and simple. The hotfix was from a couple of months ago, and at the time was not fully regression tested..but it solved that problem..this was after weeks of exhausting all of our resources.


  • D Weiner said : We had this exact problem, and it was solved via premium MS support with a hotfix related to Broadcom drivers....a bug, plain and simple

    Do you have any further details - link to the hotfix etc. We have excatly the issue here with SQL 2005 Standard build 3054 x64 on Win 2003 Enterprise x64 and we use Broadcom too. I am pursuing PSS but any info you have would be greatly appreciated.

    Thanks in advance for any help you can give.

  • Re by previous post:

    For info we are currently on this level of Broadcom drivers.

    Broadcom NetXtreme Gigabit Ethernet dated 28/08/2006

    Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client) dated 25/05/2007

    BASP Virtual Adapter dated 26/01/2007

  • Same problem over here (we also have a Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client)). But I'm not sure if this is the reason.

  • D Weiner - what was the hot fix that MS supplied.

  • We have the same issue.We have two HP DL580 G5 servers with 4 quad core CPU and 64 GB of ram running in Active-passive cluster.Both servers have the same issue.Hp has the same brand of ethernet card(Broadcom). If you tell us the hotfix or the article number we can check it out.

  • We use the same servers as Zafer and are facing exactly the same symptoms.

    Please provide us further information on the hotfix...



  • I updated the post with the final solution. Please check the bottom part of the post.

  • Does anyone know if this issue applies to the 64bit Enterprise Edition as well? We have a server, 64 bit and Enterprise edition and I noticed these messages showing up in the Event Viewer/Application Log since yesterday.

  • It happes on Enterprise Edition as well unless you use the SetSystemFileCacheSize to cap the file cache on every windows restart.

  • We have this message appear on 32-bit instances. Does the fix work for this flavor also?

  • What is the hotfix? Where I can find it?


  • The memory/Processor/disk specs you list, is that a report I can print from SQL server?


  • We've had this identical problem. The support engineer identified the Broadcom issue, so we changed the NICs to Intel. Still a huge problem!!!

    We'e running the 64bit Enterprise Edition on a pair of Dell r900s with 120GB of RAM--non clustered, Windows 2003 Server R2 SP2.

    The issue is still not resolved and causing us major problems in our production environment.

    Interestingly enough one of the two servers seems to be ok while the other just about tanks!

  • We'll give it a try..thanks!

  • Nice article.
    Could you tell me how you generated the stats about the memory usage, physicaldisk and sql server (gray background image)?

    Sorry for the novice question but I can't find anything about it.


  • It's available with Windows. Control Panel -> Administrative Tools -> Performance

Comments have been disabled for this content.