I’m trying to use the dbt-external-tables package with my Snowflake account, through dbt Cloud. This should create raw tables for me, using S3 as the source. Below is my source configuration: version: 2 sources: - name: dc305_animals database: "{{env_var('DBT_DB_NAME')}}" schema: _raw …

If Terraform created the database/schema as “dev”.“_raw” then you either get Terraform to drop the quotes, always use uppercase, or always use quoted identifiers and lowercase names in Snowflake Note: @Mark Estey originally posted this reply in Slack . It might not have transferred perfectly.

I joined the Slack too, happy to be here Note: @adam.c.leppek originally posted this reply in Slack . It might not have transferred perfectly.

There’s a specific privilege in Snowflake to create external tables (different from just create table) did you check that the user has that permission inside the schema that it’s working on? Note: @Mark Estey originally posted this reply in Slack . It might not have transferred perfectly.

Hey Mark, I checked and the role that my user is assigned has that privilege inside the schema I want to create external tables in. Note: @adam.c.leppek originally posted this reply in Slack . It might not have transferred perfectly.

It’s strange, when I do queries directly in Snowflake, quoting the various parts of the fully qualified namespace, like “db”.“schema”, things seem to work. So maybe there’s something with how quoting works in the yml source config? Note: @adam.c.leppek originally posted this reply in Slack . It migh…

Are you seeing the failed query in Snowflake’s query history? That could also help if you see it’s not being rendered with correct names Note: @Mark Estey originally posted this reply in Slack . It might not have transferred perfectly.

Normally you don’t need quoted identifiers in Snowflake unless the object was created with them originally, so if you created that database/schema using something like “_raw” then it shouldn’t matter Note: @Mark Estey originally posted this reply in Slack . It might not have transferred perfectly.

If you can’t run normal statements on that same database and schema without quotes in Snowflake’s on interface, then that would be a sign that the database name or schema name was quoted on creation Note: @Mark Estey originally posted this reply in Slack . It might not have transferred perfectly.

If you want to check, see this doc on enabling quoted identifiers on sources: https://docs.getdbt.com/reference/resource-properties/quoting but my recommendation to save yourself a lot of headaches if you can is to rename the database and/or schema to not use quoted identifiers Note: @Mark Estey or…

I actually made this database and its schemas using terraform, so that could have something to do with it Note: @adam.c.leppek originally posted this reply in Slack . It might not have transferred perfectly.

You can check by just trying to run use database.schema in the Snowflake UI. If it only works with quotes around the database and/or schema name, then that’s what’s happening. Note: @Mark Estey originally posted this reply in Slack . It might not have transferred perfectly.

dbt-external-tables FAILS interacting with Snowflake

Help

Topic		Replies	Views
dbt-external-tables CAN'T FIND external stage Help snowflake , dbt-cloud	2	235	April 21, 2025
dbt_packages - dbt_external_tables Help snowflake , dbt-cloud	2	4733	October 18, 2022
unable to connect to specified database (snowflake) Help	3	18010	August 20, 2023
Accessing external tables in snowflake from dbt Help external-tables , snowflake , dbt-cloud	0	387	August 29, 2024
Problem with configurations Help	4	3821	April 16, 2024

dbt-external-tables FAILS interacting with Snowflake

Related topics