For the complete documentation index, see llms.txt. This page is also available as Markdown.

Updating Scripts and Pipelines That Use Snowflake CREATE OR REPLACE Statements

Snowflake is releasing a behavior change for the CREATE OR REPLACE statement:

  • This statement now copies existing grants (subscription policies) to replacement objects by default.

  • Snowflake masking policies and row access policies (data policies) are NOT retained on the replacement object.

As a result, users whose access grants are retained may be able to query the replacement object without the intended masking or row-level restrictions until Immuta reapplies those policies.

Before changing production workflows

Complete these checks in each affected Snowflake account and environment.

1. Check the behavior change bundle status

As of October 16, the bundle is disabled by default, but account administrators may have enabled it themselves. Check each relevant Snowflake account by running the statement below:

SELECT SYSTEM$BEHAVIOR_CHANGE_BUNDLE_STATUS('2026_08');

Do not assume that checking one Snowflake account covers all environments. Development, test, staging, and production accounts may have different behavior change bundle settings.

Snowflake plans to move the bundle through additional rollout stages, but the timing is subject to change. Check the 2026_08 bundle status page for updated dates.

2. Identify affected statements

Search pipelines, deployment scripts, and generated SQL for CREATE OR REPLACE statements that replace tables or views protected by Immuta data policies.

For example, CREATE OR REPLACE TABLE marketing (c1 INT);

3. Update the SQL

You can add and test IGNORE GRANTS while the Snowflake behavior change bundle is disabled.

Add IGNORE GRANTS to each affected statement. For example,

  • Before: CREATE OR REPLACE TABLE marketing (c1 INT);

  • After: CREATE OR REPLACE TABLE marketing (c1 INT) IGNORE GRANTS;

This preserves the previous grant-handling behavior for workflows that did not use COPY GRANTS: existing access grants are dropped when the object is replaced. Immuta can then detect the replacement through object sync or schema monitoring and reapply the expected access and data policies.

4. Test in a non-production environment

In a test environment,

  1. Run a representative replacement workflow.

  2. Confirm the executed SQL contains IGNORE GRANTS.

  3. Confirm the replacement object is created successfully.

  4. Trigger Immuta object sync or schema detection.

  5. Confirm Immuta reapplies the expected access and data policies.

  6. Test access with representative users, including users who should

    1. Have access

    2. Be denied access

    3. See masked values

    4. Receive row-level filtering

  7. Confirm downstream jobs and applications behave as expected.

5. Roll out the change

After successful testing,

  1. Deploy the updated SQL to all affected workflows.

  2. Confirm the executed production SQL contains IGNORE GRANTS to make sure the change made earlier is executing correctly.

  3. Monitor the first production executions.

  4. Confirm Immuta completes object sync or schema monitoring and restores the expected grants and policies.

If more preparation time is needed

The preferred path is to update and validate the affected SQL. During Snowflake’s testing or opt-out period, a Snowflake administrator can disable the entire behavior change bundle by running the statement below:

Disabling the bundle also disables its other behavior changes, so the Snowflake administrator should review the broader impact before proceeding. This option provides additional preparation time, but it does not replace the required SQL changes. Once the bundle becomes generally enabled, customers can no longer opt out.

Last updated

Was this helpful?