You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've enjoyed your YT video about DBT and though a little tip might help you to adjust your sequence rowcount usage with something more future proof. I ran into the same problem a while ago myself and solved it by combining hints from Snowflake forums and Stack Overflow.
The parameter approach I'l describe also avoids some sequence oddities when using larger values as outlined in Mark's and Peter's comments.
While Snowflake has the limitation of generators requiring a "constant" value, you can use a parameter instead of a constant. This effectively "freezes" you calculated value, but updates it with each run of e.g. a stored procedure. I'd suggest to use the lowest date you currently have as base for your calculation in the parameter as outlined in my answer on Stackoverflow.
Little self promo - in case you think that approach is useful, feel free to like my SO answer as well ;)
The text was updated successfully, but these errors were encountered:
Hi Randy,
I've enjoyed your YT video about DBT and though a little tip might help you to adjust your sequence rowcount usage with something more future proof. I ran into the same problem a while ago myself and solved it by combining hints from Snowflake forums and Stack Overflow.
The parameter approach I'l describe also avoids some sequence oddities when using larger values as outlined in Mark's and Peter's comments.
While Snowflake has the limitation of generators requiring a "constant" value, you can use a parameter instead of a constant. This effectively "freezes" you calculated value, but updates it with each run of e.g. a stored procedure. I'd suggest to use the lowest date you currently have as base for your calculation in the parameter as outlined in my answer on Stackoverflow.
Little self promo - in case you think that approach is useful, feel free to like my SO answer as well ;)
The text was updated successfully, but these errors were encountered: