# How best to copy schemas in redshift?

**URL:** <https://discourse.getdbt.com/t/how-best-to-copy-schemas-in-redshift/8581>\
**Category:** Help\
**Created:** [June 5, 2023, 8:22pm UTC](https://discourse.getdbt.com/t/how-best-to-copy-schemas-in-redshift/8581 "2023-06-05T20:22:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![alibrarydweller](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@alibrarydweller](https://discourse.getdbt.com/u/alibrarydweller)\
**Post date:** [June 5, 2023, 8:22pm UTC](https://discourse.getdbt.com/t/how-best-to-copy-schemas-in-redshift/8581/1 "2023-06-05T20:22:34Z")

</div>

## The problem I’m having

I’m experienced with dbt but not so much with redshift. My `dbt build` takes in excess of an hour and once the tables are built I’m looking for a fast way to copy many at once from schema to schema.

## The context of why I’m trying to do this

I’d like to have an up-to-date series of personal schemas for development without duplicating the compute or the time of running `dbt build` in my own profile.

## What I’ve already tried

Not sure where to start, it seems copying tables to s3 might be one avenue? Is there even a native feature for this?

---

<div class="post-metadata">

**Author:** ![joellabes](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.getdbt.com/joellabes/32/3980_2.png) [@joellabes](https://discourse.getdbt.com/u/joellabes)\
**Post date:** [June 6, 2023, 4:22am UTC](https://discourse.getdbt.com/t/how-best-to-copy-schemas-in-redshift/8581/2 "2023-06-06T04:22:15Z")

</div>

Hey @alibrarydweller, you’re a bit early, but we’re going to have a native `dbt clone` command coming, most likely in dbt v1.6 (July 2023): [[CT-2348] [Feature] `dbt clone` command · Issue #7256 · dbt-labs/dbt-core · GitHub](https://github.com/dbt-labs/dbt-core/issues/7256)

In the meantime, Snowflake has a clone function ([Creating a dev environment quickly on Snowflake](https://discourse.getdbt.com/t/creating-a-dev-environment-quickly-on-snowflake/1151)), but I’m not sure if there’s something equivalent for Redshift offhand.

---

<div class="post-metadata">

**Author:** ![alibrarydweller](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@alibrarydweller](https://discourse.getdbt.com/u/alibrarydweller)\
**Post date:** [June 6, 2023, 1:44pm UTC](https://discourse.getdbt.com/t/how-best-to-copy-schemas-in-redshift/8581/3 "2023-06-06T13:44:02Z")

</div>

Oh wow, that’s spot on for what I was thinking of.

If I’m reading correctly it will come out in core in July and then be up to the adapter/redshift maintainers to implement after that?

---

<div class="post-metadata">

**Author:** ![joellabes](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.getdbt.com/joellabes/32/3980_2.png) [@joellabes](https://discourse.getdbt.com/u/joellabes)\
**Post date:** [June 8, 2023, 3:05am UTC](https://discourse.getdbt.com/t/how-best-to-copy-schemas-in-redshift/8581/4 "2023-06-08T03:05:24Z")

</div>

Redshift support should be there on day one!