I just finished listening to this passively, and I'm now excited to deep dive into this further later. Just onboarding to Snowflake as of recently, and was a bit disconcerted to see most DCM implementations be imperative. I am happy that it was acknowledged in this video and that Snowflake is going to be offering a native declarative solution!
Mind Blown!!!! I just checked today, 2024-08-20, and it looks like all of these are at least in public preview! Wow. I'd better get cracking on some DB pipelines!
This looks great @JeremiahHansen-Snowflake Would you please help me with below though? 1) Does this also provide the concept of Change Tracking Table similar to provided by SchemaChange? 2) In your opinion can this be used for Role Privileges Management? 3) In what ways this would prove beneficial over Terraform?
How to rename column or change column type in declarative approach? 🤔 It looks cool at first sight but it is not flexible compared to imperative approaches, where detailed control over the execution order and specific operations is sometimes necessary.
Hey there @emanueol, our new declarative DCM capabilities are going to be a game changer! To answer your question, the ALTER capability of our new CREATE OR ALTER (CoA) command will be aligned with the current ALTER functionality. Meaning if don't support a change today with ALTER we won't support it with CoA. So for column type changes in particular the same limitations apply. Hope that helps!
@@JeremiahHansen-Snowflake yes thanks, its great idea the CoA. How about other object types like mviews, views or dynamic tables which for now can only have new column added by fully recreating it ? not easy to add columns to mviews or dynamic tables without loosing existing materialization? anyway.. boosting CoA to other tabular objects like mviews, views or dynamic tables would be great.
Initially we will only support the existing features/capabilities of each object, so if you can't ALTER it today you won't be able to CoA it initially. But I imagine that overtime we can work to make that better.
Any chance you can make that repo publicly available?
I just finished listening to this passively, and I'm now excited to deep dive into this further later. Just onboarding to Snowflake as of recently, and was a bit disconcerted to see most DCM implementations be imperative. I am happy that it was acknowledged in this video and that Snowflake is going to be offering a native declarative solution!
Mind Blown!!!! I just checked today, 2024-08-20, and it looks like all of these are at least in public preview! Wow. I'd better get cracking on some DB pipelines!
This looks great @JeremiahHansen-Snowflake Would you please help me with below though? 1) Does this also provide the concept of Change Tracking Table similar to provided by SchemaChange?
2) In your opinion can this be used for Role Privileges Management?
3) In what ways this would prove beneficial over Terraform?
3) A lot faster
This is a great video. Would you be able to share the code?
When will create or alter be in GA and how will it impact the change of large snowflake setups?
How to rename column or change column type in declarative approach? 🤔 It looks cool at first sight but it is not flexible compared to imperative approaches, where detailed control over the execution order and specific operations is sometimes necessary.
I do get a message "Git Repository is not supported" when trying to create one? Is there any pre-requisites to start using the feature?
Yep, it's still a PrPr feature. So please work with your account team to get it enabled.
will this work with azure devops git repos?
great 😊i wonder how column type changes handled
Hey there @emanueol, our new declarative DCM capabilities are going to be a game changer! To answer your question, the ALTER capability of our new CREATE OR ALTER (CoA) command will be aligned with the current ALTER functionality. Meaning if don't support a change today with ALTER we won't support it with CoA. So for column type changes in particular the same limitations apply. Hope that helps!
@@JeremiahHansen-Snowflake yes thanks, its great idea the CoA.
How about other object types like mviews, views or dynamic tables which for now can only have new column added by fully recreating it ? not easy to add columns to mviews or dynamic tables without loosing existing materialization? anyway.. boosting CoA to other tabular objects like mviews, views or dynamic tables would be great.
Initially we will only support the existing features/capabilities of each object, so if you can't ALTER it today you won't be able to CoA it initially. But I imagine that overtime we can work to make that better.