10.32 Release Notes (with behavior changes): Sep 05, 2026 - Sep 09, 2026¶

Behavior change bundles¶

This release contains the following behavior change bundles:

The status for each bundle will change again in the following behavior change release; 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¶

PERIOD data type (General availability)¶

With this release, Snowflake is pleased to announce the general availability of the PERIOD data type. A PERIOD value stores an anchored, half-open temporal range [begin, end): an inclusive beginning bound and an exclusive ending bound of the same element type. Unlike interval types, which represent a duration with no fixed location in time, a PERIOD value identifies a specific range on the timeline, such as an employment window or a version validity interval. The beginning and ending bounds can be DATE, TIME, or TIMESTAMP values.

A family of PERIOD_* functions constructs PERIOD values, accesses their beginning and ending bounds, compares two ranges, and combines ranges.

For more information, see PERIOD data type.

Data governance updates¶

Data metric function FILTER: Modify or clear a filter on an existing association¶

You can now use a FILTER clause with ALTER TABLE or ALTER VIEW … MODIFY DATA METRIC FUNCTION to set, replace, or clear the row filter on an existing data metric function (DMF) association without dropping and recreating it.

ALTER TABLE customer_data
  MODIFY DATA METRIC FUNCTION SNOWFLAKE.CORE.NULL_COUNT
    ON (email)
    FILTER (status = 'ACTIVE');

Specify empty parentheses (FILTER ()) to clear the filter so the DMF evaluates all rows. You can’t combine FILTER with SUSPEND, RESUME, EXPECTATION, or SET in the same MODIFY statement.

For more information, see Apply data quality checks to a subset of rows.

Release notes change log¶