After upgrading Snowflake destination, the connections are failing due to failed cast columns. How do I grant alter table permissions to airbyte role in snowflake?

Granting ALTER TABLE Permissions to Airbyte Role in Snowflake The Snowflake destination v4.0.0+ requires

ALTER TABLE

permissions to support schema evolution and table modifications. [Snowflake Migration Guide] You can grant the necessary privileges by running the following SQL as an

ACCOUNTADMIN

(or a role with sufficient privileges), replacing the placeholders with your actual values:

-- Grant ALTER TABLE on existing tables
GRANT ALTER ON ALL TABLES IN SCHEMA <your_database>.<your_schema> TO ROLE <airbyte_role>;

-- Grant ALTER TABLE on future tables in your target schema
GRANT ALTER ON FUTURE TABLES IN SCHEMA <your_database>.<your_schema> TO ROLE <airbyte_role>;

-- Also grant on the airbyte_internal schema (required for v4.x)
GRANT ALTER ON FUTURE TABLES IN SCHEMA <your_database>.airbyte_internal TO ROLE <airbyte_role>;

Additional Recommended Permissions Based on the knowledge sources, the Airbyte role also needs the following privileges to function correctly in v4.x: On your target schema:

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

On the

airbyte_internal

schema (note: must be lowercase):

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

[Future Grants Issue] Why airbyte_internal Matters In v4.x, the connector creates temporary tables in the

airbyte_internal

schema (instead of the target schema) and uses

ALTER TABLE ... SWAP WITH

during Full Refresh | Overwrite syncs. This means permissions need to be granted in both schemas. [Future Grants Issue] > Note: The migration guide specifically states: "The connector now requires

ALTER TABLE

permissions to support schema evolution and table modifications. Grant your Snowflake user this permission before upgrading." [Snowflake Migration Guide] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai I had the following error:

SQL compilation error: error line 221 at position 6 Invalid privilege ALTER.

I'm sorry, but the knowledge sources do not contain enough information to definitively resolve this specific SQL compilation error regarding

Invalid privilege ALTER

in Snowflake. The knowledge sources confirm that

ALTER TABLE

permission is required after upgrading to Snowflake destination v4.0.0 [Snowflake Migration Guide], but they do not provide specific guidance on this error or an alternative syntax for granting it. A few things worth noting: • The error

Invalid privilege ALTER

suggests that Snowflake may not accept

ALTER

as a standalone grantable privilege in your environment or Snowflake edition. This is a Snowflake-side permission syntax issue rather than an Airbyte configuration issue. • Based on the community workaround documented in the GitHub issue, the privileges confirmed to be sufficient for Airbyte to function are

CREATE STAGE

and

CREATE TABLE

on the relevant schemas —

ALTER

was not explicitly listed as a separately granted privilege in that workaround. [Future Grants Issue] I'd recommend: 1. Checking the Snowflake documentation for the correct syntax to grant table-level privileges in your Snowflake edition. 2. Opening a support ticket with Airbyte support or filing a GitHub issue for clarification on exactly how

ALTER TABLE

permission should be granted for v4.x. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.