ODB-240000 ODBC error: [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]There is insufficient system memory in resource pool 'default' to run this query. SQLState: 37000 | Community
Skip to main content
Level 4
September 7, 2023
Solved

ODB-240000 ODBC error: [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]There is insufficient system memory in resource pool 'default' to run this query. SQLState: 37000

  • September 7, 2023
  • 2 replies
  • 2062 views

 

 

HI All, we are facing this error,

can u please help next steps to fix this issue

 

 

ODB-240000 ODBC error: [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]There is insufficient system memory in resource pool 'default' to run this query. SQLState: 37000

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by LakshmiPravallika

Hi @shrutii ,

 

Can you Please ping us the query which you tried , so that this error is coming.

 

Also Can you tell us when you are getting this error with brief steps(In a workflow or a Schema etc)...

 

Regards,

Pravallika.

 

 

2 replies

LakshmiPravallika
Community Advisor
LakshmiPravallikaCommunity AdvisorAccepted solution
Community Advisor
September 7, 2023

Hi @shrutii ,

 

Can you Please ping us the query which you tried , so that this error is coming.

 

Also Can you tell us when you are getting this error with brief steps(In a workflow or a Schema etc)...

 

Regards,

Pravallika.

 

 

ShrutiiAuthor
Level 4
September 7, 2023

getting this error, while running a wkf

LakshmiPravallika
Community Advisor
Community Advisor
September 7, 2023

Hi @shrutii ,

 

Can you Please share the Workflow query you are trying to run or the sample snippet of the Workflow to look into it.

 

Regards,

Pravallika.

AkshayAnand
Community Advisor
Community Advisor
September 7, 2023

Hi @shrutii 

 

You can refer the link which might explain your query. It looks like your query result is fetching more rows than the allocated RAM space, Could you please relook the SQL query code.

 

Regards

Akshay