@kapa.ai, I'm getting this error when trying to connect to a snowflake schema using the same credentials. it works find for the same user, role, wh, credentails on Airbyte v1.5.1 but I get the following error on v2.0.1 when I was trying to create a snowflake destination on it: Failed to save Snowflake due to the following error: Could not connect with provided configuration. Error: SQL access control error: Insufficient privileges to operate on table '_AIRBYTE_CONNECTION_TEST_B72EA58DE6E34CA3939D18DC3AC542B4'. L*ogs: check_connection_destination job*

The error you're seeing —

SQL access control error: Insufficient privileges to operate on table '_AIRBYTE_CONNECTION_TEST_...'

— is a known permission classification issue in the Snowflake destination connector. It's being correctly identified as a configuration/permissions problem, not a system error. What's happening In Airbyte v2.x (destination-snowflake v4.x), the connector underwent significant changes. One relevant fix is that

"Insufficient privileges"

errors are now classified as

config_error

, meaning your Snowflake role lacks the necessary privileges to operate on the schema or table being tested. [fix PR] Additionally, in v4.x, the connector now creates temporary tables in an

airbyte_internal

schema (instead of the same schema as the target tables), which is a behavior change from earlier versions. [future grants issue] What to check/fix Your Snowflake role likely needs additional privileges that weren't required in v1.5.1. Based on the knowledge sources, here are the privileges you need to grant: On your target schema:

GRANT USAGE ON SCHEMA <your_schema> TO ROLE <airbyte_role>;
GRANT CREATE STAGE ON SCHEMA <your_schema> TO ROLE <airbyte_role>;
GRANT CREATE TABLE ON SCHEMA <your_schema> TO ROLE <airbyte_role>;

On the

airbyte_internal

schema (note: must be lowercase):

GRANT USAGE ON SCHEMA airbyte_internal TO ROLE <airbyte_role>;
GRANT CREATE STAGE ON SCHEMA airbyte_internal TO ROLE <airbyte_role>;
GRANT CREATE TABLE ON SCHEMA airbyte_internal TO ROLE <airbyte_role>;

Also, since v4.0.0, the connector requires

ALTER TABLE

permissions to support schema evolution:

GRANT ALTER TABLE ON ALL TABLES IN SCHEMA <your_schema> TO ROLE <airbyte_role>;
GRANT ALTER TABLE ON FUTURE TABLES IN SCHEMA <your_schema> TO ROLE <airbyte_role>;

[migration guide] The

airbyte_internal

schema may not exist yet — you may need to create it and grant the Airbyte role the necessary privileges on it. [future grants issue] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.