﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Administering / SQL Server 2005  / memory error / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Wed, 22 May 2013 22:42:55 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: memory error</title><link>http://www.sqlservercentral.com/Forums/Topic472380-146-1.aspx</link><description>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: [url=http://blogs.msdn.com/psssql/archive/2007/05/31/the-sql-server-working-set-message.aspx]http://blogs.msdn.com/psssql/archive/2007/05/31/the-sql-server-working-set-message.aspx[/url][url=http://blogs.technet.com/askperf/archive/2007/05/18/sql-and-the-working-set.aspx]http://blogs.technet.com/askperf/archive/2007/05/18/sql-and-the-working-set.aspx[/url][url=http://support.microsoft.com/kb/918483]http://support.microsoft.com/kb/918483[/url][url=http://weblogs.asp.net/omarzabir/archive/2007/10/19/a-significant-part-of-sql-server-process-memory-has-been-paged-out-this-may-result-in-performance-degradation.aspx]http://weblogs.asp.net/omarzabir/archive/2007/10/19/a-significant-part-of-sql-server-process-memory-has-been-paged-out-this-may-result-in-performance-degradation.aspx[/url]</description><pubDate>Thu, 20 Mar 2008 12:36:54 GMT</pubDate><dc:creator>Adam Bean</dc:creator></item><item><title>RE: memory error</title><link>http://www.sqlservercentral.com/Forums/Topic472380-146-1.aspx</link><description>Do you have lock pages in memory enabled? NoAre there other applications running on this server? Just 2005Is SSIS utilized on this server? NoIs CLR in use on this server? No How many instances of SQL are running? 1Are you min and max server memory options set?  the sp_configure output is listed above in the thread.</description><pubDate>Thu, 20 Mar 2008 12:29:18 GMT</pubDate><dc:creator>mgraulich</dc:creator></item><item><title>RE: memory error</title><link>http://www.sqlservercentral.com/Forums/Topic472380-146-1.aspx</link><description>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?</description><pubDate>Thu, 20 Mar 2008 12:20:02 GMT</pubDate><dc:creator>Adam Bean</dc:creator></item><item><title>RE: memory error</title><link>http://www.sqlservercentral.com/Forums/Topic472380-146-1.aspx</link><description>24 GBs total. Do you have the KB article number for the hotfix?max server memory (MB)	16	2147483647	2147483647	2147483647</description><pubDate>Thu, 20 Mar 2008 10:43:41 GMT</pubDate><dc:creator>mgraulich</dc:creator></item><item><title>RE: memory error</title><link>http://www.sqlservercentral.com/Forums/Topic472380-146-1.aspx</link><description>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.</description><pubDate>Thu, 20 Mar 2008 10:26:27 GMT</pubDate><dc:creator>Mohan  Kumar</dc:creator></item><item><title>memory error</title><link>http://www.sqlservercentral.com/Forums/Topic472380-146-1.aspx</link><description>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%.</description><pubDate>Thu, 20 Mar 2008 10:15:09 GMT</pubDate><dc:creator>mgraulich</dc:creator></item></channel></rss>