Snowflake

What shipped

• Snowflake Data Clean Rooms updates: Snowflake Data Clean Rooms updates (18 Jun)
• Python files in Workspaces: Python files in Workspaces (General availability) (18 Jun)
• Artifacts in Snowflake CoWork: Artifacts in Snowflake CoWork (General availability) (17 Jun)
• Adaptive Compute: Adaptive Compute (General availability) (16 Jun)
• Account Usage New CORTEX_AI_GUARDRAILS_USAGE_HISTORY view: Account Usage New CORTEX_AI_GUARDRAILS_USAGE_HISTORY view (16 Jun)
• Apache Iceberg™ tables: Azure Data Lake Storage Gen2 support: Apache Iceberg™ tables: Azure Data Lake Storage Gen2 support (General availability) (12 Jun)

Why it matters

• Snowflake Data Clean Rooms updates: Governance, privacy and collaboration controls remain central to Snowflake's enterprise platform roadmap.
• Python files in Workspaces: Snowflake is smoothing application, pipeline and compute operations inside the platform.
• Artifacts in Snowflake CoWork: Snowflake is shipping incremental platform updates across data engineering, governance, AI, applications and operations.
• Adaptive Compute: Snowflake is smoothing application, pipeline and compute operations inside the platform.
• Account Usage New CORTEX_AI_GUARDRAILS_USAGE_HISTORY view: Snowflake is continuing to build Cortex and AI functionality into the data-platform workflow rather than treating AI as a separate stack.
• Apache Iceberg™ tables: Azure Data Lake Storage Gen2 support: Iceberg and open-table updates strengthen Snowflake's positioning around interoperable lakehouse architectures.

How data teams could use it

• Snowflake Data Clean Rooms updates: Security and data-governance owners should review access models, policy behaviour and audit/reporting changes before broad rollout.
• Python files in Workspaces: Analytics engineering teams can look for places where managed refresh, workspace tooling or adaptive compute reduces operational overhead.
• Artifacts in Snowflake CoWork: Platform owners should triage the release note against their roadmap, security model and workloads before enabling or adopting it.
• Adaptive Compute: Analytics engineering teams can look for places where managed refresh, workspace tooling or adaptive compute reduces operational overhead.
• Account Usage New CORTEX_AI_GUARDRAILS_USAGE_HISTORY view: Data and platform teams should assess governance, usage monitoring, cost controls and whether new AI functions can replace custom glue code.
• Apache Iceberg™ tables: Azure Data Lake Storage Gen2 support: Teams running hybrid lakehouse estates should review catalog, storage, write-support and migration implications before standardising patterns.

Editorial read

Snowflake's weekly release-note cadence shows the platform pushing in three directions at once: more AI directly inside governed data workflows, more open-table and interoperability coverage for lakehouse estates, and more operational controls for enterprise teams. The practical takeaway is to treat these updates as a backlog for platform governance: test the productivity wins, but pair them with cost visibility, access policies and rollout controls.