From 6a4125f0e52d4484c49c61ccffc725197bd2478c Mon Sep 17 00:00:00 2001 From: Kshitij Aranke Date: Thu, 26 Oct 2023 17:20:32 -0500 Subject: [PATCH] Update website/blog/2023-10-27-to-defer-or-to-clone.md Co-authored-by: Jason Ganz --- website/blog/2023-10-27-to-defer-or-to-clone.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/blog/2023-10-27-to-defer-or-to-clone.md b/website/blog/2023-10-27-to-defer-or-to-clone.md index 282048a6d23..a95b897a7e3 100755 --- a/website/blog/2023-10-27-to-defer-or-to-clone.md +++ b/website/blog/2023-10-27-to-defer-or-to-clone.md @@ -23,7 +23,7 @@ In this blog post, I’ll attempt to provide this guidance by answering these FA 1. What is `dbt clone`? 2. How is it different from deferral? 3. Should I defer or should I clone? - + ## What is `dbt clone`? `dbt clone` is a new command in dbt 1.6 that leverages native zero-copy clone functionality on supported warehouses to **copy entire schemas for free, almost instantly**.