There is insufficient system memory in resource pool 'default' to run this query

Question

There is insufficient system memory in resource pool 'default' to run this query

krishnamohan6669

SSC Veteran

Points: 234
More actions
January 1, 2014 at 8:19 am

#284083

Os version : Windows Server 2003, Enterprise Edition 32-bit AWE enabled.
Sql Server:Microsoft SQL Server 2008 R2 (SP2) - 10.50.4276.0 (Intel X86)
2 node physical cluster.
min memory:2048 Max memory:10240 min memory per query:1024
total RAM: 32GB
Page File Space:3.98 GB
Three months back we go this issue "There is insufficient system memory in resource pool 'internal' to run this query" we have max server memory as 12 GB then and from the reference of the link we had changed it to 10 gb http://social.technet.microsoft.com/Forums/sqlserver/en-US/60d20f7a-8d64-48b1-ade9-8ba648e5945c/there-is-insufficient-system-memory-in-resource-pool-default-to-run-this-query?forum=sqldatabaseengine
and now it is repeatedly occuring every week.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Jeff Moden SSC Guru Points: 1004363 More actions · Answer 1

krishnamohan6669 (1/1/2014)
and now it is repeatedly occuring every week.

So, what is running at that time "every week"? I ask because I'm thinking the "top" symptom of not having enough memory to run a given query is at fault. You need to find that query and fix it so that it runs more efficiently.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

krishnamohan6669 SSC Veteran Points: 234 More actions · Answer 2

Perl script job which inserts data for about 5GB daily.and they are doing the same process from many months and they are experiencing the problems from recent months.

Can u justify or recommend anything after watching the attached memory status.

Robert Davis One Orange Chip Points: 28027 More actions · Answer 3

My first recommendation would be to upgrade to 64 bit. Preferably on Windows 2012.

My blog: SQL Soldier[/url]
SQL Server Best Practices: SQL Server Best Practices
Twitter: @SQLSoldier
My book: Pro SQL Server 2008 Mirroring[/url]
Microsoft Certified Master: SQL Server, Data Platform MVP
Database Engineer at BlueMountain Capital Management[/url]

Jeff Moden SSC Guru Points: 1004363 More actions · Answer 4

krishnamohan6669 (1/1/2014)
Perl script job which inserts data for about 5GB daily.and they are doing the same process from many months and they are experiencing the problems from recent months.
Can u justify or recommend anything after watching the attached memory status.

Heh... I've run into those exact problems before. I don't know what the Perl script is actually doing for you that might be special but, if it's just a flat file import, then BULK INSERT is your best bet.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

krishnamohan6669 SSC Veteran Points: 234 More actions · Answer 5

Found that more MAX I/O Waittime is recorded with spotlight,so trying to increase the virtual file size. should wait and see wether this occurs again.

ChrisM@Work SSC Guru Points: 186127 More actions · Answer 6

krishnamohan6669 (1/7/2014)
Found that more MAX I/O Waittime is recorded with spotlight,so trying to increase the virtual file size. should wait and see wether this occurs again.

Jeff is proposing that you examine the perl script for optimisation opportunities. Having identified the perl script as the culprit, the cause of your problem, this would be the logical next step. Either it can be improved, or it cannot, and if it cannot, then you eliminate it from your list of entities to examine. Painting the rims of a broken-down car might make it look pretty but it wastes time and won't get you home.

^{“Write the query the simplest way. If through testing it becomes clear that the performance is inadequate, consider alternative query forms.” - Gail Shaw}

For fast, accurate and documented assistance in answering your questions, please read this article.
Understanding and using APPLY, (I) and (II) Paul White
Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden