Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Thanks Oded for patiently answering my questions. My problem got resolved when I splitted the huge database operations into small batches (after configuring MSDTC).</p> <p>During Large Database operations, insufficient memory error may come. But this error may not be visible if it is inside a Transaction.</p> <p>1) Remove transaction and see if “Insufficient Memory” exception is available.</p> <p>2) Breakdown large database operations into small batches to remove the “Insufficient Memory” exception</p> <p>3) Configure MSDTC in app tier and database</p> <p>4) Ensure that WCF does not time out abruptly. It should have enough time based on database operations.</p> <p>5) Observe the behavior when the database server is restarted (This is last option)</p> <p>Some useful information available in </p> <p><a href="https://stackoverflow.com/questions/1995718/there-is-insufficient-system-memory-in-resource-pool-default-to-run-this-query">There is insufficient system memory in resource pool &#39;default&#39; to run this query</a></p> <p><a href="https://stackoverflow.com/questions/6401918/msdtc-exception-during-transaction-c">MSDTC Exception during Transaction: C#</a></p> <p><a href="https://stackoverflow.com/questions/6395769/c-asp-net-exception-some-times-only-during-long-database-operation">C# ASP.Net: Exception (some times only) during long database operation</a></p> <p><a href="https://stackoverflow.com/questions/2296374/sql-server-2005-error-701-out-of-memory">SQL Server 2005 Error 701 - out of memory</a></p> <p>Some other checks:</p> <p>1) Whether the windows account under which the database engine is running have "Lock pages in memory permission"?</p> <p>2) Chek SQL Sever service pack version.</p> <p>3) Check size of virtual memory paging file</p> <p>4) Check max server memory</p> <p>5) Determining MemToLeave Settings</p> <p>6) "SQL Server Memory Configuration and MemToLeave"</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload