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

SJT

SJT — Wed, 30 Sep 2009 16:03:58 GMT

We think we have isolated our issue to the Qlogic HBA driver that our SQL servers use to connect to the back end storage, but unfortunately the latest available driver doesn't seem to resolve the issue. We still have some other workarounds that MS has recommended left to try - if any of these work I'll post an update.

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

Anne Carpenter — Tue, 28 Jul 2009 19:24:02 GMT

We installed Microsoft Windows Dynamic Cache Service and it seemed to work for a few weeks, but now we're back to the same problem again.

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

PK — Mon, 27 Apr 2009 05:51:45 GMT

Hi,

We have the same problem and have raised it with MS.

There looks to be a solution to this coming out very soon.

blogs.msdn.com/.../sql-server-locked-pages-and-standard-sku.aspx

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

SJT — Wed, 15 Apr 2009 19:27:45 GMT

We are having the same issue (SQL 2005 SP2/Windows 2003 SP2 x64). I'd also be interested to hear if anyone has had any luck with the Windows Dynamic Cache Service tool.

Also to re-address the original issue, it seems like the trick is to determine which process is originally causing Windows to trim its memory. In the above analysis it is assumed to be due to the Windows file cache, but possible issues with hardware/drivers are also alluded to. Has anyone found any commonality that may point towards a driver issue? For reference we are running on Dell servers with Broadcom NICS/drivers.

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

john chantha — Wed, 01 Apr 2009 16:33:11 GMT

Has anyone else tried this?

I have the same problem.

www.microsoft.com/.../details.aspx

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

omar — Sat, 07 Feb 2009 14:17:17 GMT

Microsoft release a new tool which seems to be solving this problem:

www.microsoft.com/.../details.aspx

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

Jack Burgess — Wed, 28 Jan 2009 16:58:12 GMT

We're having the same issue with SQL 2008 Ent Ed 64 on Windows 2008.

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

Mike — Tue, 13 Jan 2009 15:55:54 GMT

I think this has cropped back up with SQL 2008

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

Codermonkey — Thu, 11 Dec 2008 11:08:20 GMT

I wonder if LargeSystemCache setting would have any effect?

technet.microsoft.com/.../cc784562.aspx

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

James Cass — Thu, 04 Dec 2008 07:07:12 GMT

Can this issue be solved by upgrading the underlying operating system to Windows 2008?

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

RR — Wed, 01 Oct 2008 20:54:34 GMT

I am strugeling with Micorsoft since 3 weeks regarding this issue. I am thrown between the SQL & OS team. I have applied SP2, CU#9, KB 920739 & 953600. Any other hints?

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

Thomas — Thu, 18 Sep 2008 00:21:27 GMT

One must select Report View (Ctrl+R) to see the data in Performance Monitor as shown.

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

omar — Wed, 09 Jul 2008 17:29:29 GMT

Hi guys, the gray screenshots you see are collected from Performance Monitor. It comes with Windows.

Control Panel => Administrative Tools => Performance

Click on the + button. Now select SQL Server related categories from the dropdown and add the counters you want to monitor.

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

Rob — Wed, 09 Jul 2008 17:17:06 GMT

As an employee with Microsoft SQL Server Support and very familiar with this issue, I want to first thank Omar for his detailed analysis. However, this is one of many possible causes for this problem.

The bottom line: The issue is caused because the OS trims SQL Server in response to memory pressure it is dealing with. SQL Server has no control over being trimmed. The OS controls this.

What customers should do in response to this error is to do as Omar did and look to see what is causing the OS pressure. In this case it was clearly the System Cache, but that in no way is applicable to every situation.

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

John — Tue, 24 Jun 2008 14:25:55 GMT

Omar,

Please, do you may help me, with the Clearcache.exe, file. We have now the same problem and need urgently solve this.

john_zuniga at h o t m a i l

Thanks.

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

Bryan Hunt — Wed, 11 Jun 2008 21:08:02 GMT

Omar,

Can you tell me what utility that you used to display the performance counters in your examples above?

Thanks.

Bryan Hunt

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

Nicola Milani — Tue, 25 Mar 2008 11:49:13 GMT

How can I obtain the sql server report that you use in this article (I intend theese one with gray background)?

Thank you, bye

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

Trucking Nerd — Thu, 07 Feb 2008 22:42:05 GMT

We are running into this 17890 all of a sudden on SQL 2005 SP2 as well. We have found an interesting way to make this happen on command though. We were humming along just fine until we created a virtual server machine and turned it on. As soon as we turn it on, SQL barfs this message. It then repeats every so often until we turn the machine off, then the problem ceases to exist.

The virtual server is microsoft virtual server 2005 R2. We have tried it with a couple of virtual servers, as soon as you start one, the SQL 2005 installed on the host starts puking these errors. Wondering if anyone else has observed this as the cause for these mysterious issues?

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

Russell Albert — Wed, 09 Jan 2008 10:17:49 GMT

Has anyone got a definitive fix for this? I have just started getting it on Windows Server 2003 SP2 (64-bit) with SQL 2005 SP2 (64-Bit). Also does anyone know where I can get ClearCache?

Thanks

Russell

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

Jeremy — Fri, 16 Nov 2007 19:43:05 GMT

Look at two things.

1. Lock pages in memory local group policy set for the SQL Server service account.

2. AWE (yes, even in 64 bit) enabled in SQL Server 2005 configuration.