add video url to faq #5861
add video url to faq #5861
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
added
content
github-actions
bot
added
Docs team
| :::tip Check out video example | ||
| As an additional resource, check out this example video add URL here, which demonstrates how to refactor the sample code by reducing the number of columns returned. | ||
| :::tip Video example | ||
| As an additional resource, check out [this example video](https://www.youtube.com/watch?v=sTqzNaFXiZ8), which demonstrates how to refactor the sample code by reducing the number of columns returned. |
There was a problem hiding this comment.
columns returned
rows returned
| @@ -17,11 +17,10 @@ Some common reasons for higher memory usage are: | |||
|
|
|||
| There are various reasons why you could be experiencing this error. We recommend you review your data models to see if there are any opportunities to optimize or refactor them. For example, you can try to reduce the number of columns being selected, use `group` or `where` clauses to filter data early in the query, or use `limit` clauses to reduce the amount of data being processed. | |||
There was a problem hiding this comment.
There are various reasons why you could be experiencing this error. We recommend you review your data models to see if there are any opportunities to optimize or refactor them. For example, you can try to reduce the number of columns being selected, use
grouporwhereclauses to filter data early in the query, or uselimitclauses to reduce the amount of data being processed.
There are various reasons why you could be experiencing this error but they are mostly the outcome of retrieving too much data back into dbt (via run_query() operations or similar macros, or even using database/schemas that have lots of other non-dbt related tables/views). You can try to reduce the amount of data / number of rows retrieved back into dbt by refactoring the SQL in your run_query() operation using group, where or limit clauses. Additionally, you can also use a database/schema with fewer non-dbt related tables/views.
github-actions
bot
added
size: small
|
thanks @jeremyyeo ! can you please have another look? |
this pr adds a video url to also explain how to solve the job memory limit failure in job run and development
internal slack: https://dbt-labs.slack.com/archives/C05CJT5MJF2/p1722309301858119?thread_ts=1721059396.203019&cid=C05CJT5MJF2