Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / DB Engine / SQL Server / September 2008

Tip: Looking for answers? Try searching our database.

A significant part of sql server process memory has been paged out

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
FredG - 24 Sep 2008 20:42 GMT
Calling all MVPs,

I am seeing this error on a new server build.
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):
39336, committed (KB): 89208, memory utilization: 44%.

Environment:
HP DL580 G4 32GB Ram
Windows Server 2003 Enterprise x64 Edition build 3790.srv03_sp2_gdr
SQL Server 2005 Standard edtion x64 build 9.0.3233

because its SQL Standard, AWE is not enabled and Lock Pages in memory not
granted to the sql server service account.
However, I did try and add the service account to the Lock Pages in memory
right but no luck, same message.

If I set the max server memory for SQL Server greater than 6GB, I receive
the warning message. Less than 6GB no message.

the Memory | Available MBytes perfmon counter displays 30GB available.

Any help is appreciated.
Andrew J. Kelly - 24 Sep 2008 21:49 GMT
Fred,

Have a look here but do you have any other apps running on that server?

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.as
px


Signature

Andrew J. Kelly    SQL MVP
Solid Quality Mentors

> Calling all MVPs,
>
[quoted text clipped - 21 lines]
>
> Any help is appreciated.
FredG - 25 Sep 2008 13:57 GMT
Hi Andrew,

Yes I have looked at this post. The servers available bytes is high, the
System Cache Resident Bytes are low, 75mb as well as the cache bytes. SQL
Server: Memory Manager | Target Server Memory is okay and the Total Server
Memory is only 1GB. With all these low values I do not understand the SQL
Warnings.

There are no other applications on this server, new build, only SQL Server
2005.

I also looked at the Processes: private bytes counter for each process
running on the server, each one is under 10MB.

> Fred,
>
[quoted text clipped - 27 lines]
> >
> > Any help is appreciated.
Raman Gosala - 25 Sep 2008 16:07 GMT
Fred,

Is this server an 64-bit Standard Edition, I came across the same issue and
got it resolved.

Microsfot says to ignore the error if you see it at the start up.
how ever use this KB and follow every step and you should be good let me
know how it goes.

1)     Disabled the TCP Chimmney
2)     Updated the BIOS drivers
3)     Updated the IBM Broadcom NIC card drives
4)     make sure you are using the 64-bit .NET drivers
5)     Lock pages in memory.
6)     Memory setting has to be changed Example:: min.  ser to 2000 and max
to 5000
7) Donto forget to apply this patch
http://support.microsoft.com/default.aspx?scid=kb;EN-US;936594?
and restart the box you should not see the error again.

Regards
Raman Gosala

> Calling all MVPs,
>
[quoted text clipped - 19 lines]
>
> Any help is appreciated.
FredG - 25 Sep 2008 16:20 GMT
Hello Raman,

Thanks for the information. I will give it a try and post my results.

> Fred,
>
[quoted text clipped - 42 lines]
> >
> > Any help is appreciated.
FredG - 25 Sep 2008 16:21 GMT
Hi Raman,

Yes it is 64bit standard.

> Fred,
>
[quoted text clipped - 42 lines]
> >
> > Any help is appreciated.
FredG - 26 Sep 2008 20:49 GMT
Hello Raman,

We have implemented every item you suggested and we continue to see the same
warning.

NOTE: So far I only see this during SQL Server startup.

> Fred,
>
[quoted text clipped - 42 lines]
> >
> > Any help is appreciated.
Andrew J. Kelly - 30 Sep 2008 03:46 GMT
Sorry for the late reply Fred I was moving.  If it is only during startup
and not during normal running I wouldn't worry too much about it.

Signature

Andrew J. Kelly    SQL MVP
Solid Quality Mentors

> Hello Raman,
>
[quoted text clipped - 57 lines]
>> >
>> > Any help is appreciated.
FredG - 30 Sep 2008 20:53 GMT
Hi Andrew,
No worries.

So far I have only noticed during startup.

> Sorry for the late reply Fred I was moving.  If it is only during startup
> and not during normal running I wouldn't worry too much about it.
[quoted text clipped - 60 lines]
> >> >
> >> > Any help is appreciated.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2010 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.