Create zero-copy clones on Snowflake

[@KahanDataSolutions]

Deliver more impact w/ modern data tools, without getting overwhelmed See how in The Starter Guide for Modern Data → www.kahandatasolutions.com/guide

[@halaaljomaat3663]

Your videos all are amazing, thanks

[@KahanDataSolutions]

Glad you like them! Thanks for watching

[@RaviTheVlogger]

Very useful topic. thanks for the video

[@KahanDataSolutions]

Glad you found it helpful!

[@boblautenbach5308]

Great Video....shouldn't the cloned DB view ddl refernece the clone DB table and not the original source. The example you showed makes it appear like cloned DDL will still reference the source DB and not the cloned DB?

[@ramashankar4829]

Nice video - thanks

[@KahanDataSolutions]

Thanks for watching!

[@jamesbalkite1656]

If the source of the cloned view changes , does those changes get replicated to the target throughout its lifecycle. This DDL scenario is obviously after a target view is cloned from a source view. Thank!!

[@KahanDataSolutions]

If I understand your question correctly, I don't believe it would. Once you clone, it is essentially a brand new object and should be treated as a completely separate entity. With that in mind, the underlying source query of your view would match at the time of cloning, but any changes after that would not automatically reflect in the other.

[@saisumanthnagasuri7741]

@@KahanDataSolutions what happens if the source table get dropped ,still the cloned table exists? Please help me

[@imvengeance2921]

This is very helpful, thanks a lot. One question though, when the DDL gets cloned, should we be using Fully qualified names because we need the cloned view to reference the cloned object right? In the video the view in the cloned db is pointing to a obj in source db, so what if I need cloned view to reference cloned obj in cloned db? I know my question is confusing sorry

[@saisumanthnagasuri7741]

What happens if the source get dropped ,still the cloned table exists? Please give the clarification.