none
Error: System.OutOfMemoryException and Insufficient system memory in resource pool RRS feed

  • Question

  • Any workaround for this two errors? I am running SQL 2008R2 SP2 Ent 64-bit has 8 GB Ram out of 6 GB allocated to SQL VM.

    From SQL eror Log :

    insufficient system memory in resource pool 'default' Error: 701, Severity: 17, State: 225.
    When trying to run query from SSMS getting this error also all sql jobs throwing same error : An error occurred while executing batch. Error message is: Exception of type 'System.OutOfMemoryException' was thrown.

    Thanks for always providing Best solution


    Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach A.Shah



    • Edited by -kit Monday, June 16, 2014 6:38 PM
    • Moved by Kalman Toth Tuesday, June 17, 2014 11:28 AM Not database design
    Monday, June 16, 2014 6:36 PM

Answers

  • See this answered thread, may it's helpful for you: insufficient system memory in resource pool 'default'

    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    Tuesday, June 17, 2014 6:43 AM
    Moderator
  • Hi Lohicinisde,

    According to your error message, the error may be occurred by the following possible reasons, for example,  the ram was be completely used, reached the maximum memory allocation configured values in SQL Server or virtual memory is full and so on. Before you install the related cumulative update of SQL Server 2008 R2 SP2, I recommend you do the following steps for fixing this error. For example, allocate more memory to SQL Server, kill the unnecessary idle sessions, increase the RAM and virtual memory and reduce the number of users and so on.

    For more information, you can review the following article,

    http://nebraskasql.blogspot.com/2014/03/error-701-insufficient-system-memory.html

    In addition, you can run Profiler, and include the events SQL:StmtStarting, RPC:Starting, Error:Exception and Error:UserMessage and then filter on something suitable, for instance LoginName to see what statement that causes the error, and then we can move on from there.

    Regards,
    Sofiya Li


    Sofiya Li
    TechNet Community Support

    Tuesday, June 17, 2014 7:49 AM
    Moderator

All replies

  • Is this is production or development server?

    Try  to monitoring the same for some time and then decide your server has capacity issues and you need to increase that.

    Also you can  use resource governor to restrict memory for development servers where no such speed matters for you as that is not development. Also check if you can add some more page file\swap file on existing disk and see.

    You can try also, changing the third party or inbuilt backup schedule timing as might be backup time is clashing.

    Also check if any Anti-virus is going during such window, you can change the scan window.

    Definitely by error you had MS. Sql server exe. memory issues, :).

    Also you can try optimizing your queries which are memory intensive one.


    Santosh Singh

    Monday, June 16, 2014 7:10 PM
  • See this answered thread, may it's helpful for you: insufficient system memory in resource pool 'default'

    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    Tuesday, June 17, 2014 6:43 AM
    Moderator
  • Hi Lohicinisde,

    According to your error message, the error may be occurred by the following possible reasons, for example,  the ram was be completely used, reached the maximum memory allocation configured values in SQL Server or virtual memory is full and so on. Before you install the related cumulative update of SQL Server 2008 R2 SP2, I recommend you do the following steps for fixing this error. For example, allocate more memory to SQL Server, kill the unnecessary idle sessions, increase the RAM and virtual memory and reduce the number of users and so on.

    For more information, you can review the following article,

    http://nebraskasql.blogspot.com/2014/03/error-701-insufficient-system-memory.html

    In addition, you can run Profiler, and include the events SQL:StmtStarting, RPC:Starting, Error:Exception and Error:UserMessage and then filter on something suitable, for instance LoginName to see what statement that causes the error, and then we can move on from there.

    Regards,
    Sofiya Li


    Sofiya Li
    TechNet Community Support

    Tuesday, June 17, 2014 7:49 AM
    Moderator
  • Hello,

    Please run DBCC MEMORYSTATUS command and post output on skydrive I will analyze the output for you to get correct look what is actully causing OOM exception. Meanwhile can you look in SQL server errorlog if after OOM error there is DBCC MEMORYSTATUS output.

    Can you please post the query as well which is causing the issue.

    Sofiya can you pleas emove this thread to Database engine forum


    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.

    My TechNet Wiki Articles


    Tuesday, June 17, 2014 8:12 AM
    Moderator