10.12 Release Notes (with behavior changes): Apr 03, 2026-Apr 08, 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, planned for May 8-12, 2026; 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¶

CHECK constraints for standard tables (General availability)¶

CHECK constraints for standard tables are now generally available. A CHECK constraint enforces a condition on the values that can be inserted into or updated in one or more columns of a table. The condition is a SQL expression that you define when you create or alter the table.

CHECK constraints are enforced, which means that any INSERT or UPDATE operation that violates the constraint results in an error. You can define CHECK constraints inline as part of a column definition or out-of-line in a separate clause.

For more information, see CHECK constraints.

New features¶

Dynamic table refresh boundaries¶

You can now use DYNAMIC_TABLE_REFRESH_BOUNDARY() in a dynamic table definition to prevent an upstream dynamic table from being refreshed together with the downstream dynamic table. This lets you decouple dynamic table pipelines so that each pipeline refreshes independently. Cascading refreshes and snapshot isolation do not apply across the boundary.

For more information, see Dynamic table refresh boundary.

Programmatic notifications for Trust Center findings (Public preview)¶

You can now configure programmatic notifications for Trust Center findings using notification integrations such as webhooks (PagerDuty, Slack, Microsoft Teams) and queues (Amazon SNS, Azure Event Grid, Google Pub/Sub). When a Trust Center scanner detects a finding that meets the configured severity threshold, Snowflake sends a notification to your specified endpoint. This allows you to receive Trust Center alerts independent from Snowsight through your preferred monitoring tools.

For more information, see Programmatic notifications for Trust Center findings.

Access history improvements¶

Access history lets you monitor the SQL statements executed in Snowflake. It keeps track of the following types of statements:

• Data Manipulation Language (DML) statements. For example, statements used to insert data into a table.
• Data Query Language (DQL) statements. For example, statements that use a SELECT statement to project data.
• Data Definition Language (DDL) statements. For example, statements that create or alter a Snowflake object.

Snowflake is expanding which SQL statements are included in the access history. This release adds support for the following:

• CREATE STREAM statements.
• SHOW AGGREGATION POLICIES, SHOW AUTHENTICATION POLICIES, SHOW NETWORK POLICIES, and SHOW PASSWORD POLICIES.
• DESCRIBE JOIN POLICY, DESCRIBE NETWORK POLICY, DESCRIBE AUTHENTICATION POLICY, and DESCRIBE PASSWORD POLICY (DESCRIBE can be abbreviated to DESC).
• DDL related to MCP servers.
• DDL related to Postgres instances.
• DDL related to Cortex agents.

For a complete list of objects and commands that appear in your access history, see Supported Objects.

Release notes change log¶