What are your thoughts on using the state:modified on production runs? Is that even possible and is the juice worth the squeeze? Perhaps running only views that have changed plus all physical tables? Views don’t take a ton of resources from our warehouse db (snowflake), but when you have a few hundred views to run that starts to add up.
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Run dbt tests (contracts), slim builds, and format checks via github action for CI/CD | 0 | 1973 | August 30, 2023 | |
More time coding, less time waiting: Mastering defer in dbt | 3 | 892 | June 10, 2024 | |
How Could DBT Models be Customised for Improved Maintenance and Achievement? | 0 | 216 | June 18, 2024 | |
slim CI - Running only modified models on deploy w/ dbt core | 0 | 305 | January 27, 2025 | |
dbt Squared: Leveraging dbt Core and dbt Cloud together at scale | 2 | 1656 | October 4, 2023 |