# Understanding how DBT handles tables for no down time

**URL:** <https://discourse.getdbt.com/t/understanding-how-dbt-handles-tables-for-no-down-time/5186>\
**Category:** Help\
**Created:** [October 27, 2022, 12:16pm UTC](https://discourse.getdbt.com/t/understanding-how-dbt-handles-tables-for-no-down-time/5186 "2022-10-27T12:16:36Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![obar1](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.getdbt.com/obar1/32/1221_2.png) [@obar1](https://discourse.getdbt.com/u/obar1)\
**Post date:** [October 28, 2022, 12:07pm UTC](https://discourse.getdbt.com/t/understanding-how-dbt-handles-tables-for-no-down-time/5186/4 "2022-10-28T12:07:48Z")

</div>

user can query table that are under refresh - the risky bit is that  
with B/G you do atomic switch and avoid that possibility [Performing a blue/green deploy of your dbt project on Snowflake](http://discourse.getdbt.com/t/performing-a-blue-green-deploy-of-your-dbt-project-on-snowflake/1349)

---

_[View the full topic](https://discourse.getdbt.com/t/understanding-how-dbt-handles-tables-for-no-down-time/5186)._