adding transient dynamic table capabilities

[jhsb25]

resolves #
docs dbt-labs/docs.getdbt.com/#

Problem

Solution

Checklist

• I have read the contributing guide and understand what's expected of me
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX

[cla-bot]

Thanks for your pull request, and welcome to our community! We require contributors to sign our Contributor License Agreement and we don't seem to have your signature on file. Check out this article for more information on why we have a CLA.

In order for us to review and merge your code, please submit the Individual Contributor License Agreement form attached above above. If you have questions about the CLA, or if you believe you've received this message in error, please reach out through a comment on this PR.

CLA has not been signed by users: @jhsb25

[jhsb25]

@cla-bot check

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[bpruss]

I'm new here, is this an appropriate place to inquire about this PR and the issue it is trying to fix.
I had been following dbt-labs/dbt-adapters#716 and was really optimisitic it had made it into 1.9.
I saw multiple approval requests from jshb25. I was so optimistic that I added transient=true, to my dynamic table macro only to find that it didn't work. Did some searching and ended up here. Thanks for any info that can be provided.

[hawkinsrt]

I'm also curious about the status of this PR. We use dynamic tables for our analytic data marts but do not need the ability to time travel. It would be nice to avoid that cost and have them created as dynamic transient tables.

[anth-zen]

Sorry if this is inappropriate due to its sketchiness, but I wanted to share my hack/workaround in case it helps anyone else save a lot of money in Snowflake.

Disclaimer: The following hack is a generally horrible thing to do unless you're desperate, and it may cause other problems.

I was able to directly edit my local virtual environment to hard-wire the word "transient" into the dbt dynamic table macros. This forces dbt to always materialize dynamic tables as transient in your local dbt runs. This surely won't work in a default CI/CD pipeline, but for local development it is saving us a lot of Snowflake Fail-safe costs.

(I'm using dbt 1.10.3 and snowflake 1.9.4, so these references may be incorrect for other versions.)

In folder: .venv\Lib\site-packages\dbt\include\snowflake\macros\relations\dynamic_table

• create.sql
  • Change line 34 to say: create transient dynamic table
• replace.sql
  • Change line 47 to say: create or replace transient dynamic table

Note: These changes will certainly get reverted if you re-install or upgrade dbt locally, so you'll need to re-apply them.