Split SQL files to reduce memory load for claims#910
Merged
Conversation
chase-jones
approved these changes
Jun 12, 2025
github-project-automation
Bot
moved this from 👀 Ready for Review
to 🚀 Ready to Release
in The Tuva Project
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Describe your changes
The union + window function required more of the model to be in memory than if they were split apart. This becomes more noticeable with larger files. This update is related to this PR here. This one is applied to claims instead of clinical data since it suffers from the same issue.
How has this been tested?
Ran dbt build
Reviewer focus
None
Checklist before requesting a review
tuva_last_runto the final outputPackage release checklist
dbt_project.yml(Optional) Gif of how this PR makes you feel
Loom link