Releasesby GlyphOpenflow Connector for SQL Server (CDC) (General availability)
The Openflow Connector for SQL Server (CDC) is now generally available. The connector captures every row-level change from Microsoft SQL Server using Change Data Capture (CDC) and replicates selected tables into Snowflake in near real-time or on a schedule. It supports initial snapshot load, incremental sync, and schema evolution.
Also shipped Aug 5, 2026Snowflake in August 2026 →
REPLACE USING flows for pipelines (Beta)
REPLACE USING flows are now available in Lakeflow pipelines in Beta . Use a REPLACE USING flow when your source is a series of partial snapshots keyed by column. On each update, the flow replaces all rows that match the specified key columns and leaves all other rows unchanged.
The Table Visualization Improvements feature is now generally available
The Table Visualization Improvements feature is now generally available. You can now use the following features for table visualizations : Pagination Show/Hide Table Headers Table Borders Cell Highlighting Conditional formatting for string fields
More from Snowflake OpenflowEvery Snowflake Openflow release →
Second generation Openflow (Preview)
Second generation (gen 2) Openflow is now in public preview. Gen 2 makes Openflow deployments, runtimes, and connectors first-class Snowflake SQL objects with standard RBAC, SQL lifecycle management, and versioned connector configuration. Supported connectors at public preview: PostgreSQL CDC, MySQL/MariaDB CDC. Gen 2 Openflow is available on AWS and Azure.
Openflow Connector for Jira Cloud: Core flow (General availability)
The Atlassian Jira Cloud (Core) flow is now generally available. The flow ingests Jira Cloud issues, projects, users, and related data into dedicated Snowflake tables with explicit schemas. It supports optional deletion tracking and parallel ingestion across projects. The Atlassian Jira Cloud (Agile) flow remains in Public Preview .
Second generation Openflow deployments and runtimes (General availability)
Second generation (gen 2) Openflow deployment and runtime SQL objects are now generally available on AWS and Azure. Create, modify, and remove gen 2 deployments and runtimes with CREATE , ALTER , DROP , SHOW , and DESCRIBE commands, or through the Openflow UI, with standard Snowflake RBAC on schema-scoped objects.
Openflow gen 1 deployment creation retired
You can no longer create new first generation (gen 1) Openflow deployments (BYOC or Snowflake). All new deployments are second generation (gen 2), created with CREATE OPENFLOW DEPLOYMENT or the Openflow UI. Existing gen 1 deployments continue to work unchanged, and you can still create new gen 1 runtimes on an existing gen 1 deployment.
Second generation Openflow deployments and runtimes now available on GCP
Second generation (gen 2) Openflow deployment and runtime SQL objects are now available on Google Cloud Platform (GCP), in addition to AWS and Azure. Previously, gen 2 deployment and runtime SQL objects were generally available only on AWS and Azure.
Migration of gen 1 Openflow deployments and runtimes to gen 2 (General availability)
Migration of gen 1 Openflow deployments and runtimes to gen 2 is now generally available. From the Openflow UI, you can convert an existing gen 1 deployment ( OPENFLOW DATA PLANE INTEGRATION ) and all of its runtimes ( OPENFLOW RUNTIME INTEGRATION ) into gen 2 OPENFLOW DEPLOYMENT and OPENFLOW RUNTIME objects, with standard Snowflake RBAC on the resulting...
Openflow Endpoints (General availability)
With this release, Openflow endpoints are now generally available for Snowflake deployments and Bring Your Own Cloud (BYOC) deployments. You can create stable HTTPS URLs that route external HTTP requests to Listen processors in your Openflow runtimes.