Describe the bug

I used the set_sql_header macro to declare a BigQuery scripting variable and initialize it so it can be used in the context of my model. The model materialization is of type incremental with incremental_strategy="insert_overwrite" and creates a partitioned table.
The initial run (i.e. not incremental) works fine. However a subsequent run (incremental) fails due to syn

Tell us about the problem you're trying to solve

When specifying a Dataset_id, the Google UI often includes the project_id in its naming like this: project_id:dataset_id

Describe the solution you’d like

In the BigQuery destination code, we could accept both syntax:

• project_id:dataset_id
• dataset_id

So it's smoother for the end user whether project_id is specified or not?

I'm new to the idea of Data Vault 2.0 and I'm reading the Dan Linstedt book to understand it better.

To help me get a better perspective of how dbtvault works I would like to know how difficult do you think it would be to add support for BigQuery?

Are there specific features of Snowflake which makes it better for running dbt/dbtvault ?

Thanks,
Jacob