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

Question

Post reply

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

pshaship

SSCertifiable

Points: 6125
More actions
September 7, 2010 at 6:25 pm

#225704

We have SQL Server 2005 EE x64 with SP3.
Getting the below error is normal when the SQL Service starts?
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): 38888, committed (KB): 105728, memory utilization: 36%.
Because we are seeing this message only when SQL Server service is restarted.
And this is a DR server server and it is NOT opened to users and have 16 GB of memory. So I did NOT understand why the Memory is paging out even if there is NO activity?
Lock pages is NOT enabled as it's a not active Server:hehe:
Thanks

Viewing 8 posts - 1 through 7 (of 7 total)

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

sqlstad SSCrazy Points: 2484 More actions · Answer 1

Look at this article what explains what you can do:

"A significant part of sql server process memory has been...[/url]

jncarter Ten Centuries Points: 1195 More actions · Answer 2

If it only happens during sql startup it can be safely ignored. Check out this blog post by CSS.

http://blogs.msdn.com/b/psssql/archive/2009/05/12/sql-server-reports-working-set-trim-warning-message-during-early-startup-phase.aspx

-Jeremy

Nils Gustav Stråbø SSChampion Points: 11259 More actions · Answer 3

I have seen this when min and max server memory is set to the same value and SQL Server consumes all of the memory it is configured for.

george sibbald SSC Guru Points: 104210 More actions · Answer 4

if this is a DR server are you using database mirroring? that could cause this if you are mirroring a large number of databases and there is catching up to do following the restart.

---------------------------------------------------------------------

Nils Gustav Stråbø SSChampion Points: 11259 More actions · Answer 5

Sorry, I didn't see that you wrote that this only happens when SQL Server starts. As long as you only see this during startup, there is nothing to worry about. I think another poster posted a link to an article about this.

pshaship SSCertifiable Points: 6125 More actions · Answer 6

if this is a DR server are you using database mirroring? that could cause this if you are mirroring a large number of databases and there is catching up to do following the restart

No. We are NOT using Mirroring.

We are using Log shipping for DR.

Steve-3_5_7_9 SSChampion Points: 10832 More actions · Answer 7

Since this is x64 are you using "Lock Pages In Memory"? This should eliminate the startup message that you are receiving with regards to paging. Instead you'll see "Using locked pages for buffer pool."