# How to use Bigquery dry\_run with dbt ?

**URL:** <https://discourse.getdbt.com/t/how-to-use-bigquery-dry-run-with-dbt/11589>\
**Category:** Help\
**Tags:** testing, best-practice, bigquery, dbt-core\
**Created:** [January 15, 2024, 8:58pm UTC](https://discourse.getdbt.com/t/how-to-use-bigquery-dry-run-with-dbt/11589 "2024-01-15T20:58:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![majorcemp](https://avatars.discourse-cdn.com/v4/letter/m/3ec8ea/32.png) [@majorcemp](https://discourse.getdbt.com/u/majorcemp)\
**Post date:** [January 15, 2024, 8:58pm UTC](https://discourse.getdbt.com/t/how-to-use-bigquery-dry-run-with-dbt/11589/1 "2024-01-15T20:58:21Z")

</div>

## I use Bigquery and dbt core 0.25

## do you know how can i use the option `dry_run` of Bigquery with dbt ?

---

<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:** [January 16, 2024, 12:03am UTC](https://discourse.getdbt.com/t/how-to-use-bigquery-dry-run-with-dbt/11589/2 "2024-01-16T00:03:06Z")

</div>

Hey @majorcemp, dbt core 0.25 doesn’t exist - where are you seeing that version number? Are you using the Cloud CLI beta perhaps?

Regardless, as far as I know we haven’t implemented any dry run functionality in Core directly, however there is an [accompanying pip project](https://pypi.org/project/dbt-dry-run/) made by a dbt user which you might find helpful

---

<div class="post-metadata">

**Author:** ![majorcemp](https://avatars.discourse-cdn.com/v4/letter/m/3ec8ea/32.png) [@majorcemp](https://discourse.getdbt.com/u/majorcemp)\
**Post date:** [January 16, 2024, 12:18am UTC](https://discourse.getdbt.com/t/how-to-use-bigquery-dry-run-with-dbt/11589/3 "2024-01-16T00:18:35Z")

</div>

0.20 version I’m using the dbt core, I’ll have a look at the project thanks a lot, do you know any other ways of using the Bigquery dry\_run ? I would like to test my SQL code on Bigquery no only the jinja and yaml from dbt.  
Or maybe a specific linter that would catch the same errors Bigquery could catch when using dry\_run ?