Cloning databases: EVENT_TABLE parameter is not copied to the cloned database (Pending)¶

Attention

This behavior change is in the 2026_07 bundle.

For the current status of the bundle, refer to Bundle history.

When cloning a database, Snowflake no longer copies the EVENT_TABLE parameter to the destination database, regardless of the role used for the clone operation.

Before the change:: Cloning a database with the ACCOUNTADMIN role copied the EVENT_TABLE parameter value to the destination database. Using any other role caused the clone operation to fail.
After the change:: The EVENT_TABLE parameter is not copied to the destination database regardless of the role used for the clone operation. Cloning no longer fails when a non-ACCOUNTADMIN role is used. If the EVENT_TABLE parameter is required on the cloned database, a user with the ACCOUNTADMIN role must set it explicitly after the clone operation completes.

This change ensures that cloning behavior is consistent across roles and doesn’t depend on the ACCOUNTADMIN role. It prevents clone failures and aligns with security best practices.

If your organization relies on automated cloning workflows, review those processes to ensure they don’t depend on the EVENT_TABLE parameter being automatically copied to the destination database. If the EVENT_TABLE parameter is required on the newly cloned database, configure it explicitly after the clone operation using a role with the appropriate privileges.

Ref: 2365