September 2, 2011 at 5:39 am
I patched my server up to sql 2005 service pack 3 cumulative update 4, I enabled Locked pages in memory I'm still getting the error below.
2011-09-02 02:23:49.03 spid1s 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): 10548, committed (KB): 5385056, memory utilization: 0%.
2011-09-02 02:28:36.24 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 318 seconds. Working set (KB): 122740, committed (KB): 4987656, memory utilization: 2%.
2011-09-02 02:32:55.08 Server Using 'dbghelp.dll' version '4.0.5'
2011-09-02 02:32:55.56 Server **Dump thread - spid = 0, PSS = 0x0000000000000000, EC = 0x0000000000000000
2011-09-02 02:32:55.60 Server ***Stack Dump being sent to E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0003.txt
2011-09-02 02:32:55.60 Server * *******************************************************************************
2011-09-02 02:32:55.60 Server *
2011-09-02 02:32:55.60 Server * BEGIN STACK DUMP:
2011-09-02 02:32:55.60 Server * 09/02/11 02:32:55 spid 0
2011-09-02 02:32:55.60 Server *
2011-09-02 02:32:55.60 Server * Non-yielding Resource Monitor
2011-09-02 02:32:55.60 Server *
2011-09-02 02:32:55.60 Server * *******************************************************************************
2011-09-02 02:32:55.60 Server * -------------------------------------------------------------------------------
2011-09-02 02:32:55.60 Server * Short Stack Dump
2011-09-02 02:32:56.71 Server Stack Signature for the dump is 0x00000000000001F2
Its mostly the 'significant part' message and sometimes the 'Resource Monitor' errors and occasionally the dump. All my searching, it seems that enabling locked pages is the fix for this. Is there anything else I can do?
September 2, 2011 at 5:54 am
What edition of SQL?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 2, 2011 at 6:13 am
SQL Server 2005 Standard. Maybe I didn't apply the cumulative update from this artice correcty?
http://support.microsoft.com/kb/970070
Version says 9.0.4226
September 2, 2011 at 6:25 am
Do you have the traceflag enabled?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 2, 2011 at 6:47 am
I don't believe so. Looking through the log at start up I'm not seeing 'Using locked pages for buffer pool
'
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply