9.27 Release Notes (with behavior changes): Sep 08, 2025-Sep 10, 2025

Attention

This release has completed. For differences between the in-advance and final versions of these release notes, see Release notes change log.

Behavior change bundles

This release contains the following behavior change bundles:

Bundle NameStatus in this ReleasePrevious Status
2025_06Disabled by default; admins can enable for testingN/A (introduced in this release)
2025_05Enabled by default; admins can disable for opt-outDisabled by default
2025_04Generally enabled; admins can no longer enable/disableEnabled by default

The status for each bundle will change again in the following behavior change release, planned for October 13-15, 2025; however, this schedule is subject to change.

For more information about bundle statuses and how they may impact your accounts, see About Behavior Changes.

SQL updates

Retrieve bind variable values (Preview)

With this release, you can retrieve the values of the bind variables for queries that have been executed by using the BIND_VALUES table function in the INFORMATION_SCHEMA schema. Using this function, you can retrieve bind variable values from any code that supports bind variables, including Javascript and Snowflake Scripting code.

You can also access these bind variable values from the bind_values column in the output for the QUERY_HISTORY Account Usage view, the QUERY_HISTORY Organization Usage view, or the QUERY_HISTORY function in the INFORMATION_SCHEMA.

Note

To use this feature, the 2025_06 bundle must be enabled.

For more information, see Retrieve bind variable values.

Data pipeline updates

Dynamic tables: Support for base tables with zero data retention

You can now create dynamic tables on base tables with zero data retention (DATA_RETENTION_TIME_IN_DAYS = 0). This feature doesn’t apply to shared base tables.

For more information, see Data retention period.

Data lake updates

New system function to replace the catalog integration for an externally managed Apache Iceberg™ table

Use the new SYSTEM$SET_CATALOG_INTEGRATION system function to replace the catalog integration associated with an externally managed Apache Iceberg™ table.

You might use this function to access the latest Iceberg features for your tables, such as write support for externally managed Iceberg tables. You might also use this function to roll back to the original Glue catalog integration, if needed.

You can also use this function to migrate your tables to a different Iceberg REST catalog integration.

For more information, see SYSTEM$SET_CATALOG_INTEGRATION.

Release notes change log

AnnouncementUpdateDate
Release notesInitial publication (preview)Sep 05, 2025
New system function for replacing the catalog integration associated with an externally managed Apache Iceberg™ tableAdded to Data lake updatesSep 19, 2025
Dynamic tables: Support for base tables with zero data retentionAdded to Data pipeline updatesOct 21, 2025