Releasesby GlyphCREATE OR ALTER support for dynamic Apache Iceberg™ tables
You can now use CREATE OR ALTER DYNAMIC ICEBERG TABLE to create a dynamic Apache Iceberg™ table if it doesn’t exist or alter an existing one in place. The statement represents the complete target state: properties you don’t specify reset to their default values, and the command doesn’t trigger a refresh by itself.
Also shipped Aug 13, 2026Snowflake in August 2026 →
BigQuery pipelines add automated metadata enrichment in preview
Semantic metadata defined in SQLX configurations now syncs with Knowledge Catalog, and the Data Engineering Agent can generate this metadata from your intent or context.
Sharing tables backed by default storage will be enabled by default for all accounts
OpenSharing support for tables backed by default storage is generally available and on by default for most accounts. For most Enterprise or Premium tier accounts, Databricks will enable it automatically in mid-September 2026, and by early 2027 for the rest.
Expanded networking billing for OpenSharing SecureConnect
Databricks will be expanding networking billing for OpenSharing SecureConnect. Today, data providers are billed for data transfer (egress) when recipients access shared data through SecureConnect. Additional charge types and access scenarios, including charges billed to recipients, are planned.
OpenSharing SecureConnect will be available by default for all accounts
OpenSharing SecureConnect is generally available and available by default for accounts on the Premium plan. For accounts on the Enterprise plan, Databricks will enable it automatically in mid-September 2026, and by early 2027 for the rest.
Block or redact sensitive data in requests and responses
The Sensitive Data Detection guardrail (Beta) detects structured sensitive data (such as Social Security numbers, credit card numbers, IBANs, and phone numbers) and either blocks the interaction or redacts the matched values in place.
Smart Routing: Cut AI costs by routing each task to the right model
Smart Routing (Beta) automatically picks the right model and agent harness for each task, based on complexity, permissions, and budget. It shifts routine work to lower-cost models and reserves frontier models for hard problems, and every routing decision is visible and auditable.
More from SnowflakeEvery Snowflake release →
Snowflake Data Clean Rooms updates
Clean room UI users: New updates are applied to the UI automatically when a user starts a new session after a new update is deployed. To ensure new updates are applied, make sure to log out and log back into the UI. Clean room API users: API updates are applied either manually or automatically to an account. Learn how to manage updates for Data Clean Rooms.
New POSTGRES_COMPUTE_USAGE_HISTORY view
The ACCOUNT_USAGE and ORGANIZATION_USAGE schemas now include a new POSTGRES_COMPUTE_USAGE_HISTORY view that provides visibility into the hourly compute credit usage for Postgres instances.
Feature policy rules (General availability)
With this release, we are pleased to announce the general availability of feature policy rules. A feature policy can carry a YAML body that conditionally blocks object creation based on attributes of the request. For example, you can permit tables in general but block temporary tables, or permit tasks but block serverless (no-warehouse) tasks.
Amazon S3 Tables Iceberg REST catalog integration (General availability)
Snowflake can now connect directly to the Amazon S3 Tables Iceberg REST endpoint, so you don’t need to create an AWS Glue integration. This capability is now generally available.
Request Access in Workspaces (Preview)
With this preview release, you can resolve access-related SQL errors in Workspaces by submitting access requests directly from Snowsight. When a query fails because of missing privileges and the user can’t self-resolve the issue by switching roles, the user can submit a request with a reason.
New SNOWFLAKE_COCO_USAGE_HISTORY view in Account Usage and Organization Usage (General availability)
The SNOWFLAKE_COCO_USAGE_HISTORY view is now generally available in the ACCOUNT_USAGE and ORGANIZATION_USAGE schemas. It provides a unified view of usage history for CoCo across the CLI, Desktop, and Snowsight interfaces. The information in the view includes the number of credits consumed each time a user interacts with CoCo.
User skills in Snowflake CoWork (Preview)
User skills are now available in public preview in Snowflake CoWork. Business users can create reusable workflows conversationally, from the UI ( + menu > Skills > Create new ), or by uploading a skill folder on Capabilities > Skills , then run them explicitly with / or from the Skills menus, or implicitly when a conversation matches the skill.
Data movement policies (General availability)
With this release, data movement policies are now generally available for Enterprise Edition (or higher). Data movement policies are part of Snowflake’s data exfiltration protection controls. These SQL-style conditional policies can help you limit, alert on, or block data movement operations based on specific movement types.