March 20, 2008 at 10:15 am
I receive the following two error messages in my sql logs and I have a feeling its affecting my application batch processing. I can't find much out about it on the internet. This is SQL 2005 SP2 X64 machine with 24 GBs of RAM running Windows 2003 SP2. Not many users at all on the server at all.
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): 130168, committed (KB):
17139648, memory utilization: 0%
A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 336 seconds. Working set (KB): 1552836, committed (KB): 4613352, memory utilization: 33%.
March 20, 2008 at 10:26 am
Although there is hotfix available for this issue that brings 9.00.3186.00. But My experience says it does not resolve issue completely. Hence, to resolve this issue you have to clear cache. You may do this using clearcache.exe file with -1 value.
How much memory your server has? What is Max Memory setting? If possible please let me know your sp_configure output.
[font="Verdana"]--www.sqlvillage.com[/size][/font]
March 20, 2008 at 10:43 am
24 GBs total. Do you have the KB article number for the hotfix?
max server memory (MB)16214748364721474836472147483647
March 20, 2008 at 12:20 pm
Do you have lock pages in memory enabled?
Are there other applications running on this server?
Is SSIS utilized on this server?
Is CLR in use on this server?
How many instances of SQL are running?
Are you min and max server memory options set?
March 20, 2008 at 12:29 pm
Do you have lock pages in memory enabled? No
Are there other applications running on this server? Just 2005
Is SSIS utilized on this server? No
Is CLR in use on this server? No
How many instances of SQL are running? 1
Are you min and max server memory options set? the sp_configure output is listed above in the thread.
March 20, 2008 at 12:36 pm
Hmm, with your responses I wouldn't be to alarmed about enabling lock pages in memory then, but it is still good practice to have it enabled.
You may want to read up on these articles: http://blogs.msdn.com/psssql/archive/2007/05/31/the-sql-server-working-set-message.aspx
http://blogs.technet.com/askperf/archive/2007/05/18/sql-and-the-working-set.aspx
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply