SNOWFLAKE DOCS DIFF
本日は全8,515ページのうち137ページが改訂され、削除はありませんでした。重要度Aが14件、Bが24件、Cが99件で、破壊的変更はありません。更新は特に Openflow に集中し、Gen 2 の権限設計、SQLによるデプロイメント・ランタイム管理、保守手順が大きく整理されています。加えて、Delta Sharing のアクセス要件緩和や Cortex Code の Interactive Warehouses 対応も注目されます。
CREATE OPENFLOW DEPLOYMENT、CREATE OPENFLOW RUNTIME、CREATE OPENFLOW CONNECTOR によるSQLベースの構築・管理手順が拡充されました。OPENFLOW_ADMIN、専用のインフラ用データベース・スキーマ、DEFAULT_SECONDARY_ROLES = ('ALL') などの設定が示されました。snowflake-interactive バンドルスキルが追加され、Interactive Warehouses の作成・管理や診断に対応しました。新規テーブルのスナップショットを省略して即時増分レプリケーションを開始する設定の説明が削除されました。また、失敗テーブルの再レプリケーションへのリンクがメンテナンスページに移動し、前提条件の下に「Before you begin」見出しが追加されました。 影響: 該当設定の詳細はこのページから確認できなくなり、再レプリケーション手順は移動先ページを参照する必要があります。
判定根拠: SQL 構文/コードブロックの増減 (+0/-14)
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/postgres/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/postgres/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).@@ -20,69 +20,42 @@ This topic describes the steps to set up the %postgresql%. -This connector can be configured to immediately start replicating incremental changes for newly added tables,-bypassing the snapshot load phase. This option is often useful when reinstalling the connector-in an account where previously replicated data exists and you want to continue replication without having to re-snapshot tables.- For details on the incremental load process, see [Incremental replication](/user-guide/data-integration/openflow/connectors/postgres/incremental-replication).--For information about restarting table replication for failed tables, see-[Restart table replication](#label-of-postgres-restart-table-replication).+For information about restarting replication for failed tables, see [Restart table replication](/user-guide/data-integration/openflow/connectors/postgres/maintenance#label-of-postgres-restart-table-replication). ## Prerequisites++### Before you begin 1. Ensure that you have reviewed [](/user-guide/data-integration/openflow/connectors/postgres/about). 2. Ensure that you have reviewed the [supported PostgreSQL versions](#label-supported-pg-versions).-3. Ensure that you have [](/user-guide/data-integration/openflow/setup-openflow-byoc) or [Set up Openflow - Snowflake Deployments](/user-guide/data-integration/openflow/setup-openflow-spcs).-4. If using %ofsfspcs-plural%, ensure that you've reviewed [configuring required domains](/user-guide/data-integration/openflow/setup-openflow-spcs-sf-allow-list)- and have granted access to the required domains for the [](#label-openflow-domains-used-by-openflow-connectors-postgresql) connector.-5. As a database administrator, perform the following tasks:- 1. [Configure wal_level](#configure-wal-level)- 2. [Review other server settings](#label-postgres-review-server-settings)- 3. [Create a publication](#create-a-publication)- 4. Ensure that there is enough disk space on your PostgreSQL server for the WAL.- This is because once created, a replication slot causes PostgreSQL to retain the WAL data from the position held by the replication slot,- until the connector confirms and advances that position.- 5. Ensure that every table enabled for replication has one of the following identity key configurations:- - **Primary key**: The connector uses primary key columns as the identity key and requires the table's REPLICA IDENTITY to be set to `DEFAULT`.- - **Unique index (for tables without a primary key)**: Use a unique index that meets the requirements in [](#label-postgres-configure-replica-identity-using-index) as the identity key. You must run `ALTER TABLE <table_name> REPLICA IDENTITY USING INDEX <index_name>` before enabling replication.- 6. For tables without a primary key, see [](#label-postgres-configure-replica-identity-using-index).- 7. Create a user for the connector. The connector requires a user with the `REPLICATION` attribute and permissions- to SELECT from every replicated table. Create that user with a password to enter into the connector's configuration.- For more information on replication security, see [Security](https://www.postgresql.org/docs/current/logical-replication-security.html).--6. As a Snowflake account administrator, perform the following tasks:- 1. Create a Snowflake user with the type as [SERVICE](#label-user-type-property).- Create a database to store the replicated data, and set up- privileges for the Snowflake user to create objects in that database by granting the [USAGE and CREATE SCHEMA privileges](#label-database-privileges).- ```sql- CREATE DATABASE <destination_database>;- CREATE USER <openflow_user> TYPE=SERVICE COMMENT='Service user for automated access of Openflow';- CREATE ROLE <openflow_role>;- GRANT ROLE <openflow_role> TO USER <openflow_user>;- GRANT USAGE ON DATABASE <destination_database> TO ROLE <openflow_role>;- GRANT CREATE SCHEMA ON DATABASE <destination_database> TO ROLE <openflow_role>;- CREATE WAREHOUSE <openflow_warehouse>- WITH- WAREHOUSE_SIZE = 'XSMALL'- AUTO_SUSPEND = 300- AUTO_RESUME = TRUE;- GRANT USAGE, OPERATE ON WAREHOUSE <openflow_warehouse> TO ROLE <openflow_role>;- ```-- 2. Create a pair of secure keys (public and private). Store the private key for the user in a file to use while configuring the connector.- Assign the public key to the Snowflake service user:-- ```sql- ALTER USER <openflow_user> SET RSA_PUBLIC_KEY = 'thekey';- ```-- For more information, see [key-pair authentication](/user-guide/key-pair-auth).-- 3. Designate a warehouse for the connector to use. Start with the `XSMALL` warehouse size,- then experiment with size depending on the number of tables being replicated, and the amount of data- transferred. Large numbers of tables typically scale better with [multi-cluster warehouses](/user-guide/warehouses-multicluster),- rather than the warehouse size.--### Configure wal_level+3. Make sure you have an Openflow deployment and runtime for this connector. If you don't, see+ [Set up Openflow - Snowflake Deployments](/user-guide/data-integration/openflow/setup-openflow-spcs)+ or [Set up Openflow - BYOC](/user-guide/data-integration/openflow/setup-openflow-byoc).++ A runtime's size is fixed when you create it, so decide on a size before you create the runtime.+ See [](/user-guide/data-integration/openflow/connectors/cdc-runtime-sizing).++4. If using Snowflake deployments, ensure that you've reviewed [configuring required domains](/user-guide/data-integration/openflow/setup-openflow-spcs-sf-allow-list)+ and have granted access to the required domains for the [](/user-guide/data-integration/openflow/setup-openflow-spcs-sf-allow-list#label-openflow-domains-used-by-openflow-connectors-postgresql) connector.++### Source database setup++As a database administrator, perform the following tasks:++1. [Configure wal_level](#configure-wal-level)+2. [Review other server settings](#label-postgres-review-server-settings)+3. [Create a publication](#create-a-publication)+4. Ensure that there is enough disk space on your PostgreSQL server for the WAL.+ This is because once created, a replication slot causes PostgreSQL to retain the WAL data from the position held by the replication slot,+ until the connector confirms and advances that position.+5. Ensure that every table enabled for replication has one of the following identity key configurations:+ - **Primary key**: The connector uses primary key columns as the identity key and requires the table's REPLICA IDENTITY to be set to `DEFAULT`.+ - **Unique index (for tables without a primary key)**: Use a unique index that meets the requirements in [](#label-postgres-configure-replica-identity-using-index) as the identity key. You must run `ALTER TABLE <table_name> REPLICA IDENTITY USING INDEX <index... (truncated)
差分が長いため、途中まで表示しています。
見出しが「Create an Openflow deployment」「Create an Openflow runtime」に変更され、権限設定が Gen 2 と Gen 1 に分離されました。Gen 2では CREATE OPENFLOW DEPLOYMENT、CREATE DATABASE、およびスキーマ上の CREATE OPENFLOW RUNTIME／CREATE OPENFLOW CONNECTOR（後者2つはデータベース・スキーマ作成後）を付与し、Gen 1では従来の統合権限を付与します。また、default_secondary_roles の設定例が <openflow_user> の形式に変更され、利用ロールの例として openflow_admin が示されました。
影響: 管理者は世代に応じて付与する権限と対象スキーマを見直し、各ユーザーに DEFAULT_SECONDARY_ROLES = ('ALL') を設定する必要があります。
判定根拠: SQL 構文/コードブロックの増減 (+7/-4)
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-byoc+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-byoc@@ -16,6 +16,6 @@ Setting up Openflow involves the following steps: -- [Create a deployment in your cloud](#create-a-deployment-in-your-cloud)-- [Create a Runtime environment in your cloud](#create-a-runtime-environment-in-your-cloud)+- [Create an Openflow deployment](#create-an-openflow-deployment)+- [Create an Openflow runtime](#create-an-openflow-runtime) ## Prerequisites@@ -25,49 +25,62 @@ ### Snowflake account -You'll need to first define privileges at the Snowflake account level.--1. Run the following SQL commands to grant the required privileges to the Openflow admin role:-+First, grant the required privileges to the Openflow admin at the account level.++1. Run the following SQL commands to grant the required privileges to the Openflow admin.+ For help choosing a generation, see [Openflow gen 1 and gen 2](/user-guide/data-integration/openflow/gen2/openflow-generations).++ **Gen 2:** ```sql USE ROLE ACCOUNTADMIN; - GRANT CREATE OPENFLOW DATA PLANE INTEGRATION ON ACCOUNT TO ROLE $openflow_admin_role;- GRANT CREATE OPENFLOW RUNTIME INTEGRATION ON ACCOUNT TO ROLE $openflow_admin_role;+ GRANT CREATE OPENFLOW DEPLOYMENT ON ACCOUNT TO ROLE openflow_admin;+ GRANT CREATE DATABASE ON ACCOUNT TO ROLE openflow_admin;+ -- Run these two after creating the database and schema for gen 2 objects:+ -- GRANT CREATE OPENFLOW RUNTIME ON SCHEMA <db>.<schema> TO ROLE openflow_admin;+ -- GRANT CREATE OPENFLOW CONNECTOR ON SCHEMA <db>.<schema> TO ROLE openflow_admin; ``` - The new privileges are assigned to the ACCOUNTADMIN role as part of the default set of privileges, and that role can grant the privileges to a role of their choosing for the Openflow admin role, denoted as $openflow_admin_role in the code.--2. Next, set `default_secondary_roles` to `ALL` for all Openflow users:- 1. Sign in to Snowflake with a role that your ACCOUNTADMIN assigned for using Openflow.-- This may not be any of the following roles: ACCOUNTADMIN, ORGADMIN, GLOBALORGADMIN, or SECURITYADMIN.-- If you see a blank screen or the error "message: Invalid consent request" when logging into Openflow, change your role to a role that is not one of these listed roles.-- For more information, see [Prerequisites](#prerequisites).-- 2. Run the following code, replacing $openflow_user for each Openflow user:-+ **Gen 1:** ```sql USE ROLE ACCOUNTADMIN;- ALTER USER $openflow_user SET DEFAULT_SECONDARY_ROLES = ('ALL');++ GRANT CREATE OPENFLOW DATA PLANE INTEGRATION ON ACCOUNT TO ROLE openflow_admin;+ GRANT CREATE OPENFLOW RUNTIME INTEGRATION ON ACCOUNT TO ROLE openflow_admin; ``` + These privileges are assigned to the ACCOUNTADMIN role as part of the default set of privileges, and that role can grant the privileges to a role of their choosing for the Openflow admin, denoted as `openflow_admin` in the code.++2. Next, set `default_secondary_roles` to `ALL` for all Openflow users:+ 1. Sign in to Snowflake and switch to a role that your account admin has set up for using Openflow, for example `openflow_admin`.++ This may not be any of the following roles: ACCOUNTADMIN, ORGADMIN, GLOBALORGADMIN, or SECURITYADMIN.++ If you see a blank screen or the error "message: Invalid consent request" when logging into Openflow, change your role to a role that is not one of these listed roles.++ For more information, see [Prerequisites](#prerequisites).++ 2. Run the following code, replacing `<openflow_user>` for each Openflow user:++ ```sql+ USE ROLE ACCOUNTADMIN;+ ALTER USER <openflow_user> SET DEFAULT_SECONDARY_ROLES = ('ALL');+ ```+ This setting is required because Openflow actions are authorized by using any of the authenticated user's roles, and not just the default role. <a id="label-deployment-privileges"></a> -#### Deployment integration privileges--The deployment integration object represents a set of resources provisioned to deploy one or more Snowflake Openflow runtimes. For organizations bringing-their own cloud resources, the deployment integration object represents a managed Kubernetes cluster along with its associated nodes.--Users with the CREATE DATA PLANE INTEGRATION privilege on the Snowflake account can create and delete the deployment integration objects.--Additional privileges can be defined on deployment integration objects directly to support differentiation of access.--You can grant the following privileges on a deployment integration object:--- OWNERSHIP: Enables full control over deployment actions objects, including deletion of the deployment.+#### Deployment privileges++The deployment object represents a set of resources provisioned to deploy one or more Snowflake Openflow runtimes. For organizations bringing+their own cloud resources, the deployment represents a managed Kubernetes cluster along with its associated nodes.++Users with `CREATE OPENFLOW DATA PLANE INTEGRATION` (gen 1) or `CREATE OPENFLOW DEPLOYMENT` (gen 2) on the account can create deployment objects.++Additional privileges can be defined on deployment objects directly to support differentiation of access.++You can grant the following privileges on a deployment object:++- OWNERSHIP: Enables full control over deployment actions, including deletion of the deployment. - USAGE: Enables creation of runtime child objects. @@ -78,7 +91,7 @@ The runtime object represents a cluster of one or more Snowflake Openflow runtime servers, provisioned to run flow definitions. For Kubernetes deployments, the runtime object represents a stateful set of Snowflake Openflow runtime containers deployed in a namespace, along with supporting components. -Users with the OWNERSHIP privilege on the parent deployment integration object and the CREATE RUNTIME INTEGRATION account-level privilege can create runtime integration objects. Additional privileges can be defined on runtime integration objects directly to support differentiation of access.--You can grant the following privileges on a runtime integration object:+Users with the OWNERSHIP privilege on the parent deployment object and the `CREATE OPENFLOW RUNTIME INTEGRATION` (gen 1) or `CREATE OPENFLOW RUNTIME` (gen 2) privilege can create runtimes. Additional privileges can be defined on runtime objects directly.++You can grant the following privileges on a runtime object: - OWNERSHIP: Enables full control over runtime actions, including deletion of the associated runtime and modification of runtime flow definitions.@@ -139,9 +152,9 @@ Consider a scenario where the following roles should be set up: -- **accountadmin:** Out-of-the box role from Snowflake, which has these two CREATE privileges:- - CREATE OPENFLOW DATA PLANE INTEGRATION- - CREATE OPENFLOW RUNTIME INTEGRATION--- **deployment_manager:** Can create, manage, and delete deployments.+- **accountadmin:** Out-of-the box role from Snowflake, which has these CREATE privileges:+ - CREATE OPENFLOW DATA PLANE INTEGRATION (gen 1) / CREATE OPENFLOW DEPLOYMENT (gen 2)+ - CREATE OPENFLOW RUNTIME INTEGRATION (gen 1) / CREATE OPENFLOW RUNTIME (gen 2, on schema)++- **openflow_admin:** Can create, manage, and delete deployments. - **deployment1_runtime_manager_1:** Can create a runtime only within deployment 1. It can modify and delete a runtime that it created within deployment 1, but not a runtime created by deployment1_runtime_manager_2. - **deployment1_runtime_manager_2:** Can create a runtime only within deployment 1. It can modify and delete a runtime that it created within deployment 1, but not a runtime created by deployment1_runtime_manager_1.@@ -156,5 +169,5 @@ ```sql use role ACCOUNTADMIN;- create role if not exists deployment_man... (truncated)
差分が長いため、途中まで表示しています。
テーブルデータへのアクセス要件が、vended credentials 必須から、既定の vended credentials または external volume のいずれかに変更されました。CATALOG_NAME は従来の shares/ プレフィックス付きに加え、共有名のみも指定可能になりました。
影響: vended credentials 非対応の Delta Sharing サーバーでも、external volume を構成して共有テーブルへアクセスできるようになります。
判定根拠: SQL 構文/コードブロックの増減 (+9/-0)
--- ahttps://docs.snowflake.com/en/user-guide/tables-iceberg-configure-catalog-integration-delta-sharing+++ bhttps://docs.snowflake.com/en/user-guide/tables-iceberg-configure-catalog-integration-delta-sharing@@ -34,6 +34,8 @@ - **Table format must be Delta.** A Delta Sharing catalog integration supports only Delta tables (`TABLE_FORMAT = DELTA`). -- **Vended credentials are required for table access.** Snowflake uses vended credentials returned by the Delta Sharing server- to access the underlying table data in cloud storage. The Delta Sharing server must support vended credentials.+- **Table data access requires vended credentials or an external volume.** By default, Snowflake uses vended credentials+ returned by the Delta Sharing server to access the underlying table data in cloud storage. If the Delta Sharing server+ doesn't support vended credentials, you can configure an external volume that grants Snowflake direct access to the+ storage instead. See [](#label-tables-iceberg-configure-catalog-integration-delta-sharing-external-volume). ## Prerequisites@@ -108,5 +110,6 @@ - `CATALOG_URI` is the `endpoint` value from the recipient credential file. - `CATALOG_NAME` is `shares/` followed by the name of the Delta Sharing share. For example, if your share is named- `sales_share`, specify `CATALOG_NAME = 'shares/sales_share'`.+ `sales_share`, specify `CATALOG_NAME = 'shares/sales_share'`. You can also specify just the share name without the+ `shares/` prefix, for example `CATALOG_NAME = 'sales_share'`. - `BEARER_TOKEN` is the `bearerToken` value from the recipient credential file. @@ -160,5 +163,6 @@ - `CATALOG_URI` is the endpoint URL for the Delta Sharing recipient that the provider gave you.-- `CATALOG_NAME` is `shares/` followed by the name of the Delta Sharing share.+- `CATALOG_NAME` is `shares/` followed by the name of the Delta Sharing share. You can also specify just the share name+ without the `shares/` prefix. - `OIDC_AUDIENCE` is the audience value that the Delta Sharing server's OIDC recipient policy expects. @@ -248,5 +252,6 @@ - `CATALOG_URI` is the endpoint URL for the Delta Sharing recipient that the provider gave you.-- `CATALOG_NAME` is `shares/` followed by the name of the Delta Sharing share.+- `CATALOG_NAME` is `shares/` followed by the name of the Delta Sharing share. You can also specify just the share name+ without the `shares/` prefix. - `OAUTH_CLIENT_ID` and `OAUTH_CLIENT_SECRET` are the OAuth2 credentials issued by the provider's identity provider. - `OAUTH_TOKEN_URI` is the token endpoint URL of the identity provider.@@ -320,4 +325,76 @@ and [](/sql-reference/sql/create-database-catalog-linked). +<a id="label-tables-iceberg-configure-catalog-integration-delta-sharing-external-volume"></a>++## Use an external volume when the provider doesn't support credential vending++By default, a Delta Sharing catalog integration uses vended credentials (`ACCESS_DELEGATION_MODE = VENDED_CREDENTIALS`) to+access the shared table data in cloud storage. Some Delta Sharing servers don't support credential vending. For example,+servers that implement version 1 of the Delta Sharing protocol don't provide the `/temporary-table-credentials` endpoint.+Against those servers, credential vending fails and the shared tables remain uninitialized placeholders that you can't query.++In that case, you can grant Snowflake direct access to the underlying cloud storage with an+[external volume](/user-guide/tables-iceberg-configure-external-volume) instead.++1. Create the catalog integration **without** `ACCESS_DELEGATION_MODE = VENDED_CREDENTIALS`. The following example uses OAuth+ authentication, but you can use any of the supported authentication methods:++ ```sql+ USE ROLE ACCOUNTADMIN;++ CREATE OR REPLACE CATALOG INTEGRATION my_delta_sharing_int_ext_vol+ CATALOG_SOURCE = DELTA_SHARING+ TABLE_FORMAT = DELTA+ REST_CONFIG = (+ CATALOG_URI = '<recipient_endpoint>'+ CATALOG_NAME = 'shares/<share_name>'+ )+ REST_AUTHENTICATION = (+ TYPE = OAUTH+ OAUTH_CLIENT_ID = '<oauth_client_id>'+ OAUTH_CLIENT_SECRET = '<oauth_client_secret>'+ OAUTH_TOKEN_URI = 'https://<token_server_uri>'+ )+ ENABLED = TRUE;+ ```++2. Configure an external volume that grants Snowflake access to the cloud storage that backs the shared tables. For+ instructions, see [](/user-guide/tables-iceberg-configure-external-volume). Because Delta Sharing tables are read-only in+ Snowflake, the external volume doesn't need write access, so you can set `ALLOW_WRITES = FALSE`.++ The following example creates an external volume for Amazon S3:++ ```sql+ CREATE OR REPLACE EXTERNAL VOLUME iceberg_external_volume+ STORAGE_LOCATIONS = (+ (+ NAME = 'my-s3-us-west-2'+ STORAGE_PROVIDER = 'S3'+ STORAGE_BASE_URL = 's3://<my_bucket>/'+ STORAGE_AWS_ROLE_ARN = '<arn:aws:iam::123456789012:role/myrole>'+ STORAGE_AWS_EXTERNAL_ID = 'external_id'+ )+ )+ ALLOW_WRITES = FALSE;+ ```++ Set `STORAGE_BASE_URL` to the cloud storage location that backs the shared tables. If you don't know this location, the+ provider can supply it, or you can retrieve it from the base location that the Delta Sharing server returns for the share.++3. Specify the external volume with the `EXTERNAL_VOLUME` parameter when you create the catalog-linked database:++ ```sql+ CREATE OR REPLACE DATABASE delta_sharing_cld+ LINKED_CATALOG = (+ CATALOG = my_delta_sharing_int_ext_vol+ ALLOWED_WRITE_OPERATIONS = 'NONE'+ SYNC_INTERVAL_SECONDS = 30+ )+ EXTERNAL_VOLUME = 'iceberg_external_volume';+ ```++With this configuration, Snowflake uses the external volume to read the shared table data directly from cloud storage and+doesn't call the Delta Sharing server's credential-vending endpoint.+ ## Query Delta tables
Openflow の世代判定がアカウント単位で明記され、SHOW OPENFLOW DEPLOYMENTS で gen 2 対応可否を確認できるようになりました。SQL では gen 2 の CREATE OPENFLOW DEPLOYMENT 構文と DEPLOYMENT_TYPE = SNOWFLAKE、USE_PRIVATE_LINK、DISPLAY_NAME が追加され、イベントテーブル作成手順も OPENFLOW_ADMIN とインフラストラクチャスキーマを使う形に変更されています。
影響: gen 2 対応アカウントでは新規デプロイメントが自動的に gen 2 となるため、SQL 作成前に SHOW OPENFLOW DEPLOYMENTS で確認し、PrivateLink 利用時は USE_PRIVATE_LINK = TRUE を設定する必要があります。
判定根拠: SQL 構文/コードブロックの増減 (+16/-6)
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-spcs-deployment+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-spcs-deployment@@ -11,5 +11,5 @@ deployment itself; only active runtimes consume Snowflake credits. -1. [Create a deployment](#label-openflow-spcs-create-deployment) - create the deployment itself.+1. [Create a deployment](#label-openflow-spcs-create-deployment). 2. [[Optional] Configure an Openflow-specific event table](#label-openflow-spcs-event-table) - configure an Openflow-specific event table to store Openflow logs and metrics. @@ -17,4 +17,25 @@ ## Create a deployment++You can create a deployment from the Openflow UI, which works for both generations, or with SQL. The+SQL commands in this topic create gen 2 deployments.++Which generation you get is determined by your account, not by how you create the deployment. Once+your account is enabled for gen 2, every new deployment is gen 2 and you can no longer create gen 1+deployments. Existing gen 1 deployments keep working unchanged.++To check whether your account is enabled for gen 2, run the following command:++```sql+SHOW OPENFLOW DEPLOYMENTS;+```++If the command succeeds, your account is enabled for gen 2, including when it returns no rows. If it+returns a SQL error, your account isn't enabled for gen 2 and new deployments are gen 1.++For other ways to tell gen 1 and gen 2 resources apart, see+[](/user-guide/data-integration/openflow/gen2/openflow-generations#label-openflow-generations-identify).++### Using the Openflow UI To access the Openflow Runtime UI using PrivateLink as described in [Setup PrivateLink UI access](/user-guide/data-integration/openflow/setup-openflow-spcs-configure-pr-ui),@@ -31,5 +52,19 @@ 8. Select **Create Deployment**. -Your deployment will then be created.+### Using SQL (gen 2)++Gen 2 deployments are first-class Snowflake objects created with SQL:++```sql+USE ROLE OPENFLOW_ADMIN;++CREATE OPENFLOW DEPLOYMENT my_deployment+ DEPLOYMENT_TYPE = SNOWFLAKE+ -- USE_PRIVATE_LINK = TRUE, -- Enable if you need PrivateLink+ DISPLAY_NAME = 'My Snowflake Deployment';+```++For PrivateLink considerations and additional parameters, see+[Quickstart: gen 2 Openflow](/user-guide/data-integration/openflow/gen2/quickstart#create-a-gen-2-deployment). <a id="label-openflow-spcs-event-table"></a>@@ -40,31 +75,31 @@ For helpful queries to analyze this telemetry data, see [Monitor Openflow](/user-guide/data-integration/openflow/monitor). -By default, Openflow uses the [account event table](#label-logging-event-table-default) (SNOWFLAKE.TELEMETRY.EVENTS), but you can configure an Openflow-specific event table per deployment. A dedicated event table is recommended to optimize query performance, enable granular access control, and simplify Openflow monitoring and maintenance.+By default, Openflow uses the [account event table](/developer-guide/logging-tracing/event-table-setting-up#label-logging-event-table-default) (SNOWFLAKE.TELEMETRY.EVENTS), but you can configure an Openflow-specific event table per deployment. A dedicated event table is recommended to optimize query performance, enable granular access control, and simplify Openflow monitoring and maintenance. -1. To store the event table outside the Openflow database, grant the OPENFLOW_ADMIN role- access to the `` and `` where you want to store it:+1. Create the event table in the Openflow infrastructure schema: ```sql- USE ROLE ACCOUNTADMIN;+ USE ROLE OPENFLOW_ADMIN;+ USE DATABASE <openflow_db>;+ USE SCHEMA <openflow_schema>; - GRANT USAGE ON DATABASE TO ROLE OPENFLOW_ADMIN;- GRANT USAGE ON SCHEMA . TO ROLE OPENFLOW_ADMIN;+ CREATE EVENT TABLE IF NOT EXISTS <openflow_db>.<openflow_schema>.openflow_events; ``` -2. Create the event table:+2. Get your deployment name and set the event table:++ **Gen 2:** ```sql- USE ROLE OPENFLOW_ADMIN;+ SHOW OPENFLOW DEPLOYMENTS; - CREATE EVENT TABLE IF NOT EXISTS ..EVENTS;+ ALTER OPENFLOW DEPLOYMENT <deployment_name>+ SET EVENT_TABLE = '<openflow_db>.<openflow_schema>.openflow_events'; ``` -3. Get your dataplane name, which you use in the next step, from the `name` column:+ **Gen 1:** ```sql SHOW OPENFLOW DATA PLANE INTEGRATIONS;- ``` -4. Set the event table for this deployment, replacing `<OPENFLOW_DATAPLANE_INTEGRATION_NAME>` with the value from the previous step:- ```sql ALTER OPENFLOW DATA PLANE INTEGRATION <OPENFLOW_DATAPLANE_INTEGRATION_NAME>- SET EVENT_TABLE = '..EVENTS';+ SET EVENT_TABLE = '<openflow_db>.<openflow_schema>.openflow_events'; ``` @@ -76,16 +111,22 @@ - To create a monitoring role, run the following code:++ **Gen 1:** ```sql USE ROLE OPENFLOW_ADMIN; - -- Create a role for monitoring Openflow deployments and runtimes if it doesn't yet exist CREATE ROLE IF NOT EXISTS <OPENFLOW_MONITOR_ROLE>;+ GRANT MONITOR ON INTEGRATION <OPENFLOW_DATAPLANE_INTEGRATION_NAME> TO ROLE <OPENFLOW_MONITOR_ROLE>;+ GRANT ROLE <OPENFLOW_MONITOR_ROLE> TO ROLE <OPENFLOW_ADMIN_ROLE>;+ GRANT ROLE <OPENFLOW_MONITOR_ROLE> TO USER <SNOWFLAKE_USER>;+ ``` - GRANT MONITOR ON INTEGRATION <OPENFLOW_DATAPLANE_INTEGRATION_NAME> TO ROLE <OPENFLOW_MONITOR_ROLE>;+ **Gen 2:**+ ```sql+ USE ROLE OPENFLOW_ADMIN; - -- Add to role hierarchy so administrators can manage objects owned by this role+ CREATE ROLE IF NOT EXISTS <OPENFLOW_MONITOR_ROLE>;+ GRANT MONITOR ON OPENFLOW DEPLOYMENT <deployment_name> TO ROLE <OPENFLOW_MONITOR_ROLE>; GRANT ROLE <OPENFLOW_MONITOR_ROLE> TO ROLE <OPENFLOW_ADMIN_ROLE>;-- -- Grant the role to the appropriate Snowflake users GRANT ROLE <OPENFLOW_MONITOR_ROLE> TO USER <SNOWFLAKE_USER>; ```@@ -93,3 +134,3 @@ ### Next steps -[Create execute-as role](/user-guide/data-integration/openflow/setup-openflow-spcs-create-rr)+[Create the execute-as role and external access integrations](/user-guide/data-integration/openflow/setup-openflow-spcs-create-rr)
PostgreSQL レプリカサーバーからのテーブル複製に関する説明が追加され、hot standby replica または subscriber server からの論理レプリケーションをサポートする条件として、PostgreSQL 16 以上が必要と明記されました（Amazon Aurora は非対応）。また、管理者の役割分担が Openflow administrator／data engineer に整理され、Runtime sizing の参照先が共通ページへ変更されました。 影響: レプリカ接続を構成する場合は PostgreSQL 16 以上を使用し、事前にプライマリとレプリカ間の複製およびレプリカ上のデータ存在を確認する必要があります。
判定根拠: SQL 構文/コードブロックの増減 (+3/-0)
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/postgres/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/postgres/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).@@ -126,5 +126,5 @@ ## Openflow requirements -- Choose the runtime size based on the sustained replication workload. For sizing guidance and how to run multiple connectors on one runtime, see [Runtime sizing](#label-postgres-runtime-sizing).+- Choose the runtime size based on the sustained replication workload. For sizing guidance and how to run multiple connectors on one runtime, see [Runtime sizing](/user-guide/data-integration/openflow/connectors/cdc-runtime-sizing). - The connector doesn't support multi-node Openflow runtimes. Configure the runtime for this connector with **Min nodes** and **Max nodes** set to `1`. @@ -153,9 +153,11 @@ 1. A **Database administrator** configures PostgreSQL replication settings, creates a publication, and credentials for the connector. Optionally, they deliver the SSL certificate.-2. A **Snowflake account administrator** performs the following tasks:- 1. Creates a service user for the connector, a warehouse for the connector, and a destination database to replicate into.- 2. Installs the connector.- 3. Specifies the required parameters for the flow template.- 4. Runs the flow. The connector performs the following tasks when run in Openflow:+2. An **Openflow administrator** creates a warehouse for the connector and a destination database+ to replicate into.++3. An **Openflow administrator** or a **data engineer** performs the following tasks:+ 1. Installs the connector.+ 2. Specifies the required parameters for the flow template.+ 3. Runs the flow. The connector performs the following tasks when run in Openflow: 1. Creates a schema for journal tables. 2. Creates the schemas and destination tables matching the source tables configured for replication.@@ -229,4 +231,60 @@ The same soft-delete mechanism applies when you change a table's Column Filter JSON. For details, see [Replicate a subset of columns in a table](#label-postgres-connector-replication-subset-of-columns).++<a id="label-replicate-tables-from-postgres-replica"></a>++### Replicate tables from a PostgreSQL replica server++The connector can ingest data from a primary server, a [hot standby replica](https://www.postgresql.org/docs/current/hot-standby.html),+or subscriber server using [logical replication](https://www.postgresql.org/docs/current/logical-replication.html).+Before configuring the connector to connect to a PostgreSQL replica, ensure that replication between primary and replica+nodes works correctly. When investigating issues with missing data in the connector, first ensure that missing rows are+present in the replica server used by the connector.++Additional considerations when connecting to a standby replica:++<blockquote>++- PostgreSQL version of the server must be >= 16. Amazon Aurora is not supported because it [doesn't offer logical decoding from read replicas](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraPostgreSQL.Replication.Logical.html).+- Only connecting to a hot standby replica is supported. Note that warm standby replicas can't accept connections+ from clients until they are promoted to a primary instance.+- [The publication](#label-postgres-connector-create-a-publication) needed by the connector must be created on+ the primary server, not the standby server. The standby server is read-only and doesn't let you create a publication.++</blockquote>++If you connect to a hot standby instance and see+**Trying to create the replication slot '<replication slot>' timed out. If connecting to a standby instance, ensure there is some traffic on the primary PostgreSQL instance, otherwise the call to create a replication slot will never return.**+error in the Openflow bulletin, or the **Read PostgreSQL CDC Stream** processor isn't starting, log in to the primary PostgreSQL instance and+execute the following query:++```sqlsyntax+SELECT pg_log_standby_snapshot();+```++The error occurs when there are no data changes in the primary server. As such, the connector can stall while+creating a replication slot on the replica server. This results from the replica server requiring information about+running transactions from the primary server to be able to create a replication slot. Primary servers won't send the+information while idle. The `pg_log_standby_snapshot()` function forces the primary server to send information+about running transactions to the replica server.++On PostgreSQL 17 and later, if you want the replication slot to survive a primary failover, the connector must connect to the primary rather than a standby. See [PostgreSQL 17+ failover slot support](/user-guide/data-integration/openflow/connectors/postgres/failover).++### Track data changes in tables++The connector replicates not only the current state of data from the source tables, but also every+state of every row from every changeset. This data is stored in journal tables created in the same+schema as the destination table.++The journal table names are formatted as `<source_table_name>_JOURNAL_<timestamp>_<schema_generation>`,+where `<timestamp>` is the value of epoch seconds when the source table was added to replication, and+`<schema_generation>` is an integer increasing with every schema change on the source table. As a+result, source tables that undergo schema changes will have multiple journal tables.++When a table is removed from replication, then added back, the `<timestamp>` value will change, and+`<schema_generation>` will start again from `1`.++Snowflake recommends that you don't alter the structure of journal tables in any way. They are used+by the connector to update the destination table as part of the replication process. <a id="label-postgres-replication-key-selection"></a>@@ -355,5 +413,5 @@ - **Snapshot load**: The rejected row is written to the destination table's error table.-- **Incremental (CDC) load**: The rejected row is written to the journal table's error table, because CDC changes are first written to the journal table. For more information about journal tables, see [](/user-guide/data-integration/openflow/connectors/postgres/setup#track-data-changes-in-tables).+- **Incremental (CDC) load**: The rejected row is written to the journal table's error table, because CDC changes are first written to the journal table. For more information about journal tables, see [](#track-data-changes-in-tables). The connector enables error logging only on tables that it creates after you select **Log Errors and Continue**. To capture rejected rows for tables that were already being replicated, enable error logging on their existing destination and journal tables with the stored procedure in [Enable error logging on an existing schema](/user-guide/data-integration/openflow/connectors/postgres/maintenance#label-of-postgres-enable-error-logging-existing-schema).
Gen 2 privileges セクションが追加され、CREATE OPENFLOW DEPLOYMENT、CREATE DATABASE、CREATE INTEGRATION、CREATE OPENFLOW RUNTIME/CONNECTOR などの権限付与、インフラ用データベース・スキーマの作成手順が示されました。Gen 1 privileges には GRANT CREATE INTEGRATION ON ACCOUNT が追加されました。
影響: Gen 2 のセットアップでは専用のインフラ用データベース・スキーマが必要になり、コネクタの書き込み先とは分離して権限とオブジェクトを準備する必要があります。
判定根拠: SQL 構文/コードブロックの増減 (+15/-0)
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-spcs-sf+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-spcs-sf@@ -50,8 +50,63 @@ ## Configure required privileges -Openflow requires defining specific Snowflake Account level privileges.+Openflow requires defining specific Snowflake account-level privileges. These privileges are assigned to the ACCOUNTADMIN role as part of the default set of privileges. ACCOUNTADMIN will automatically have the following privileges and will be able to grant them-to a role of their choosing for the Openflow admin role, shown as `OPENFLOW_ADMIN` role in the following example:+to a role of their choosing for the Openflow admin role, shown as `OPENFLOW_ADMIN` role in the following examples.++### Gen 2 privileges++Gen 2 deployments are account-level objects, while runtimes and connectors are schema-level objects.+That means gen 2 needs a database and schema of its own to hold them.++1. Grant the Openflow admin role the account-level privileges it needs:++ ```sql+ USE ROLE ACCOUNTADMIN;++ GRANT CREATE OPENFLOW DEPLOYMENT ON ACCOUNT TO ROLE OPENFLOW_ADMIN;+ GRANT CREATE DATABASE ON ACCOUNT TO ROLE OPENFLOW_ADMIN;+ GRANT CREATE INTEGRATION ON ACCOUNT TO ROLE OPENFLOW_ADMIN;++ -- Snowflake deployments only:+ GRANT CREATE COMPUTE POOL ON ACCOUNT TO ROLE OPENFLOW_ADMIN;+ ```++2. Create the database and schema that will hold your gen 2 Openflow objects:++ ```sql+ USE ROLE OPENFLOW_ADMIN;++ CREATE DATABASE IF NOT EXISTS openflow_db;+ CREATE SCHEMA IF NOT EXISTS openflow_db.openflow_schema;+ ```++ This is your Openflow **infrastructure database and schema**, also referred to as the control+ schema. Your deployments' runtimes, your connectors, and any secrets those connectors reference+ live here. You create it once and reuse it.+++ Keep the infrastructure database separate from the databases your connectors write data to.+ Snowflake recommends a dedicated destination database per connector.++ A connector creates destination schemas and tables named after the source's schemas and tables.+ Those names aren't under your control and can change as the source changes, so pointing a+ connector at your infrastructure database risks collisions with the Openflow objects that live+ there.+++3. Grant the Openflow admin role the ability to create gen 2 objects in that schema:++ ```sql+ USE ROLE ACCOUNTADMIN;++ GRANT CREATE OPENFLOW RUNTIME ON SCHEMA openflow_db.openflow_schema TO ROLE OPENFLOW_ADMIN;+ GRANT CREATE OPENFLOW CONNECTOR ON SCHEMA openflow_db.openflow_schema TO ROLE OPENFLOW_ADMIN;+ ```++For the full gen 2 setup workflow, see+[Quickstart: gen 2 Openflow](/user-guide/data-integration/openflow/gen2/quickstart).++### Gen 1 privileges ```sql@@ -60,4 +115,5 @@ GRANT CREATE OPENFLOW DATA PLANE INTEGRATION ON ACCOUNT TO ROLE OPENFLOW_ADMIN; GRANT CREATE OPENFLOW RUNTIME INTEGRATION ON ACCOUNT TO ROLE OPENFLOW_ADMIN;+GRANT CREATE INTEGRATION ON ACCOUNT TO ROLE OPENFLOW_ADMIN; GRANT CREATE COMPUTE POOL ON ACCOUNT TO ROLE OPENFLOW_ADMIN; ```
ジャーナルテーブルのストレージ回収手順が追加され、全テーブルの truncate、複製対象から外したテーブルの削除、現行世代以外のジャーナルテーブル削除が可能と明記されました。また、コネクタ停止・削除時の PostgreSQL replication slot の扱いと、停止中は WAL が増大する注意点が追加され、ランタイムサイズの参照先も変更されています。 影響: 長時間の一時停止を避け、不要なジャーナルテーブルを整理するとともに、コネクタ削除時の replication slot の後処理が必要ですが、diff からは削除時の具体的な手順は詳細不明です。
判定根拠: SQL 構文/コードブロックの増減 (+2/-0)
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/postgres/maintenance+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/postgres/maintenance@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).@@ -139,5 +139,5 @@ Raising the per-value limit increases the amount of data that the connector loads into memory and moves through the flow, which raises the load on both the runtime and the warehouse. Size the runtime and warehouse accordingly. -During both snapshot and incremental replication, the queue in front of the **Upload Rows via Snowpipe Streaming 2** processor can fill with FlowFiles and trigger back pressure, which consumes a large amount of runtime disk space. For larger tables, use a Large runtime to provide additional storage. For guidance on choosing a size, see [Runtime sizing](/user-guide/data-integration/openflow/connectors/postgres/setup#label-postgres-runtime-sizing).+During both snapshot and incremental replication, the queue in front of the **Upload Rows via Snowpipe Streaming 2** processor can fill with FlowFiles and trigger back pressure, which consumes a large amount of runtime disk space. For larger tables, use a Large runtime to provide additional storage. For guidance on choosing a size, see [Runtime sizing](/user-guide/data-integration/openflow/connectors/cdc-runtime-sizing#label-openflow-cdc-runtime-sizing). #### Snapshot replication@@ -355,4 +355,43 @@ <a id="label-postgres-reinstall-connector"></a> +## Reclaim journal table storage++Journal tables hold every change to a replicated table. The connector never drops them, but it only+reads the latest journal for each replicated source table, using append-only streams on top of the+journals. To reclaim storage, you can:++- Truncate all journal tables at any time.+- Drop the journal tables related to source tables that were removed from replication.+- Drop all but the latest generation journal tables for actively replicated tables.++For example, if your connector is set to actively replicate source table `orders`, and you have+earlier removed table `customers` from replication, you may have the following journal tables. In+this case you can drop all of them *except* `orders_5678_2`.++```text+customers_1234_1+customers_1234_2+orders_5678_1+orders_5678_2+```++## Stop or delete the connector++When stopping or removing the connector, you have to consider the [replication slot](https://www.postgresql.org/docs/current/warm-standby.html#STREAMING-REPLICATION-SLOTS) that the connector uses.++The connector creates its own replication slot with a name starting with+`snowflake_connector_` followed by a random suffix. As the connector reads the replication stream,+it advances the slot, so that PostgreSQL can trim its WAL log and free up disk space.++When the connector is paused, the slot isn't advanced, and changes to the source database keep increasing the WAL+log size. You should not keep the connector paused for extended periods of time, especially on high-traffic databases.++When the connector is removed, whether by dropping it with `DROP OPENFLOW CONNECTOR` (gen 2), deleting it from the Openflow canvas,+or any other means, such as deleting the whole Openflow instance, the replication slot remains in place, and must be dropped manually.++If you have multiple connector instances replicating from the same PostgreSQL database,+each instance will create its own uniquely named replication slot. When dropping a replication slot manually, make sure+it's the right one. You can see which replication slot is used by a given connector instance by checking the state of the `CaptureChangePostgreSQL` processor.+ ## Reinstall the connector
Openflow UI に加え、gen 2 ランタイムを SQL で作成する手順が追加され、CREATE OPENFLOW RUNTIME と NODE_TYPE、MIN_NODES、MAX_NODES、EXECUTE_AS_ROLE、EXTERNAL_ACCESS_INTEGRATIONS などの指定例が示されました。ランタイムの監視権限付与も、Gen 2 はスキーマレベルのオブジェクト、Gen 1 はデータプレーン統合として、世代別の SQL に分けられました。
影響: Gen 2 ランタイムを SQL で作成・監視できるようになり、ノードサイズやノード数の選定時にはランタイムサイジングガイダンスを参照する必要があります。
判定根拠: SQL 構文/コードブロックの増減 (+6/-1)
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-spcs-create-runtime+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-spcs-create-runtime@@ -12,4 +12,9 @@ A runtime hosts your data integration flows within a deployment: connectors and custom flow definitions. Each runtime is isolated for security and resource control, and can scale from one node up to fifty to handle varying data volumes.++You can create a runtime from the Openflow UI, which works for both generations, or with SQL. The+SQL commands in this topic create gen 2 runtimes.++### Using the Openflow UI To create a runtime in your Snowflake deployment:@@ -44,5 +49,5 @@ <tr> <td>**Node Type**</td>- <td>Choose a node type from the **Node type** drop-down list. This specifies the size of your nodes.</td>+ <td>Choose a node type from the **Node type** drop-down list. This specifies the size of your nodes. For guidance on choosing a size and node count, see [](/user-guide/data-integration/openflow/connectors/cdc-runtime-sizing).</td> </tr> <tr>@@ -69,6 +74,27 @@ 6. Select **Create**. The runtime takes a couple of minutes to be created. -Once created, view your runtime by navigating to the **Runtimes** tab of the Openflow control plane.-Select the runtime to open the Openflow canvas.+Your runtime will appear in the runtime table in the control plane.++### Using SQL (gen 2)++Gen 2 runtimes are schema-level objects created with SQL:++```sql+USE ROLE OPENFLOW_ADMIN;+USE DATABASE openflow_db;+USE SCHEMA openflow_schema;++CREATE OPENFLOW RUNTIME my_runtime+ IN DEPLOYMENT my_deployment+ NODE_TYPE = MEDIUM+ MIN_NODES = 1+ MAX_NODES = 1+ EXECUTE_AS_ROLE = openflow_execute_as_rl+ EXTERNAL_ACCESS_INTEGRATIONS = (my_eai)+ DISPLAY_NAME = 'My Runtime';+```++For the full gen 2 workflow, see+[Quickstart: gen 2 Openflow](/user-guide/data-integration/openflow/gen2/quickstart#label-openflow-gen2-quickstart-runtime). ## [Optional] Grant MONITOR privileges on the runtime@@ -76,5 +102,14 @@ If you created a [monitoring role](#label-openflow-spcs-monitoring-role) when setting up your deployment, you can add the runtime to that role. This allows data engineers or operations teams to monitor the runtime without having the OPENFLOW_ADMIN role. -- To add the runtime to the monitoring role, run the following code, replacing `<OPENFLOW_RUNTIME_INTEGRATION_NAME>` with the name of the Openflow runtime integration:+- To add the runtime to the monitoring role, run the code for your generation:++ **Gen 2** (runtimes are schema-level objects):+ ```sql+ USE ROLE OPENFLOW_ADMIN;++ GRANT MONITOR ON OPENFLOW RUNTIME <openflow_db>.<openflow_schema>.<runtime_name> TO ROLE <OPENFLOW_MONITOR_ROLE>;+ ```++ **Gen 1** (runtimes are data plane integrations): ```sql USE ROLE OPENFLOW_ADMIN;
管理タスクの一覧が追加され、Gen 2 では DROP OPENFLOW DEPLOYMENT 構文（DROP OPENFLOW DEPLOYMENT my_deployment;）でデプロイメントを削除できるようになりました。アップグレード方針が明確化され、Snowflake deployments は自動更新、BYOC は手動更新となり、コネクター更新の説明対象が Gen 1 に限定されました。
影響: Snowflake deployments は手動アップグレード不要となる一方、BYOC deployments は UI または deployment agent script による更新計画が必要です。
判定根拠: SQL 構文/コードブロックの増減 (+3/-0)
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/manage+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/manage@@ -14,5 +14,12 @@ - [](/user-guide/data-integration/openflow/connectors/about-openflow-connectors) -This topic describes the steps to manage Openflow components.+This topic covers the following management tasks:++- [Back up flow definitions and protect runtime state](#back-up-flow-definitions-and-protect-runtime-state)+- [Runtime availability and autoscaling behavior](#runtime-availability-and-autoscaling-behavior)+- [Delete a deployment](#delete-a-deployment)+- [Upgrade a deployment](#upgrade-a-deployment)+- [Upgrade a runtime](#upgrade-a-runtime)+- [Upgrade a connector](#upgrade-a-connector) <a id="label-openflow-backup-flow-definitions"></a>@@ -130,5 +137,11 @@ have been removed and you no longer need the deployment configuration. -From the AWS Console:+**Gen 2 (SQL):** Drop the deployment directly:++```sql+DROP OPENFLOW DEPLOYMENT my_deployment;+```++**Gen 1 BYOC (AWS Console):** 1. Navigate to EC2 Instances.@@ -164,11 +177,20 @@ A deployment includes several components: the agent, deployment service, deployment UI,-runtime gateway, and runtime operator. You can upgrade via the UI or, for BYOC deployments,-via the deployment agent script. For details on what's included in each release, see+runtime gateway, and runtime operator. For details on what's included in each release, see [Openflow version history](/user-guide/data-integration/openflow/version-history). -Only the owner of a deployment can perform an upgrade.+**Snowflake deployments** are upgraded automatically by Snowflake on a rolling basis. If your+deployment is on an older version, it will be upgraded to the latest version automatically;+you do not need to initiate the upgrade yourself. Once a deployment has been upgraded to a+recent version, it will continue to receive automatic upgrades going forward.++**BYOC deployments** are not upgraded automatically. You determine upgrade timing and+frequency using the [deployment agent script](#upgrade-via-the-deployment-agent-byoc) or the+[UI](#upgrade-from-the-ui). ### Upgrade from the UI++The UI upgrade path applies to BYOC deployments. Snowflake deployments are upgraded+automatically and do not require manual intervention. 1. Sign in to %sf-web-interface-link%.@@ -307,4 +329,7 @@ processing logic is improved, or new processor versions are used–for example, to add support for a new source API version. +This section describes upgrading **gen 1** connectors on the runtime canvas. For gen 2 connectors,+see [](/user-guide/data-integration/openflow/gen2/manage-connector-lifecycle).+ When connector updates are available, you will see an **Upgrade** icon in your process group on the canvas.
Gen 2 が新規セットアップに推奨と明記され、デプロイメント作成に CREATE OPENFLOW DEPLOYMENT、ランタイム作成に CREATE OPENFLOW RUNTIME、コネクター作成に CREATE OPENFLOW CONNECTOR またはセットアップウィザードを利用できるよう整理されました。Gen 1 は従来どおり UI を使用し、実施頻度もデプロイメント作成は通常一度、ロールとランタイム作成はランタイムごとに繰り返す形に明確化されています。
影響: 新規構築では Gen 2 と SQL ベースの手順を優先し、Gen 1 利用時は UI 操作とコネクターのランタイムキャンバスからのインストールが必要です。
判定根拠: SQL 構文/コードブロックの増減 (+2/-0)
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-spcs+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-spcs@@ -11,4 +11,8 @@ To setup an %ofsfspcs%, perform the following tasks:++**Gen 2 is recommended for new setups.** The steps below cover both generations. New to+gen 2? See the [gen 2 Openflow quickstart](/user-guide/data-integration/openflow/gen2/quickstart)+for a streamlined SQL-first walkthrough. <div className="colwidths-given">@@ -52,6 +56,7 @@ After configuring core Snowflake, you then create an Openflow deployment.+Gen 2 uses `CREATE OPENFLOW DEPLOYMENT` (SQL); gen 1 uses the Openflow UI. -Optionally, configure a Openflow-specific event table to store Openflow logs and metrics.+Optionally, configure an Openflow-specific event table to store Openflow logs and metrics. </td>@@ -60,6 +65,12 @@ <tr> <td>4</td>- <td>[Create execute-as role](/user-guide/data-integration/openflow/setup-openflow-spcs-create-rr)</td>- <td>After creating an %ofsfspcs%, you must create an execute-as role and associated external access integrations.</td>+ <td>[Create the execute-as role and external access integrations](/user-guide/data-integration/openflow/setup-openflow-spcs-create-rr)</td>+ <td>++Create the role that connectors use to access Snowflake resources.+This is called the execute-as role.+Both require external access integrations for Snowflake deployments.++</td> <td>Data engineer</td> </tr>@@ -67,5 +78,10 @@ <td>5</td> <td>[Create runtime](/user-guide/data-integration/openflow/setup-openflow-spcs-create-runtime)</td>- <td>Create a runtime associated with the previously created execute-as role.</td>+ <td>++Create a runtime associated with the previously created role.+Gen 2 uses `CREATE OPENFLOW RUNTIME` (SQL); gen 1 uses the Openflow UI.++</td> <td>Data engineer</td> </tr>@@ -79,5 +95,11 @@ <td>7</td> <td>[Connect your data sources using Openflow connectors](/user-guide/data-integration/openflow/connectors/about-openflow-connectors)</td>- <td>Configure one or more connectors in the %ofsfspcs%.</td>+ <td>++Configure one or more connectors in the %ofsfspcs%. Gen 2 connectors can be created with SQL+(`CREATE OPENFLOW CONNECTOR`) or the [setup wizard](/user-guide/data-integration/openflow/gen2/setup-connector-wizard).+Gen 1 connectors are installed from the catalog on the runtime canvas.++</td> <td>Data engineer</td> </tr>@@ -86,5 +108,5 @@ </div> -Note that steps 3, 4 and 5 are typically repeated for each connector you want to configure in a given deployment.+Note that step 3 (deployment creation) is typically done once. Steps 4 and 5 (role and runtime creation) are repeated for each runtime you add to the deployment. ## Next steps
各 SQL 例で使用するロールが SECURITYADMIN から OPENFLOW_ADMIN に変更され、ネットワークルール操作時には USE DATABASE <openflow_db> と USE SCHEMA <openflow_schema> が追加されました。さらに、既存の EAI にネットワークルールを追加するため、ALTER EXTERNAL ACCESS INTEGRATION と ALLOWED_NETWORK_RULES を使う手順が新設され、既存ルールの確認方法も示されました。
影響: Openflow の設定・更新では OPENFLOW_ADMIN と対象データベース／スキーマの指定が必要になり、既存 EAI の変更時は既存ルールを確認して ALLOWED_NETWORK_RULES に併記する運用が必要です。
判定根拠: SQL 構文/コードブロックの増減 (+3/-0)
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-spcs-sf-allow-list+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-spcs-sf-allow-list@@ -34,5 +34,7 @@ ```sql-USE ROLE SECURITYADMIN;+USE ROLE OPENFLOW_ADMIN;+USE DATABASE <openflow_db>;+USE SCHEMA <openflow_schema>; CREATE NETWORK RULE MY_OPENFLOW_NETWORK_RULE@@ -45,5 +47,7 @@ ```sql-USE ROLE SECURITYADMIN;+USE ROLE OPENFLOW_ADMIN;+USE DATABASE <openflow_db>;+USE SCHEMA <openflow_schema>; CREATE NETWORK RULE GOOGLEADS_OPENFLOW_NETWORK_RULE@@ -60,5 +64,5 @@ ```sql-USE ROLE SECURITYADMIN;+USE ROLE OPENFLOW_ADMIN; CREATE EXTERNAL ACCESS INTEGRATION MY_OPENFLOW_EAI@@ -76,5 +80,7 @@ ```sql-USE ROLE SECURITYADMIN;+USE ROLE OPENFLOW_ADMIN;+USE DATABASE <openflow_db>;+USE SCHEMA <openflow_schema>; ALTER NETWORK RULE GOOGLEADS_OPENFLOW_NETWORK_RULE SET@@ -90,4 +96,19 @@ If you do not have an external access integration for the altered network rule, refer to the section above for instructions on creating a new integration.++## Alter an existing external access integration++To add a network rule to an existing external access integration, first check+which network rules the EAI already allows, then add the new rule alongside them:++```sql+USE ROLE OPENFLOW_ADMIN;++ALTER EXTERNAL ACCESS INTEGRATION <eai_name> SET+ ALLOWED_NETWORK_RULES = (<existing_network_rules>, <new_network_rule>);+```++Use [](/sql-reference/sql/desc-external-access-integration) to see which network+rules an EAI already references. ## Next steps
ジャーナルテーブルのストレージ回収セクションが追加され、TRUNCATE、不要な世代・レプリケーション対象外テーブルの削除による容量回収方法と具体例が示されました。また、ランタイムサイズ案内のリンク先が MySQL 固有ページから共通の CDC ランタイムサイジングページに変更され、デプロイ方式の説明順も入れ替えられました。
影響: 運用時に不要なジャーナルテーブルを整理してストレージを回収できるようになり、ランタイムサイズの参照先も共通ガイダンスへ変わります。
判定根拠: SQL 構文/コードブロックの増減 (+2/-0)
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/mysql/maintenance+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/mysql/maintenance@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).@@ -140,5 +140,5 @@ Raising the per-value limit increases the amount of data that the connector loads into memory and moves through the flow, which raises the load on both the runtime and the warehouse. Size the runtime and warehouse accordingly. -During both snapshot and incremental replication, the queue in front of the **Upload Rows via Snowpipe Streaming 2** processor can fill with FlowFiles and trigger back pressure, which consumes a large amount of runtime disk space. For larger tables, use a Large runtime to provide additional storage. For guidance on choosing a size, see [Runtime sizing](/user-guide/data-integration/openflow/connectors/mysql/setup#label-mysql-runtime-sizing).+During both snapshot and incremental replication, the queue in front of the **Upload Rows via Snowpipe Streaming 2** processor can fill with FlowFiles and trigger back pressure, which consumes a large amount of runtime disk space. For larger tables, use a Large runtime to provide additional storage. For guidance on choosing a size, see [Runtime sizing](/user-guide/data-integration/openflow/connectors/cdc-runtime-sizing#label-openflow-cdc-runtime-sizing). #### Snapshot replication@@ -281,4 +281,25 @@ <a id="label-mysql-reinstall-connector"></a> +## Reclaim journal table storage++Journal tables hold every change to a replicated table. The connector never drops them, but it only+reads the latest journal for each replicated source table, using append-only streams on top of the+journals. To reclaim storage, you can:++- Truncate all journal tables at any time.+- Drop the journal tables related to source tables that were removed from replication.+- Drop all but the latest generation journal tables for actively replicated tables.++For example, if your connector is set to actively replicate source table `orders`, and you have+earlier removed table `customers` from replication, you may have the following journal tables. In+this case you can drop all of them *except* `orders_5678_2`.++```text+customers_1234_1+customers_1234_2+orders_5678_1+orders_5678_2+```+ ## Reinstall the connector
snowflake-interactive バンドルスキルが追加され、Interactive Warehouses の作成・管理に対応しました。既存テーブルへのゼロコピークエリや interactive tables の作成、TARGET_LAG・クラスタリングキーの設定、フォールバックウェアハウスの構成、クエリータイムアウトなどの診断が可能になると記載されています。
影響: Interactive Warehouses を利用するユーザーは、低レイテンシー・高同時実行 workloads 向けの構成やトラブルシューティングを CoCo CLI から行えるようになります。
判定根拠: SQL 構文/コードブロックの増減 (+1/-0)
--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/bundled-skills+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/bundled-skills@@ -83,4 +83,18 @@ - Modify warehouse properties such as size, type, and scaling settings - Get recommendations for optimal Adaptive warehouse settings based on your workload++<a id="label-bundled-skill-snowflake-interactive"></a>++### `snowflake-interactive`++Create and manage [Interactive Warehouses](/user-guide/interactive) for low-latency, high-concurrency workloads: sub-second dashboards, API backends, and agentic queries.+Interactive warehouses works on any table type: standard, iceberg, dynamic, hybrid and interactive tables.++Ways to use it:++- Get started with interactive analytics and choose the right path: zero-copy queries on existing tables or purpose-built interactive tables+- Create static or dynamic interactive tables with optimal clustering keys and TARGET_LAG settings+- Create and configure interactive warehouses, associate tables, and set up a fallback warehouse for mixed workloads+- Diagnose interactive query timeouts, cache warming issues, and fallback warehouse behavior <a id="label-bundled-skill-workload-performance-analysis"></a>
Gen 2 privilegesとして、CREATE OPENFLOW DEPLOYMENT、CREATE DATABASE、CREATE INTEGRATION の付与例が追加され、従来の権限に代えて、または追加して使用できることが示されました。従来の権限はGen 1 privilegesとして明示され、CREATE INTEGRATION の付与も追加されています。
影響: Openflow 管理者の設定時に、環境に応じて Gen 2 権限を付与する選択肢が増え、従来の Gen 1 権限との扱いを確認する必要があります。
判定根拠: SQL 構文/コードブロックの増減 (+1/-0)
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-roles-login+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-roles-login@@ -30,8 +30,17 @@ GRANT CREATE ROLE ON ACCOUNT TO ROLE OPENFLOW_ADMIN; + -- Gen 2 privileges (instead of, or in addition to, the gen 1 grants below):+ -- GRANT CREATE OPENFLOW DEPLOYMENT ON ACCOUNT TO ROLE OPENFLOW_ADMIN;+ -- GRANT CREATE DATABASE ON ACCOUNT TO ROLE OPENFLOW_ADMIN;+ -- GRANT CREATE INTEGRATION ON ACCOUNT TO ROLE OPENFLOW_ADMIN;++ -- Gen 1 privileges: GRANT CREATE OPENFLOW DATA PLANE INTEGRATION ON ACCOUNT TO ROLE OPENFLOW_ADMIN; GRANT CREATE OPENFLOW RUNTIME INTEGRATION ON ACCOUNT+ TO ROLE OPENFLOW_ADMIN;++ GRANT CREATE INTEGRATION ON ACCOUNT TO ROLE OPENFLOW_ADMIN; ```
Prerequisites を再構成し、Openflow のデプロイメントとランタイムを必須条件として追加しました。ランタイム作成前のサイズ決定と CDC ランタイムサイズ説明へのリンク、Snowflake deployments 利用時のドメイン許可先リンクを追加し、データベース側の手順を Source database setup として分離しています。増分レプリケーションの説明はこのページから削除され、バイナリログ表の一部は体裁のみ変更されています。 影響: 利用者はコネクタ設定前に Openflow ランタイムを作成し、そのサイズを事前に決める必要があります。
変更内容: 本文を更新（496行追加・386行削除）
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/mysql/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/mysql/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).@@ -20,21 +20,27 @@ This topic describes the steps to set up the %mysql%. -This connector can be configured to immediately start replicating incremental changes for newly added tables,-bypassing the snapshot load phase. This option is often useful when reinstalling the connector-in an account where previously replicated data exists and you want to continue replication without having to re-snapshot tables.--For details on the incremental load process, see [Incremental replication](/user-guide/data-integration/openflow/connectors/mysql/incremental-replication).- ## Prerequisites +### Before you begin+ 1. Ensure that you have reviewed [](/user-guide/data-integration/openflow/connectors/mysql/about).-2. Ensure that you have [](/user-guide/data-integration/openflow/setup-openflow-byoc) or [Set up Openflow - Snowflake Deployments](/user-guide/data-integration/openflow/setup-openflow-spcs).-3. If using %ofsfspcs-plural%, ensure that you've reviewed [configuring required domains](/user-guide/data-integration/openflow/setup-openflow-spcs-sf-allow-list)- and have granted access to the required domains for the [](#label-openflow-domains-used-by-openflow-connectors-mysql) connector.-4. Ensure that you have MySQL 8 or later to synchronize data with Snowflake.-5. As a database administrator, perform the following tasks:- 1. Enable [binary logs](https://dev.mysql.com/doc/refman/8.4/en/binary-log.html), then save and configure its format as follows:-- <div className="colwidths-given">+2. Ensure that you have MySQL 8 or later to synchronize data with Snowflake.+3. Make sure you have an Openflow deployment and runtime for this connector. If you don't, see+ [Set up Openflow - Snowflake Deployments](/user-guide/data-integration/openflow/setup-openflow-spcs)+ or [Set up Openflow - BYOC](/user-guide/data-integration/openflow/setup-openflow-byoc).++ A runtime's size is fixed when you create it, so decide on a size before you create the runtime.+ See [](/user-guide/data-integration/openflow/connectors/cdc-runtime-sizing).++4. If using Snowflake deployments, ensure that you've reviewed [configuring required domains](/user-guide/data-integration/openflow/setup-openflow-spcs-sf-allow-list)+ and have granted access to the required domains for the [](/user-guide/data-integration/openflow/setup-openflow-spcs-sf-allow-list#label-openflow-domains-used-by-openflow-connectors-mysql) connector.++### Source database setup++As a database administrator, perform the following tasks:++1. Enable [binary logs](https://dev.mysql.com/doc/refman/8.4/en/binary-log.html), then save and configure its format as follows:++ <div className="colwidths-given"> @@ -48,9 +54,9 @@ <td> - Set to `on`.-- This enables the binary log that records structural and data changes.-- </td>+ Set to `on`.++ This enables the binary log that records structural and data changes.++ </td> </tr> <tr>@@ -58,11 +64,11 @@ <td> - Set to `row`.-- The connector supports only row-based replication. MySQL 8.x versions may be the last ones to support this setting, and future versions will only support row-based replication.-- Not applicable in GCP Cloud SQL, where it is fixed at the right value.-- </td>+ Set to `row`.++ The connector supports only row-based replication. MySQL 8.x versions may be the last ones to support this setting, and future versions will only support row-based replication.++ Not applicable in GCP Cloud SQL, where it is fixed at the right value.++ </td> </tr> <tr>@@ -70,12 +76,12 @@ <td> - Set to `full`.-- The connector requires all row metadata to operate, most importantly, column names and primary key information.-- Under Microsoft Azure Database for MySQL the `binlog_row_metadata` field isn't user modifiable.- Raise a Microsoft support ticket to change this value.-- </td>+ Set to `full`.++ The connector requires all row metadata to operate, most importantly, column names and primary key information.++ Under Microsoft Azure Database for MySQL the `binlog_row_metadata` field isn't user modifiable.+ Raise a Microsoft support ticket to change this value.++ </td> </tr> <tr>@@ -83,11 +89,11 @@ <td> - Set to `full`.-- The connector requires that all columns be written into the binary log.-- Not applicable in Amazon Aurora, where it is fixed at the right value.-- </td>+ Set to `full`.++ The connector requires that all columns be written into the binary log.++ Not applicable in Amazon Aurora, where it is fixed at the right value.++ </td> </tr> <tr>@@ -95,9 +101,9 @@ <td> - Leave empty.-- This option only affects JSON columns, where it can be set to include only the modified parts of JSON documents for `UPDATE` statements. The connector requires that full documents are written into the binary log.-- </td>+ Leave empty.++ This option only affects JSON columns, where it can be set to include only the modified parts of JSON documents for `UPDATE` statements. The connector requires that full documents are written into the binary log.++ </td> </tr> <tr>@@ -105,14 +111,17 @@ <td> - Set to at least a few hours, or longer to ensure that the database agent can continue incremental replication after extended pauses or downtime.- Snowflake recommends that you set the [binary log expiration period (binlog_expire_logs_seconds)](https://dev.mysql.com/doc/refman/8.4/en/replication-options-binary-log.html#sysvar_binlog_expire_logs_seconds) to at least a few- hours to ensure stable working of the connector. After the binary log expiration period ends,- binary log files might be automatically removed. If the integration is paused for a long period,- for example due to maintenance work, and the expired binary log files are deleted during this time,- Openflow can't replicate the data from these files.-- If you're using scheduled replication, the value needs to be longer than the configured schedule.-- </td>+ Snowflake recommends setting the+ [binary log expiration period (binlog_expire_logs_seconds)](https://dev.mysql.com/doc/refman/8.4/en/replication-options-binary-log.html#sysvar_binlog_expire_logs_seconds)+ to at least 72 hours (`259200`).++ Retention has to cover the entire window between a replication problem starting, someone+ noticing it, and the fix being applied. Once the expiration period elapses, MySQL can remove+ binary log files automatically, and Openflow can't replicate data from files that no longer+ exist, so the data is lost. Time spent paused counts toward that window, whether the pause is+ planned maintenance or an unnoticed failure.++ If you're using scheduled replication, the value needs to be longer than the conf... (truncated)
差分が長いため、途中まで表示しています。
複数 CDC コネクタを 1 つのランタイムで実行する手順（Snowflake CoCo の openflow skill、共有 Source/Destination context、Ingestion context の個別上書き）が本文から削除され、参照先が #run-multiple-connectors-on-one-runtime に変更されました。あわせて、Openflow Snowflake deployments と BYOC deployments の説明順が入れ替わっています。 影響: 複数コネクタの具体的な設定手順はこのページでは確認できなくなり、新しい参照先で手順を確認する必要があります。
変更内容: 本文を更新（15行追加・98行削除）
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/oracle/setup-connector+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/oracle/setup-connector@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).@@ -85,6 +85,5 @@ keep their shared Source and Destination parameter contexts intact and override only the per-connector values in each Ingestion context. For the-recommended process, see [Run multiple CDC connector instances on one runtime](#label-openflow-cdc-connector-packing-parameter-contexts)-in the configuration section for the connector you are setting up.+recommended process, see [](#run-multiple-connectors-on-one-runtime). Run a connector on a dedicated runtime, not packed with others, when any of the@@ -135,93 +134,5 @@ - [](#label-oracle-source-parameters): Used to define the configuration of data downloaded from Oracle. -<a id="label-openflow-cdc-connector-packing-parameter-contexts"></a>--### Run multiple CDC connector instances on one runtime--You don't have to configure multiple CDC connector instances by hand. The-**openflow skill in Snowflake CoCo** is the recommended path when you need to-run many CDC connectors on one runtime. The skill applies this pattern-consistently across the connector fleet. To get started, install and connect-the [Snowflake CoCo CLI](/user-guide/cortex-code/cortex-code-cli), then ask-the bundled [openflow skill](/user-guide/cortex-code/bundled-skills#label-bundled-skill-openflow)-to configure the layout.--Each CDC connector instance uses Source, Destination, and Ingestion parameter-contexts. The Ingestion context inherits from the Source and Destination-contexts, so any value you don't override in Ingestion resolves from the-parent context.--<a id="label-openflow-cdc-connector-packing-recommended-setup"></a>--#### Use shared Source and Destination contexts with per-connector overrides in Ingestion--Snowflake recommends this setup for running multiple CDC connector instances-manually. It's the same pattern the openflow skill applies automatically at-scale.--When you import more than one CDC connector instance of the same type into one-runtime, keep the Source and Destination contexts at their default names and-let every connector instance inherit from them. In that connector's Ingestion-parameter context, override only the values that differ from the shared-defaults: the connection URL, replication slot or server ID, destination-database, and table list. Leave shared values, such as the Snowflake role,-warehouse, and JDBC driver, in the Source and Destination contexts so every-connector instance inherits them.--Use the following process for each additional connector instance:--1. Import the connector instance.-2. Confirm that its Ingestion context inherits from the existing Source and- Destination contexts, instead of creating a new set of Source and- Destination contexts.-3. In the Ingestion context, override every value that must differ from the- shared defaults: at minimum, the source connection identity (for example,- the JDBC URL and replication slot or server ID) and the destination- database.-4. Confirm that the connector replicates from the correct source into the- correct destination before moving on to the next connector instance.--<a id="label-openflow-cdc-connector-packing-do-not-rename"></a>--#### Don't rename the Source and Destination contexts--Don't rename the Source or Destination parameter contexts to make them unique-per connector instance. Renaming these contexts might seem like a simpler way-to keep each connector instance visually distinct, but it silently breaks-future connector version upgrades.--When Snowflake ships a connector version that adds a new parameter to the-Source or Destination context, the upgrade process looks for a context with-the connector's default name to apply that new parameter to. If you renamed-the context, the upgrade process can't find it, and the new parameter isn't-added to the context your connector instances actually use. Your connector-instances then silently fall out of sync with the new version, and the-Snowflake registry can't repair this automatically. This risk applies whether-you rename the contexts to a single shared alternate name or to a distinct-name per connector instance.--The Ingestion context is safe to rename, because the registry creates a fresh-Ingestion context for every new connector instance. Renaming it doesn't affect-any other connector instance or any future upgrade. If you want every-connector instance to be individually identifiable in the parameter context-list, rename only its Ingestion context, for example to the source database-name, tenant name, or region.--<a id="label-openflow-cdc-connector-packing-avoid-unintended-inheritance"></a>--#### Avoid unintended inheritance from an earlier connector instance--The most common mistake when importing an additional CDC connector instance is-unintentionally reusing the previous instance's Ingestion context, instead of-creating a dedicated context. If this happens, the new connector instance uses the-earlier instance's source database, destination database, table list,-replication slot, server ID, or XStream configuration, and replicates the-wrong data without any error.--After importing each additional connector instance, always confirm that its-Ingestion context is new and dedicated to that instance, and not shared with-any earlier connector instance. If the import wizard offers an option to-inherit existing parameter contexts, confirm that it creates a new Ingestion-context rather than reusing an existing one.+To run multiple CDC connector instances on one runtime, see [](/user-guide/data-integration/openflow/connectors/cdc-runtime-sizing#run-multiple-connectors-on-one-runtime). <a id="label-oracle-snowflake-destination-parameters"></a>@@ -248,6 +159,7 @@ <td> -The database where data is persisted. It must already exist in Snowflake.-The name is case-sensitive. For unquoted identifiers, provide the name in uppercase.+The database where data is persisted. It must already exist in Snowflake and the connector's+role must have `USAGE` and `CREATE SCHEMA` on it. The name is case-sensitive. For unquoted+identifiers, provide the name in uppercase. </td>@@ -327,5 +239,5 @@ - **SNOWFLAKE_MANAGED** Authentication Strategy: Must be blank.--+ <dl>@@ -422,5 +334,5 @@ - **Fail Table** (default): The table is marked as failed on the first invalid row, and replication stops for that table.-- **Log Errors and Continue**: The connector keeps replicating the valid rows and records each rejected row in the table's error table.+- **Log Errors and Continue** : The connector keeps replicating the valid rows and records each rejected row in the table's error table. </blockquote>@@ -431,5 +343,10 @@ <tr> <td>Snowflake Warehouse</td>- <td>Snowflake warehouse used to run queries.</td>+ <td>++Snowflake warehouse used to run merge queries. Start with `XSMALL`; for many tables, a+multi-cluster warehouse scales better than a larger size.++</td> <td>Yes</td> </tr>
対応リージョンの記載順が変更され、Openflow Snowflake deployments が先に示されるようになりました。また、複数 CDC コネクタを同一ランタイムで実行する詳細説明（Snowflake CoCo の openflow skill、共有 Source／Destination コンテキスト、Ingestion の個別上書き手順）が削除され、参照先が #run-multiple-connectors-on-one-runtime に変更されています。
影響: 複数 CDC コネクタの具体的な設定手順はこのページから確認できなくなり、移転先または詳細は diff からは詳細不明です。
変更内容: 本文を更新（4行追加・93行削除）
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).@@ -247,6 +247,5 @@ keep their shared Source and Destination parameter contexts intact and override only the per-connector values in each Ingestion context. For the-recommended process, see [Run multiple CDC connector instances on one runtime](#label-openflow-cdc-connector-packing-parameter-contexts)-in the configuration section for the connector you are setting up.+recommended process, see [](#run-multiple-connectors-on-one-runtime). Run a connector on a dedicated runtime, not packed with others, when any of the@@ -304,93 +303,5 @@ SQLServer Ingestion Parameters context, the configuration is picked up by the connector, and the replication lifecycle starts for every table. -<a id="label-openflow-cdc-connector-packing-parameter-contexts"></a>--### Run multiple CDC connector instances on one runtime--You don't have to configure multiple CDC connector instances by hand. The-**openflow skill in Snowflake CoCo** is the recommended path when you need to-run many CDC connectors on one runtime. The skill applies this pattern-consistently across the connector fleet. To get started, install and connect-the [Snowflake CoCo CLI](/user-guide/cortex-code/cortex-code-cli), then ask-the bundled [openflow skill](/user-guide/cortex-code/bundled-skills#label-bundled-skill-openflow)-to configure the layout.--Each CDC connector instance uses Source, Destination, and Ingestion parameter-contexts. The Ingestion context inherits from the Source and Destination-contexts, so any value you don't override in Ingestion resolves from the-parent context.--<a id="label-openflow-cdc-connector-packing-recommended-setup"></a>--#### Use shared Source and Destination contexts with per-connector overrides in Ingestion--Snowflake recommends this setup for running multiple CDC connector instances-manually. It's the same pattern the openflow skill applies automatically at-scale.--When you import more than one CDC connector instance of the same type into one-runtime, keep the Source and Destination contexts at their default names and-let every connector instance inherit from them. In that connector's Ingestion-parameter context, override only the values that differ from the shared-defaults: the connection URL, replication slot or server ID, destination-database, and table list. Leave shared values, such as the Snowflake role,-warehouse, and JDBC driver, in the Source and Destination contexts so every-connector instance inherits them.--Use the following process for each additional connector instance:--1. Import the connector instance.-2. Confirm that its Ingestion context inherits from the existing Source and- Destination contexts, instead of creating a new set of Source and- Destination contexts.-3. In the Ingestion context, override every value that must differ from the- shared defaults: at minimum, the source connection identity (for example,- the JDBC URL and replication slot or server ID) and the destination- database.-4. Confirm that the connector replicates from the correct source into the- correct destination before moving on to the next connector instance.--<a id="label-openflow-cdc-connector-packing-do-not-rename"></a>--#### Don't rename the Source and Destination contexts--Don't rename the Source or Destination parameter contexts to make them unique-per connector instance. Renaming these contexts might seem like a simpler way-to keep each connector instance visually distinct, but it silently breaks-future connector version upgrades.--When Snowflake ships a connector version that adds a new parameter to the-Source or Destination context, the upgrade process looks for a context with-the connector's default name to apply that new parameter to. If you renamed-the context, the upgrade process can't find it, and the new parameter isn't-added to the context your connector instances actually use. Your connector-instances then silently fall out of sync with the new version, and the-Snowflake registry can't repair this automatically. This risk applies whether-you rename the contexts to a single shared alternate name or to a distinct-name per connector instance.--The Ingestion context is safe to rename, because the registry creates a fresh-Ingestion context for every new connector instance. Renaming it doesn't affect-any other connector instance or any future upgrade. If you want every-connector instance to be individually identifiable in the parameter context-list, rename only its Ingestion context, for example to the source database-name, tenant name, or region.--<a id="label-openflow-cdc-connector-packing-avoid-unintended-inheritance"></a>--#### Avoid unintended inheritance from an earlier connector instance--The most common mistake when importing an additional CDC connector instance is-unintentionally reusing the previous instance's Ingestion context, instead of-creating a dedicated context. If this happens, the new connector instance uses the-earlier instance's source database, destination database, table list,-replication slot, server ID, or XStream configuration, and replicates the-wrong data without any error.--After importing each additional connector instance, always confirm that its-Ingestion context is new and dedicated to that instance, and not shared with-any earlier connector instance. If the import wizard offers an option to-inherit existing parameter contexts, confirm that it creates a new Ingestion-context rather than reusing an existing one.+To run multiple CDC connector instances on one runtime, see [](/user-guide/data-integration/openflow/connectors/cdc-runtime-sizing#run-multiple-connectors-on-one-runtime). <a id="label-of-sqlserver-source-parameters"></a>
Openflow Snowflake deployments の案内順が変更され、BYOC より前に掲載されました。また、複数の CDC コネクタを 1 つのランタイムで実行する詳細な手順（Source／Destination／Ingestion parameter contexts の共有・上書き方法や Snowflake CoCo の openflow skill の説明）が削除され、一般的なアンカーへの参照に置き換えられました。 影響: 複数 CDC コネクタの手動構成に関するページ内の具体的な手順が読めなくなったため、既存設定への直接的な機能影響は不明ですが、新規構成時は diff からは詳細不明です。
変更内容: 本文を更新（4行追加・93行削除）
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server-cdc/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server-cdc/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).@@ -597,6 +597,5 @@ keep their shared Source and Destination parameter contexts intact and override only the per-connector values in each Ingestion context. For the-recommended process, see [Run multiple CDC connector instances on one runtime](#label-openflow-cdc-connector-packing-parameter-contexts)-in the configuration section for the connector you are setting up.+recommended process, see [](#run-multiple-connectors-on-one-runtime). Run a connector on a dedicated runtime, not packed with others, when any of the@@ -654,93 +653,5 @@ SQLServer Ingestion Parameters context, the configuration is picked up by the connector, and the replication lifecycle starts for every table. -<a id="label-openflow-cdc-connector-packing-parameter-contexts"></a>--### Run multiple CDC connector instances on one runtime--You don't have to configure multiple CDC connector instances by hand. The-**openflow skill in Snowflake CoCo** is the recommended path when you need to-run many CDC connectors on one runtime. The skill applies this pattern-consistently across the connector fleet. To get started, install and connect-the [Snowflake CoCo CLI](/user-guide/cortex-code/cortex-code-cli), then ask-the bundled [openflow skill](/user-guide/cortex-code/bundled-skills#label-bundled-skill-openflow)-to configure the layout.--Each CDC connector instance uses Source, Destination, and Ingestion parameter-contexts. The Ingestion context inherits from the Source and Destination-contexts, so any value you don't override in Ingestion resolves from the-parent context.--<a id="label-openflow-cdc-connector-packing-recommended-setup"></a>--#### Use shared Source and Destination contexts with per-connector overrides in Ingestion--Snowflake recommends this setup for running multiple CDC connector instances-manually. It's the same pattern the openflow skill applies automatically at-scale.--When you import more than one CDC connector instance of the same type into one-runtime, keep the Source and Destination contexts at their default names and-let every connector instance inherit from them. In that connector's Ingestion-parameter context, override only the values that differ from the shared-defaults: the connection URL, replication slot or server ID, destination-database, and table list. Leave shared values, such as the Snowflake role,-warehouse, and JDBC driver, in the Source and Destination contexts so every-connector instance inherits them.--Use the following process for each additional connector instance:--1. Import the connector instance.-2. Confirm that its Ingestion context inherits from the existing Source and- Destination contexts, instead of creating a new set of Source and- Destination contexts.-3. In the Ingestion context, override every value that must differ from the- shared defaults: at minimum, the source connection identity (for example,- the JDBC URL and replication slot or server ID) and the destination- database.-4. Confirm that the connector replicates from the correct source into the- correct destination before moving on to the next connector instance.--<a id="label-openflow-cdc-connector-packing-do-not-rename"></a>--#### Don't rename the Source and Destination contexts--Don't rename the Source or Destination parameter contexts to make them unique-per connector instance. Renaming these contexts might seem like a simpler way-to keep each connector instance visually distinct, but it silently breaks-future connector version upgrades.--When Snowflake ships a connector version that adds a new parameter to the-Source or Destination context, the upgrade process looks for a context with-the connector's default name to apply that new parameter to. If you renamed-the context, the upgrade process can't find it, and the new parameter isn't-added to the context your connector instances actually use. Your connector-instances then silently fall out of sync with the new version, and the-Snowflake registry can't repair this automatically. This risk applies whether-you rename the contexts to a single shared alternate name or to a distinct-name per connector instance.--The Ingestion context is safe to rename, because the registry creates a fresh-Ingestion context for every new connector instance. Renaming it doesn't affect-any other connector instance or any future upgrade. If you want every-connector instance to be individually identifiable in the parameter context-list, rename only its Ingestion context, for example to the source database-name, tenant name, or region.--<a id="label-openflow-cdc-connector-packing-avoid-unintended-inheritance"></a>--#### Avoid unintended inheritance from an earlier connector instance--The most common mistake when importing an additional CDC connector instance is-unintentionally reusing the previous instance's Ingestion context, instead of-creating a dedicated context. If this happens, the new connector instance uses the-earlier instance's source database, destination database, table list,-replication slot, server ID, or XStream configuration, and replicates the-wrong data without any error.--After importing each additional connector instance, always confirm that its-Ingestion context is new and dedicated to that instance, and not shared with-any earlier connector instance. If the import wizard offers an option to-inherit existing parameter contexts, confirm that it creates a new Ingestion-context rather than reusing an existing one.+To run multiple CDC connector instances on one runtime, see [](/user-guide/data-integration/openflow/connectors/cdc-runtime-sizing#run-multiple-connectors-on-one-runtime). <a id="label-of-sqlserver-cdc-source-parameters"></a>
Openflow の execute-as role に加え、runtime が外部データソースへ接続するための network rules と external access integrations (EAI) の作成・関連付けを同ページで扱う構成に変更されました。execute-as role は複数 runtime で再利用可能となり、付与先が USER <username> から ROLE OPENFLOW_ADMIN に変更され、データベース／スキーマのプレースホルダーも <OPENFLOW_SPCS_DATABASE> 等から <openflow_db>／<openflow_schema> に変更されています。
影響: 既存手順から移行する場合は、権限付与先を OPENFLOW_ADMIN ロールに見直し、EAI とネットワークルールおよび必要に応じた outbound PrivateLink の設定手順を確認する必要があります。
変更内容: 本文を更新（37行追加・28行削除）
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-spcs-create-rr+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-spcs-create-rr@@ -1,3 +1,3 @@-# Set up %ofsfspcs%: Create execute-as role+# Set up %ofsfspcs%: Create the execute-as role and external access integrations This feature is not available in the People's Republic of China.@@ -10,34 +10,27 @@ - [](/user-guide/data-integration/openflow/connectors/about-openflow-connectors) -%ofsfspcs% requires the creation of a number of resources which are specific not to a deployment-but to a specific runtime. Typically such resources include:+%ofsfspcs% runtimes need a few supporting resources before they can access your data: -- Creation of a runtime-specific execute-as role-- Creation of Runtime specific network rules and External Access Integrations (EAI)+- An execute-as role that flows use to access Snowflake objects+- Network rules and external access integrations (EAI) that let the runtime reach external data sources This topic describes the creation of these resources. 1. Create an execute-as role and grant it the privileges needed to write data to Snowflake.-2. Associate the execute-as role with a runtime.-3. Create External Access Integrations and associate them to Runtimes.- See [Creating External Access Integrations](#label-create-network-rules-and-external-access-integrations)-4. When Outbound PrivateLink connectivity is required to connect to a private system using SPCS Egress.+2. Associate the execute-as role with the runtime.+3. Create external access integrations and associate them with the runtime.+ See [Creating network rules and external access integrations](#label-create-network-rules-and-external-access-integrations).+4. Configure outbound PrivateLink if required to connect to a private system using SPCS egress. <a id="label-create-runtime-role"></a> -## Create an execute-as role+## Create the execute-as role -When creating and editing Openflow runtimes, runtime owners associate a role with the runtime.-This role is used for flows that execute within the runtime.-For more information, see [What is an execute-as role?](/user-guide/data-integration/openflow/about-spcs#label-openflow-spcs-what-is-runtime-role).+When creating an Openflow runtime, you associate a role with it. Flows that run within the runtime+execute as this role, so it's called the execute-as role. You can reuse the same execute-as role+across multiple runtimes. For more information, see+[What is an execute-as role?](/user-guide/data-integration/openflow/about-spcs#label-openflow-spcs-what-is-runtime-role). -Creating an execute-as role is a prerequisite for creating a runtime and involves the following steps:--1. Create the role itself-2. Grant the role access to the warehouse used by the Runtime.-3. Grant the role access to the Snowflake objects used by the Runtime.-4. Grant the role access to the External Access Integrations used by the Runtime.--To create an execute-as role:+Creating the role is a prerequisite for creating a runtime: 1. Create the role.@@ -52,5 +45,5 @@ CREATE ROLE IF NOT EXISTS OPENFLOW_<RUNTIME_NAME>_EXECUTE_AS_RL; - GRANT ROLE OPENFLOW_<RUNTIME_NAME>_EXECUTE_AS_RL TO USER <username>;+ GRANT ROLE OPENFLOW_<RUNTIME_NAME>_EXECUTE_AS_RL TO ROLE OPENFLOW_ADMIN; ``` @@ -69,11 +62,14 @@ ```sql- GRANT USAGE ON DATABASE <OPENFLOW_SPCS_DATABASE> TO ROLE OPENFLOW_<RUNTIME_NAME>_EXECUTE_AS_RL;- GRANT USAGE ON SCHEMA <OPENFLOW_SPCS_SCHEMA> TO ROLE OPENFLOW_<RUNTIME_NAME>_EXECUTE_AS_RL;+ GRANT USAGE ON DATABASE <openflow_db> TO ROLE OPENFLOW_<RUNTIME_NAME>_EXECUTE_AS_RL;+ GRANT USAGE ON SCHEMA <openflow_schema> TO ROLE OPENFLOW_<RUNTIME_NAME>_EXECUTE_AS_RL; ``` <a id="label-create-network-rules-and-external-access-integrations"></a> -### Creating Network Rules and External Access Integrations+## Creating network rules and external access integrations++The following steps apply to both gen 1 and gen 2 Snowflake deployments. Both generations+require network rules and EAIs so the runtime can reach external data sources. Snowflake's security model provides secure access to specific endpoints and systems@@ -94,13 +90,22 @@ These examples use RUNTIME_NAME as a placeholder for the name of the Runtime being created. +Replacing a network rule or external access integration silently detaches it from every runtime+that references it. Use `CREATE ... IF NOT EXISTS` for new objects, and `ALTER` to modify existing+ones.+ 1. Create an appropriate network rule. See [](/sql-reference/sql/create-network-rule) for more information. - `<OPENFLOW_DATABASE>` denotes the name of the database that will contain the network rule.- Snowflake suggests creating a specific database for network rules and external access integrations related to Openflow.+ Snowflake recommends creating network rules in the same infrastructure schema+ (`openflow_db.openflow_schema`) you've been using for Openflow objects, so that+ everything is in one place. An EAI is an account-level object, so it has no+ database or schema; a network rule is a schema-level object. Where you keep the+ network rule is your choice as long as the execute-as role has access to the+ EAI, but using the infrastructure schema keeps things simple and consistent. ```sql- USE DATABASE <OPENFLOW_DATABASE>;+ USE DATABASE <openflow_db>;+ USE SCHEMA <openflow_schema>; CREATE NETWORK RULE IF NOT EXISTS OPENFLOW_<RUNTIME_NAME>_NETWORK_RULE@@ -150,4 +155,8 @@ ``` +Replacing a network rule or external access integration silently detaches it from every runtime+that references it. Use `CREATE ... IF NOT EXISTS` for new objects, and `ALTER` to modify existing+ones.+ ## Next steps
生成物が snowflake.yml（snowflake-app エンティティ）から、app.yml のフラットな version: 2 マニフェストへ変更され、name、database、schema、query_warehouse が事前設定されるようになりました。--database、--schema、--warehouse は接続設定の値を上書きする説明に簡略化され、生成される app.yml には code_stage と code_workspace を含めない仕様になっています。既存の snowflake.yml を使うプロジェクトは従来どおり動作すると明記されました。
影響: 新規プロジェクトでは app.yml を前提に編集・デプロイする必要がありますが、既存の snowflake.yml プロジェクトの移行は不要です。
変更内容: 本文を更新（29行追加・27行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/setup+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/setup@@ -10,8 +10,9 @@ - [](/developer-guide/snowflake-app-runtime/app-yml) -Initializes a `snowflake.yml` for a Snowflake App Runtime project. Creates a-`snowflake.yml` file in the current directory with a `snowflake-app` entity-preconfigured from Snowsight account defaults and your current connection. This command-does not apply to Snowflake Native Apps projects.+Initializes an `app.yml` for a Snowflake App Runtime project. Creates an+`app.yml` in the current directory: a flat `version: 2` manifest whose `name`,+`database`, `schema`, and `query_warehouse` are preconfigured from account+parameters and the current connection. This command does not apply to Native App+projects. ## Syntax@@ -65,5 +66,5 @@ <dd> -Only print the resolved configuration values without writing `snowflake.yml`. Default: False.+Only print the resolved configuration values without writing app.yml. Default: False. </dd>@@ -145,7 +146,5 @@ <dd> -Database to use. In `snow app setup`, this value is written to the generated-`snowflake.yml` as an explicit override, taking precedence over account-parameters and connection defaults.+Database to use. Overrides the value specified for the connection. </dd>@@ -153,7 +152,5 @@ <dd> -Database schema to use. In `snow app setup`, this value is written to the-generated `snowflake.yml` as an explicit override, taking precedence over-account parameters and connection defaults.+Database schema to use. Overrides the value specified for the connection. </dd>@@ -167,7 +164,5 @@ <dd> -Warehouse to use. In `snow app setup`, this value is written to the generated-`snowflake.yml` as the `query_warehouse` override, taking precedence over-account parameters and connection defaults.+Warehouse to use. Overrides the value specified for the connection. </dd>@@ -246,5 +241,5 @@ The `snow app setup` command bootstraps a new Snowflake App Runtime project by-generating a `snowflake.yml` file that contains a `snowflake-app` entity and the+generating an `app.yml` file: a flat `version: 2` manifest that contains the default deployment details. Setup resolves the destination database, schema, and warehouse in this order: the explicit `--database`, `--schema`, and@@ -252,6 +247,9 @@ [account administrator setup](/developer-guide/snowflake-app-runtime/account-admin-setup), then your current connection settings. Remote builds use the shared external-access integration from Snowsight setup; you don't add one in `snowflake.yml`+access integration from Snowsight setup; you don't add one in `app.yml` for the usual path.++Existing projects that use a `snowflake.yml` with a `snowflake-app` entity keep+working as before. We recommend completing@@ -260,5 +258,5 @@ service packages your app when you run [`snow app deploy`](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/deploy).-After `snowflake.yml` exists, edit it only when you need to override defaults,+After `app.yml` exists, edit it only when you need to override defaults, then deploy to ship your changes. @@ -276,9 +274,11 @@ [How field values are resolved](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/snowflake-yml#label-snowflake-yml-resolution). -The generated file uses a workspace backend (`code_workspace`) when the database-came from your [personal database](/user-guide/personal-databases). Otherwise it-uses a stage backend (`code_stage`).--If `snowflake.yml` already exists in the current directory (and you aren't using+Setup leaves `code_stage` and `code_workspace` out of the generated `app.yml`, so+[`snow app deploy`](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/deploy)+provisions temporary code storage for the build and drops it afterward. Set+`code_stage` or `code_workspace` in `app.yml` to keep a persisted stage or+workspace instead.++If `app.yml` already exists in the current directory (and you aren't using `--dry-run`), setup prints a message and does not overwrite the file. @@ -288,7 +288,9 @@ the command errors. -For the full `snowflake.yml` structure and schema, see the+For the `app.yml` manifest fields, see+[](/developer-guide/snowflake-app-runtime/app-yml). For the `snowflake.yml`+schema that existing projects use, see the [snowflake.yml reference](/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/snowflake-yml).-For a concrete `snowflake.yml` example after setup, see+For a concrete example after setup, see [Getting started with Snowflake App Runtime](/developer-guide/snowflake-app-runtime/getting-started). For entity keys, identifiers, mixins, and other patterns the CLI applies to@@ -298,5 +300,5 @@ ## Examples -Initialize `snowflake.yml` for a Snowflake App Runtime project in the current directory:+Initialize `app.yml` for a Snowflake App Runtime project in the current directory: ```snowcli@@ -304,5 +306,5 @@ ``` -After running the command, edit `snowflake.yml` to configure your app, then deploy it:+After running the command, edit `app.yml` to configure your app, then deploy it: ```snowcli@@ -310,5 +312,5 @@ ``` -Show the resolved configuration without writing `snowflake.yml`:+Show the resolved configuration without writing `app.yml`: ```snowcli
リリースノートの記載が整理され、dbt command center、OUTPUTパネル、Lineageタブ、restricted session scope改善、dbt.snowflakeManaged.executionTimeout（既定値4時間）および関連修正の説明が削除されました。一方、Monthlyスケジュール、DesktopからのHTMLレポート公開、チャットセッションの右クリックメニュー（Pin・Rename・Delete）は引き続き記載されています。 影響: dbtやセッションスコープ関連の変更内容はこのリリースノートから確認できなくなり、利用者は新たに記載された月次自動化やHTMLレポート公開機能を中心に参照することになります。
変更内容: 本文を更新（5行追加・34行削除）
--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-21-1+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-21-1@@ -3,33 +3,13 @@ # Cortex Code Desktop v1.21.1 release notes -v1.21.1 is a stability and polish release on top of v1.21.0. It gives dbt projects a full command-center with output streaming and a new Lineage tab, completes the restricted session scope-experience, adds monthly automation schedules, and fixes a bug that could stop all terminal commands-from working until you restarted the app.+v1.21.1 is a stability and polish release on top of v1.21.0. It adds monthly automation schedules,+lets you publish HTML reports natively from Desktop, adds a right-click menu for chat sessions, and+fixes a bug that could stop all terminal commands from working until you restarted the app. ## What's new -- **dbt command center**: In local mode, the Project Action Bar now has an editable full-CLI command- input with **Run** and **Stop** buttons. For Snowflake-managed runs, the Action Bar adds Profile- and Environment controls plus an input for `--select` and other flags. Your choices persist per- project, and the command preview updates as you change flags.--- **dbt output in the OUTPUT panel**: dbt runs started from the Action Bar stream into the native- **OUTPUT** panel as a plain-text, copy-paste-friendly transcript with clear run status. Transcripts- are kept per project, so they survive switching projects. Snowflake-managed command labels are- sanitized: `ENV_VARS` keys are shown but values are redacted.--- **New Lineage tab**: The dbt DAG moves into a **Lineage** tab in the bottom panel that follows the- project you have selected. You can send lineage selections straight to chat with **Add to chat**.--- **Restricted session scope improvements**: The restricted session scope dialog now opens- immediately with an in-dialog loading state instead of waiting on Snowflake, keeps a single- persistent dialog as you move between the existing-scope and creation steps, lists all your account- roles up front instead of requiring a search term, and keeps **Back** and **Cancel** available- while creation is in flight.- - **Monthly automation schedules**: Automations add a **Monthly** frequency with a day-of-month- control (1 through 31), for both local and cloud automations. Months that don't have the chosen day- are skipped, so a schedule set to the 31st is safe in February.+ control (1 through 31). Months that don't have the chosen day are skipped, so a schedule set to the+ 31st is safe in February. - **Publish HTML reports from Desktop**: The publish-report flow now runs natively in Cortex Code@@ -40,7 +20,4 @@ **Pin**, **Rename**, and **Delete** from a right-click context menu, alongside the existing hover buttons.--- **dbt execution timeout**: A new `dbt.snowflakeManaged.executionTimeout` setting (default 4 hours)- caps Snowflake-managed dbt runs that never return, instead of showing them as running indefinitely. ## Reliability and fixes@@ -57,8 +34,2 @@ - **Fewer renderer crashes**: Fixed a memory leak where pooled code blocks retained their editor models, which could crash the renderer during heavy streamed output.-- **Fixed: dbt runs hanging or losing results on timeout**: A Snowflake-managed dbt run that timed- out could wedge, or could discard its `manifest.json` and `run_results.json` when it actually- succeeded during cancellation.-- **Steadier restricted session scope setup**: An expired parent token during child-session setup now- retries once with refreshed credentials instead of surfacing an isolation error. Scope isolation is- preserved.
Runtime sizing の参照先が共通ガイダンスに変更され、手順では Openflow administrator と data engineer の役割が分離されました。また、変更履歴を保持するジャーナルテーブルの命名規則（<source_table_name>_JOURNAL_<timestamp>_<schema_generation>）と、構造を変更しない推奨事項が追加されました。冒頭のデプロイメント説明は順序が入れ替わっています。
影響: 運用時は権限分担を見直し、ジャーナルテーブルを直接変更しないこと、および新しいランタイムサイズガイダンスを参照する必要があります。
変更内容: 本文を更新（28行追加・9行削除）
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/mysql/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/mysql/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).@@ -117,5 +117,5 @@ ## Openflow requirements -- Choose the runtime size based on the sustained replication workload. For sizing guidance and how to run multiple connectors on one runtime, see [Runtime sizing](#label-mysql-runtime-sizing).+- Choose the runtime size based on the sustained replication workload. For sizing guidance and how to run multiple connectors on one runtime, see [Runtime sizing](/user-guide/data-integration/openflow/connectors/cdc-runtime-sizing). - The connector doesn't support multi-node Openflow runtimes. Configure the runtime for this connector with **Min nodes** and **Max nodes** set to `1`. @@ -160,9 +160,11 @@ - (Optionally) Provide the SSL certificate -2. A **Snowflake account administrator** performs the following tasks:- 1. Creates a service user for the connector, a warehouse for the connector, and a destination database for the replicated data.- 2. Installs the connector.- 3. Specifies the required parameters for the flow template.- 4. Runs the flow. The connector performs the following tasks when run in Openflow:+2. An **Openflow administrator** creates a warehouse for the connector and a destination database+ for the replicated data.++3. An **Openflow administrator** or a **data engineer** performs the following tasks:+ 1. Installs the connector.+ 2. Specifies the required parameters for the flow template.+ 3. Runs the flow. The connector performs the following tasks when run in Openflow: 1. Creates a schema for journal tables. 2. Creates the schemas and destination tables matching the source tables configured for replication.@@ -236,4 +238,21 @@ The same soft-delete mechanism applies when you change a table's Column Filter JSON. For details, see [Replicate a subset of columns in a table](#label-mysql-connector-replication-subset-of-columns).++### Track data changes in tables++The connector replicates not only the current state of data from the source tables, but also every+state of every row from every changeset. This data is stored in journal tables created in the same+schema as the destination table.++The journal table names are formatted as `<source_table_name>_JOURNAL_<timestamp>_<schema_generation>`,+where `<timestamp>` is the value of epoch seconds when the source table was added to replication, and+`<schema_generation>` is an integer increasing with every schema change on the source table. As a+result, source tables that undergo schema changes will have multiple journal tables.++When a table is removed from replication, then added back, the `<timestamp>` value will change, and+`<schema_generation>` will start again from `1`.++Snowflake recommends that you don't alter the structure of journal tables in any way. They are used+by the connector to update the destination table as part of the replication process. <a id="label-mysql-replication-key-selection"></a>@@ -358,5 +377,5 @@ - **Snapshot load**: The rejected row is written to the destination table's error table.-- **Incremental (CDC) load**: The rejected row is written to the journal table's error table, because CDC changes are first written to the journal table. For more information about journal tables, see [](/user-guide/data-integration/openflow/connectors/mysql/setup#track-data-changes-in-tables).+- **Incremental (CDC) load**: The rejected row is written to the journal table's error table, because CDC changes are first written to the journal table. For more information about journal tables, see [](#track-data-changes-in-tables). The connector enables error logging only on tables that it creates after you select **Log Errors and Continue**. To capture rejected rows for tables that were already being replicated, enable error logging on their existing destination and journal tables with the stored procedure in [Enable error logging on an existing schema](/user-guide/data-integration/openflow/connectors/mysql/maintenance#label-of-mysql-enable-error-logging-existing-schema).
Openflow の対応デプロイメントに Gen 1／Gen 2 の区分が追加され、公開プレビュー機能が有効なアカウントでは新規デプロイメントが Gen 2、それ以外では Gen 1 になることが明記されました。Gen 2 ではデプロイメント、ランタイム、コネクターを SQL-first で管理でき、両デプロイメントで Snowflake secrets、Snowflake デプロイメントでは outbound private connectivity に対応する説明が追加されました。 影響: 利用者はアカウントの有効化状況に応じた世代を前提に、Gen 2 quickstart と Gen 1／Gen 2 比較ドキュメントを参照して構築・運用方法を選ぶ必要があります。
変更内容: 本文を更新（23行追加・12行削除）
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/about@@ -7,6 +7,6 @@ Openflow BYOC deployments are available to all accounts in AWS [](#label-na-general-regions). +- [](/user-guide/data-integration/openflow/about-spcs) - [](/user-guide/data-integration/openflow/about-byoc)-- [](/user-guide/data-integration/openflow/about-spcs) - [](/user-guide/data-integration/openflow/manage) - [](/user-guide/data-integration/openflow/monitor)@@ -77,5 +77,10 @@ ## Openflow deployment types -Openflow is supported in both the Bring Your Own Cloud (BYOC) and Snowpark Container Services (SPCS) versions.+Openflow is supported in both the Bring Your Own Cloud (BYOC) and Snowflake deployment types.+Both deployment types are available in gen 1 and gen 2. Your account is enabled for one or the+other: if your account is enabled for public preview features, any new deployment is gen 2;+otherwise, it is gen 1. Gen 2 (public preview) provides SQL-first management of+deployments, runtimes, and connectors. For a comparison of gen 1 and gen 2, see+[](/user-guide/data-integration/openflow/gen2/openflow-generations). <dl>@@ -91,4 +96,5 @@ When configuring %ofsfspcs-plural%, follow the process as outlined in [Setup Openflow - Snowflake Deployment](/user-guide/data-integration/openflow/setup-openflow-spcs).+For gen 2, see the [gen 2 quickstart](/user-guide/data-integration/openflow/gen2/quickstart). </dd>@@ -104,4 +110,5 @@ When configuring BYOC deployments, follow the process as outlined in [](/user-guide/data-integration/openflow/setup-openflow-byoc).+For gen 2, see the [gen 2 quickstart](/user-guide/data-integration/openflow/gen2/quickstart). </dd>@@ -154,15 +161,19 @@ </dd>-<dt>Secrets management (BYOC)</dt>-<dd>--- Integration with AWS Secrets Manager or Hashicorp Vault. For more information,+<dt>Secrets management</dt>+<dd>++- Integration with [Snowflake secrets](/sql-reference/sql/create-secret) across both BYOC and+ Snowflake deployments.+- (BYOC) Integration with AWS Secrets Manager or Hashicorp Vault. For more information, see [Encrypted Passwords in Configuration Files](https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#encrypt-config_tool). </dd>-<dt>Private link support</dt>-<dd>--- Openflow connectors are compatible with reading and writing data to Snowflake using inbound AWS PrivateLink.+<dt>Private connectivity support</dt>+<dd>++- Openflow connectors are compatible with reading and writing data to Snowflake using+ [inbound AWS PrivateLink](/user-guide/admin-security-privatelink) (BYOC) or+ [outbound private connectivity](/user-guide/private-connectivity-outbound) (Snowflake deployments). </dd>@@ -280,6 +291,6 @@ A <span className="emph">deployment</span> is where your data flows execute, within individual runtimes. You will often have multiple runtimes to isolate different projects, teams, or for SDLC reasons, all associated with a single deployment.-Deployments come in two types [Bring Your Own Cloud (BYOC)](/user-guide/data-integration/openflow/about-byoc)-and [Openflow - Snowflake](/user-guide/data-integration/openflow/about-spcs).+Deployments come in two types, [Openflow - Snowflake](/user-guide/data-integration/openflow/about-spcs)+and [Bring Your Own Cloud (BYOC)](/user-guide/data-integration/openflow/about-byoc). </dd>
v1.21.1 のハイライトが、dbt command center・出力ストリーミングなどから、月次自動化スケジュール、ネイティブHTMLレポート公開、チャットセッションの右クリックメニュー、信頼性修正へ変更されました。提示されたdiffでは、v1.21.0の行もバージョンリンクのみになっており、その他の詳細はdiffからは不明です。 影響: リリース一覧で示されるv1.21.1の主要機能が変わるため、利用者が確認すべき新機能・改善点の案内内容が更新されます。
変更内容: 本文を更新（14行追加・14行削除）
--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-desktop/release-notes/index+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-desktop/release-notes/index@@ -12,16 +12,16 @@ ## Version history -| Version | Date | Highlights |-| ---------------------------------------------------------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------- |-| [v1.21.1](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-21-1) | August 2026 | dbt command center, output streaming, and Lineage tab; restricted session scope polish; monthly automations |-| [v1.21.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-21-0) | August 2026 | Enterprise MDM enforcement on macOS, more file previews in agent mode, and a fix for repeated SSO sign-in tabs |-| [v1.20.2](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-20-2) | July 2026 | Windows update crash fix, deep-link sharing for skills and plugins, and a Restart menu item |-| [v1.20.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-20-0) | July 2026 | Smoother, more reliable chat: preserved drafts, snappier streaming, smoother MCP auto-start, and a memory crash fix |-| [v1.19.1](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-19-1) | July 2026 | Faster and smaller installs and updates, refreshed update UI, subagent inherit model, clone repo, WSL support |-| [v1.19.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-19-0) | July 2026 | Token efficiency (tool search + offload), chat threads, dbt enhancements, skills and MCP improvements, security fixes |-| [v1.18.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-18-0) | July 2026 | Semantic code search (tgrep), file-changes summary, /compact, tidier chat, Cortex Threads (experimental) |-| [v1.17.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-17-0) | June 2026 | Refreshed chat and Plan Mode, clickable file paths, Plugins Catalog, Universal Navigator |-| [v1.16.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-16-0) | June 2026 | SSH remote workspaces, Personalization page, reimagined Memory, Brave web search, long-standing fixes |-| [v1.15.1](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-15-1) | May 2026 | Plan Mode pause/resume, dbt Cloud polish, SQL Fix-it button, SSH primitives |-| [v1.15.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-15-0) | May 2026 | UX overhaul, Remote-SSH, hierarchical SQL permissions, dbt Cloud Mode, Mermaid diagrams |-| [v1.14.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-14-0) | May 2026 | Plugins, App Gallery, chat reliability, security hardening |+| Version | Date | Highlights |+| ---------------------------------------------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------ |+| [v1.21.1](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-21-1) | August 2026 | Monthly automation schedules, native HTML report publishing, a right-click menu for chat sessions, and reliability fixes |+| [v1.21.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-21-0) | August 2026 | Enterprise MDM enforcement on macOS, more file previews in agent mode, and a fix for repeated SSO sign-in tabs |+| [v1.20.2](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-20-2) | July 2026 | Windows update crash fix, deep-link sharing for skills and plugins, and a Restart menu item |+| [v1.20.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-20-0) | July 2026 | Smoother, more reliable chat: preserved drafts, snappier streaming, smoother MCP auto-start, and a memory crash fix |+| [v1.19.1](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-19-1) | July 2026 | Faster and smaller installs and updates, refreshed update UI, subagent inherit model, clone repo, WSL support |+| [v1.19.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-19-0) | July 2026 | Token efficiency (tool search + offload), chat threads, dbt enhancements, skills and MCP improvements, security fixes |+| [v1.18.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-18-0) | July 2026 | Semantic code search (tgrep), file-changes summary, /compact, tidier chat, Cortex Threads (experimental) |+| [v1.17.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-17-0) | June 2026 | Refreshed chat and Plan Mode, clickable file paths, Plugins Catalog, Universal Navigator |+| [v1.16.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-16-0) | June 2026 | SSH remote workspaces, Personalization page, reimagined Memory, Brave web search, long-standing fixes |+| [v1.15.1](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-15-1) | May 2026 | Plan Mode pause/resume, dbt Cloud polish, SQL Fix-it button, SSH primitives |+| [v1.15.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-15-0) | May 2026 | UX overhaul, Remote-SSH, hierarchical SQL permissions, dbt Cloud Mode, Mermaid diagrams |+| [v1.14.0](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-14-0) | May 2026 | Plugins, App Gallery, chat reliability, security hardening |
dbt command center、dbt 出力の OUTPUT パネル表示、Lineage タブ、Restricted session scope 改善、および dbt.snowflakeManaged.executionTimeout（既定値 4 時間）の記載が削除されました。一方、HTML レポートのネイティブ公開、チャットセッションの右クリック操作（Pin／Rename／Delete）、月次スケジュールの明記が追加され、メモリリークによる renderer クラッシュ修正も追記されています。
影響: dbt 関連の新機能・設定変更はこのリリース概要から確認できなくなった一方、cortex バイナリなしで HTML レポートを公開でき、チャット管理と大量出力時の安定性が向上します。
変更内容: 本文を更新（9行追加・18行削除）
--- ahttps://docs.snowflake.com/en/release-notes/2026/other/2026-08-24-coco-desktop-v1-21-1+++ bhttps://docs.snowflake.com/en/release-notes/2026/other/2026-08-24-coco-desktop-v1-21-1@@ -1,27 +1,18 @@ # Aug 24, 2026: CoCo Desktop v1.21.1 -CoCo Desktop v1.21.1 is a stability and polish release that focuses on dbt projects, restricted-session scope, and automation schedules:+CoCo Desktop v1.21.1 is a stability and polish release that focuses on automation schedules, native+HTML report publishing, and reliability: -- **dbt command center**: The Project Action Bar adds an editable full-CLI command input with **Run**- and **Stop** for local runs, plus Profile, Environment, and `--select` controls for- Snowflake-managed runs.-- **dbt output in the OUTPUT panel**: dbt runs stream into the native **OUTPUT** panel as- copy-paste-friendly transcripts that are kept per project. Snowflake-managed command labels are- sanitized so environment variable values aren't written to the log.-- **New Lineage tab**: The dbt DAG moves into a **Lineage** tab in the bottom panel that follows your- selected project, and you can send lineage selections to chat.-- **Restricted session scope improvements**: The dialog opens immediately with a loading state, stays- persistent across steps, lists all your account roles up front, and stays cancellable while it- works. - **Monthly automation schedules**: Schedule an automation on a specific day of the month (1 through- 31) for both local and cloud automations.+ 31).+- **Publish HTML reports from Desktop**: The publish-report flow now runs natively, so publishing an+ HTML report no longer requires the `cortex` command-line binary.+- **Right-click menu for chat sessions**: Conversations in the Agent Manager sidebar offer **Pin**,+ **Rename**, and **Delete** from a right-click context menu. - **Fixed: terminal commands failing until restart**: Leaked pseudo-terminals from subagent and background terminals could stop all new terminal commands from working until you restarted the app. -This release also fixes remote path handling on Windows clients over SSH, publishes HTML reports-natively from CoCo Desktop, adds a right-click context menu for chat sessions in the Agent Manager-sidebar, and adds a `dbt.snowflakeManaged.executionTimeout` setting (default 4 hours) that caps-Snowflake-managed dbt runs that never return.+This release also fixes remote path handling on Windows clients over SSH and a memory leak that could+crash the renderer during heavy streamed output. For more information, see [](/user-guide/cortex-code/cortex-code-desktop/release-notes/v1-21-1).
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（9行追加・9行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/native-apps-commands/setup-app+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/native-apps-commands/setup-app@@ -6,5 +6,5 @@ - [](/developer-guide/snowflake-cli/command-reference/native-apps-commands/deploy-app) -Initializes a `snowflake.yml` for a Snowflake Apps Deploy project. Creates a `snowflake.yml` file in the current directory with a `snowflake-app` entity preconfigured from account parameters and the current connection. This command does not apply to Snowflake Native Apps projects.+(Snowflake App Runtime only) Initializes an `app.yml` for a Snowflake App Runtime project. Creates an `app.yml` in the current directory: a flat `version: 2` manifest whose `name`, `database`, `schema`, and `query_warehouse` are preconfigured from account parameters and the current connection. This command does not apply to Native App projects. ## Syntax@@ -64,5 +64,5 @@ <dd> -Name of the Snowflake Apps Deploy to initialize. Defaults to the current directory name.+Name of the Snowflake App Runtime to initialize. Defaults to the current directory name. </dd>@@ -70,5 +70,5 @@ <dd> -Only print the resolved configuration values without writing snowflake.yml. Default: False.+Only print the resolved configuration values without writing app.yml. Default: False. </dd>@@ -314,21 +314,21 @@ ## Usage notes -The `snow app setup` command bootstraps a new Snowflake Apps Deploy project by generating a `snowflake.yml` file containing a `snowflake-app` entity. Edit `snowflake.yml` after the command completes, then run `snow app deploy` to ship your changes.--Starting with %sf-cli% version 3.17.0, `snow app` commands support both Snowflake Native Apps (`application` and `application package` entities) and Snowflake Apps Deploy (`snowflake-app` entities). Shared subcommands such as `bundle`, `deploy`, `validate`, `open`, `events`, and `teardown` select the correct flow automatically based on the entity type in `snowflake.yml`.+The `snow app setup` command bootstraps a new Snowflake App Runtime project by generating an `app.yml` file. Edit `app.yml` after the command completes, then run `snow app deploy` to ship your changes.++Starting with %sf-cli% version 3.17.0, `snow app` commands support both Snowflake Native Apps (`application` and `application package` entities) and Snowflake App Runtime (`snowflake-app` entities). Shared subcommands such as `bundle`, `deploy`, `validate`, `open`, `events`, and `teardown` select the correct flow automatically based on the entity type in the project file. ## Examples -- Initialize `snowflake.yml` for a Snowflake Apps Deploy project in the current directory:+- Initialize `app.yml` for a Snowflake App Runtime project in the current directory: ```snowcli snow app setup ``` - After running the command, edit `snowflake.yml` to configure your app, then deploy it:+ After running the command, edit `app.yml` to configure your app, then deploy it: ```snowcli snow app deploy ``` -- Show the resolved configuration without writing `snowflake.yml`:+- Show the resolved configuration without writing `app.yml`: ```snowcli snow app setup --dry-run
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（18行追加・0行削除）
--- ahttps://docs.snowflake.com/en/release-notes/clients-drivers/snowflake-cli-2026+++ bhttps://docs.snowflake.com/en/release-notes/clients-drivers/snowflake-cli-2026@@ -12,4 +12,22 @@ See [](/developer-guide/snowflake-cli/index) for documentation.++## Version 3.26.0 (Aug 31, 2026)++### New additions++- `snow connection test --enable-diag` now appends [SnowCD](https://docs.snowflake.com/en/user-guide/snowcd)-style per-endpoint connectivity checks (health, latency, certificate info, and an effective network policy summary) to the existing `SnowflakeConnectionTestReport.txt`. Stdout is unchanged. Pass `--print-diag` with `--enable-diag` to print that same report to stdout. Replaces the end-of-life SnowCD tool.+- `app.yml` (version 2) for Snowflake App Runtime projects is now generally available, and no longer needs a feature flag. `snow app setup` creates an `app.yml` for new projects. Existing `snowflake.yml` projects keep working as before.+- Git metadata support for `snow dbt deploy` is now available. `--git-commit` and `--git-branch` record the source commit and branch in the project's `last_deployed_from` metadata. These values will also be auto-detected from GitHub Actions environments if no explicit flags are specified.++### Fixes and improvements++- `snow app deploy` for Snowflake App Runtime projects now explains a failure while preparing code storage in terms of the statement that actually failed. A missing database or schema is reported as such instead of as a missing privilege, a privilege error names only the grant that statement needs, and a rejected stage encryption type is named explicitly.+- `snow app deploy` for Snowflake App Runtime projects no longer surfaces a raw connector traceback when uploading code fails. The error now names the stage or workspace being written to, how many files had already uploaded, and what to do next. Failed file transfers, which were previously not caught at all, are reported the same way.+- `snow helpers detect-encoding` now detects when the Windows console isn't configured for UTF-8 output (independent of the CLI's own encoding settings) and points the user at the fix — `chcp.com 65001` for cmd.exe/Git Bash, or the docs for PowerShell 5.x. The CLI's startup encoding warning surfaces the same note, but only when it isn't already warning about a Python encoding mismatch — run `snow helpers detect-encoding` for the full picture.+- `snow app deploy` for Snowflake App Runtime projects no longer needs OWNERSHIP on the code stage and CREATE STAGE on the schema to redeploy. The upload used to start by dropping the stage and creating it again, so a role holding only WRITE could deploy once and then never again — and a role allowed to drop the stage but not create one lost the stage entirely. The stage is now only dropped when the deploying role can also recreate it; otherwise its contents are cleared, with a warning that files deleted from the project since the last deploy may survive on the stage.+- Snowflake App Runtime projects now use temporary code storage by default. `snow app setup` leaves `code_stage`/`code_workspace` out of `app.yml`, and `snow app deploy` provisions a temporary `<app>_CODE` stage (or a `<app>_CODE` workspace for personal databases, which don't support stages) just for the build and drops it once the build finishes. Because the name is derived from the app, `--build-only` can still find and drop what `--upload-only` created. Set `code_stage` or `code_workspace` in `app.yml` to keep a persisted stage/workspace instead.+- Fixed `snow helpers check-version` failing with "Could not determine the latest Snowflake CLI version" when the local version cache file was corrupted. A corrupted or unreadable cache now falls back to a live network fetch instead of silently returning nothing.+- The passive new-version banner no longer blocks CLI startup. The version cache is refreshed in a background thread while the command runs, and the banner is shown after the command completes (including on `--help`, `--version`, and `--info`). ## Version 3.25.0 (Aug 24, 2026)
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（16行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/sql/alter-application+++ bhttps://docs.snowflake.com/en/sql-reference/sql/alter-application@@ -27,4 +27,5 @@ [ SHARE_EVENTS_WITH_PROVIDER = { TRUE | FALSE } ] [ DEBUG_MODE = { TRUE | FALSE } ]+ [ AUTHORIZE_RESTRICTED_PROVIDER_REMOTE_OPERATIONS_UNTIL = { '<timestamp>' | 'INDEFINITE' | 'NEVER' } ] ALTER APPLICATION [ IF EXISTS ] <name> UNSET@@ -32,4 +33,5 @@ [ SHARE_EVENTS_WITH_PROVIDER ] [ DEBUG_MODE ]+ [ AUTHORIZE_RESTRICTED_PROVIDER_REMOTE_OPERATIONS_UNTIL ] ALTER APPLICATION [ IF EXISTS ] <name> RENAME TO <new_app_name>@@ -111,4 +113,16 @@ Specifies whether to share logs and event data with the provider.++</dd>+<dt>`AUTHORIZE_RESTRICTED_PROVIDER_REMOTE_OPERATIONS_UNTIL = { '<timestamp>' | 'INDEFINITE' | 'NEVER' }`</dt>+<dd>++Specifies whether the provider can perform [restricted remote app operations](/developer-guide/native-apps/ui-consumer-remote-app-operation) on the app, such as the `run_sql` operation.++- `'<timestamp>'`: Authorizes the provider to perform restricted remote app operations until the specified timestamp.+- `'INDEFINITE'`: Authorizes the provider to perform restricted remote app operations indefinitely.+- `'NEVER'`: Revokes authorization for restricted remote app operations.++Default: `'NEVER'` </dd>@@ -142,4 +156,6 @@ Disables debug mode for the installed app. This clause is semantically the same as setting `DEBUG_MODE = FALSE`. - `SHARE_EVENTS_WITH_PROVIDER`+- `AUTHORIZE_RESTRICTED_PROVIDER_REMOTE_OPERATIONS_UNTIL`+ Revokes authorization for restricted provider remote app operations. This is semantically the same as setting `AUTHORIZE_RESTRICTED_PROVIDER_REMOTE_OPERATIONS_UNTIL = 'NEVER'`. - <code className="samp">TAG <em>tag_name</em> [ , <em>tag_name</em> ... ]</code> - <code className="samp">REFERENCES[ ( '<em>reference_name</em>' [, '<em>reference_alias</em>' ] ) ]</code>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（16行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-application+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-application@@ -32,4 +32,5 @@ [ [ WITH ] TAG ( <tag_name> = '<tag_value>' [ , ... ] ) ] [ AUTHORIZE_TELEMETRY_EVENT_SHARING = { TRUE | FALSE } ]+ [ AUTHORIZE_RESTRICTED_PROVIDER_REMOTE_OPERATIONS_UNTIL = { '<timestamp>' | 'INDEFINITE' | 'NEVER' } ] [ WITH FEATURE POLICY = <policy_name> ] @@ -40,4 +41,5 @@ [ [ WITH ] TAG ( <tag_name> = '<tag_value>' [, ...] ) ] [ AUTHORIZE_TELEMETRY_EVENT_SHARING = { TRUE | FALSE } ]+ [ AUTHORIZE_RESTRICTED_PROVIDER_REMOTE_OPERATIONS_UNTIL = { '<timestamp>' | 'INDEFINITE' | 'NEVER' } ] [ WITH FEATURE POLICY = <policy_name> ] @@ -48,4 +50,5 @@ [ [ WITH ] TAG ( <tag_name> = '<tag_value>' [ , ... ] ) ] [ AUTHORIZE_TELEMETRY_EVENT_SHARING = { TRUE | FALSE } ]+ [ AUTHORIZE_RESTRICTED_PROVIDER_REMOTE_OPERATIONS_UNTIL = { '<timestamp>' | 'INDEFINITE' | 'NEVER' } ] [ WITH FEATURE POLICY = <policy_name> ] @@ -56,4 +59,5 @@ [ BACKGROUND_INSTALL = { TRUE | FALSE } ] [ AUTHORIZE_TELEMETRY_EVENT_SHARING = { TRUE | FALSE } ]+ [ AUTHORIZE_RESTRICTED_PROVIDER_REMOTE_OPERATIONS_UNTIL = { '<timestamp>' | 'INDEFINITE' | 'NEVER' } ] [ WITH FEATURE POLICY = <policy_name> ] ```@@ -184,4 +188,16 @@ Enables [logging and event sharing](/developer-guide/native-apps/event-about) in the app.++</dd>+<dt>`AUTHORIZE_RESTRICTED_PROVIDER_REMOTE_OPERATIONS_UNTIL = { '<timestamp>' | 'INDEFINITE' | 'NEVER' }`</dt>+<dd>++Specifies whether the provider can perform [restricted remote app operations](/developer-guide/native-apps/ui-consumer-remote-app-operation) on the app, such as the `run_sql` operation.++- `'<timestamp>'`: Authorizes the provider to perform restricted remote app operations until the specified timestamp.+- `'INDEFINITE'`: Authorizes the provider to perform restricted remote app operations indefinitely.+- `'NEVER'`: Revokes authorization for restricted remote app operations.++Default: `'NEVER'` </dd>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（15行追加・1行削除）
--- ahttps://docs.snowflake.com/en/release-notes/preview-features+++ bhttps://docs.snowflake.com/en/release-notes/preview-features@@ -79,4 +79,11 @@ <tbody> <tr>+ <td>[Second generation Openflow](/user-guide/data-integration/openflow/gen2/index)</td>+ <td>Open</td>+ <td>August 2026</td>+ <td>[](/user-guide/data-integration/openflow/gen2/index)</td>+ <td>Gen 2 Openflow deployments, runtimes, and connectors are first-class Snowflake SQL objects with versioned connector configuration and standard RBAC. Supported connectors at Public Preview: PostgreSQL CDC, MySQL/MariaDB CDC. Migration from gen 1 to gen 2 is separately available in Private Preview.</td>+ </tr>+ <tr> <td>Stable egress IP addresses on Azure</td> <td>Open</td>@@ -114,4 +121,11 @@ <td>[](/user-guide/cleanrooms/custom-templates#label-dcr-template-preset-tables)</td> <td>Preset a specific dataset in a Collaboration Data Clean Rooms template with a `preset_tables` block, so the template always reads that dataset and the analysis runner doesn't supply it at run time.</td>+ </tr>+ <tr>+ <td>Remote app operations for Snowflake Native Apps</td>+ <td>Open</td>+ <td>August 2026</td>+ <td>[](/developer-guide/native-apps/remote-app-operation)</td>+ <td>Providers can perform on-demand operations on a consumer %native-app%, such as running SQL statements, disabling the app, enabling the app, or retrying an upgrade.</td> </tr> <tr>@@ -343,5 +357,5 @@ <td>Open</td> <td>June 2026</td>- <td>[](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime), [](/developer-guide/snowflake-app-runtime/getting-started)</td>+ <td>[](/developer-guide/snowflake-app-runtime/about-snowflake-app-runtime), [](/developer-guide/snowflake-app-runtime/getting-started), [](/developer-guide/snowflake-app-runtime/security)</td> <td>Build and deploy Node.js web applications (with a focus on Next.js) directly on Snowflake using Cortex Code or the Snowflake CLI. Describe an app in natural language, test it locally, and deploy to a live, SSO-backed URL. Python support is planned.</td> </tr>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（14行追加・0行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/dbt-commands/deploy+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/dbt-commands/deploy@@ -25,4 +25,6 @@ --install-local-deps --dbt-version <dbt_version>+ --git-commit <git_commit>+ --git-branch <git_branch> --connection <connection> --host <host>@@ -137,4 +139,16 @@ </dd>+<dt><code className="samp">--git-commit <em>TEXT</em></code></dt>+<dd>++Git commit hash to record in last_deployed_from metadata when deploying from a plain stage (e.g. SnowCLI temp stage). In GitHub Actions it is auto-detected when not provided.++</dd>+<dt><code className="samp">--git-branch <em>TEXT</em></code></dt>+<dd>++Git branch name to record in last_deployed_from metadata when deploying from a plain stage (e.g. SnowCLI temp stage). In GitHub Actions it is auto-detected when not provided.++</dd> <dt><code className="samp">--connection, -c, --environment <em>TEXT</em></code></dt> <dd>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（10行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/sql/desc-application+++ bhttps://docs.snowflake.com/en/sql-reference/sql/desc-application@@ -312,4 +312,14 @@ The type of release channel. Valid values are `QA`, `ALPHA`, `DEFAULT`. For more information, see [](/developer-guide/native-apps/release-channels).++</td>+ </tr>+ <tr>+ <td>`authorize_restricted_provider_remote_operations_until`</td>+ <td>++The timestamp until which the consumer has authorized the provider to perform+[restricted remote app operations](/developer-guide/native-apps/ui-consumer-remote-app-operation).+If authorized indefinitely, the value is `INDEFINITE`. If consent has not been granted, the value is `NEVER`. </td>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（7行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/account-usage+++ bhttps://docs.snowflake.com/en/sql-reference/account-usage@@ -214,4 +214,11 @@ <td>Historical</td> <td>24 hours</td>+ <td></td>+ <td>Data retained for 1 year.</td>+ </tr>+ <tr>+ <td>[APPLICATION_REMOTE_OPERATION_HISTORY](/sql-reference/account-usage/application_remote_operation_history)</td>+ <td>Historical</td>+ <td>1 hour</td> <td></td> <td>Data retained for 1 year.</td>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（7行追加・0行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/connection-commands/test-connection+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/connection-commands/test-connection@@ -14,4 +14,5 @@ ```console snow connection test+ --print-diag --connection <connection> --host <host>@@ -59,4 +60,10 @@ <dl>+<dt>`--print-diag`</dt>+<dd>++Print the full per-endpoint diagnostic to stdout. Without this flag, `--enable-diag` writes that diagnostic only to the report file. Default: False.++</dd> <dt><code className="samp">--connection, -c, --environment <em>TEXT</em></code></dt> <dd>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（0行追加・7行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/deploy+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/snowflake-app-runtime-commands/deploy@@ -27,5 +27,4 @@ --build-only --promote-only- --provision-certs --target <target> --connection <connection>@@ -81,10 +80,4 @@ </dd>-<dt>`--provision-certs`</dt>-<dd>--(Snowflake App Runtime only) When deploying a CNG (serverless) app whose account has no per-account URL certificate yet, trigger certificate provisioning automatically instead of only printing the system-function command. Provisioning is asynchronous (up to ~3 hours); the deploy still stops so it can be re-run once provisioning completes. Default: False.--</dd> <dt><code className="samp">--target <em>TEXT</em></code></dt> <dd>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（6行追加・0行削除）
--- ahttps://docs.snowflake.com/en/release-notes/clients-drivers/monthly-releases+++ bhttps://docs.snowflake.com/en/release-notes/clients-drivers/monthly-releases@@ -78,4 +78,10 @@ <tr> <td>%snowflake-cli-rn%</td>+ <td>3.26.0</td>+ <td>31-Aug-2026</td>+ <td></td>+ </tr>+ <tr>+ <td>%snowflake-cli-rn%</td> <td>3.25.0</td> <td>24-Aug-2026</td>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・1行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/access-control+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/access-control@@ -185,3 +185,6 @@ For general RBAC concepts, see-[](/user-guide/security-access-control-overview).+[](/user-guide/security-access-control-overview). For administrator guidance on+managing the risks that applications introduce (including caller grant+restrictions, feature policies, and external access controls), see+[Securing Snowflake App Runtime applications](/developer-guide/snowflake-app-runtime/security).
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（2行追加・2行削除）
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/about-openflow-connectors+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/about-openflow-connectors@@ -146,6 +146,6 @@ </tr> <tr>- <td>[Openflow Connector for SQL Server](/user-guide/data-integration/openflow/connectors/sql-server/about)</td>- <td>CDC replication of Microsoft SQL Server data with Snowflake for comprehensive, centralized reporting</td>+ <td>[Openflow Connector for SQL Server (CT)](/user-guide/data-integration/openflow/connectors/sql-server/about)</td>+ <td>Change tracking replication of Microsoft SQL Server data with Snowflake for comprehensive, centralized reporting</td> </tr> <tr>
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/shopify/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/shopify/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/veeva-vault/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/veeva-vault/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kafka/kafka-json-avro+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kafka/kafka-json-avro@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kafka/kafka-dlq-metadata+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kafka/kafka-dlq-metadata@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server-cdc/compare-change-tracking-cdc+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server-cdc/compare-change-tracking-cdc@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/streaming/configuring-avro-data-type-ingestion+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/streaming/configuring-avro-data-type-ingestion@@ -3,7 +3,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/streaming/configuring-custom-transformations+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/streaming/configuring-custom-transformations@@ -3,7 +3,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/streaming/configuring-dead-letter-queue-handling+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/streaming/configuring-dead-letter-queue-handling@@ -3,7 +3,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/streaming/configuring-private-key-authentication+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/streaming/configuring-private-key-authentication@@ -3,7 +3,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/streaming/configuring-protobuf-data-type-ingestion+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/streaming/configuring-protobuf-data-type-ingestion@@ -3,7 +3,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/mongodb/connect+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/mongodb/connect@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kinesis/maintenance+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kinesis/maintenance@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/shopify/maintain+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/shopify/maintain@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/jira-cloud/migrate-from-legacy+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/jira-cloud/migrate-from-legacy@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/salesforce-bulk-api/monitor+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/salesforce-bulk-api/monitor@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/shopify/object-definitions+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/shopify/object-definitions@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kinesis/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kinesis/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kinesis/configuring-dead-letter-queue-handling+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kinesis/configuring-dead-letter-queue-handling@@ -3,7 +3,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/mysql/data-mapping+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/mysql/data-mapping@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/mysql/incremental-replication+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/mysql/incremental-replication@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/oracle/setup-oracledb+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/oracle/setup-oracledb@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/oracle/data-mapping+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/oracle/data-mapping@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/oracle/manage-commercial-terms+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/oracle/manage-commercial-terms@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/oracle/maintenance+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/oracle/maintenance@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/oracle/incremental-replication+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/oracle/incremental-replication@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/oracle/setup-snowflake+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/oracle/setup-snowflake@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/postgres/data-mapping+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/postgres/data-mapping@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/meta-ads/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/meta-ads/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/dataverse/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/dataverse/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/mongodb/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/mongodb/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sharepoint/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sharepoint/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/shopify/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/shopify/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kinesis/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kinesis/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/oracle/setup-tasks+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/oracle/setup-tasks@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/jira-cloud/setup-agile+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/jira-cloud/setup-agile@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/jira-cloud/setup-core+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/jira-cloud/setup-core@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/amazon-ads/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/amazon-ads/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/box/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/box/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/google-ads/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/google-ads/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/google-drive/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/google-drive/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/google-sheets/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/google-sheets/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/hubspot/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/hubspot/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/jira-cloud/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/jira-cloud/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kafka/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kafka/setup@@ -7,7 +7,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/amazon-ads/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/amazon-ads/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/box/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/box/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/google-ads/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/google-ads/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/google-drive/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/google-drive/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/google-sheets/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/google-sheets/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/hubspot/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/hubspot/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/jira-cloud/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/jira-cloud/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/linkedin-ads/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/linkedin-ads/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/meta-ads/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/meta-ads/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/dataverse/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/dataverse/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/oracle/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/oracle/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sharepoint/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sharepoint/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/slack/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/slack/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/snowflake-to-kafka/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/snowflake-to-kafka/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server-cdc/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server-cdc/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/workday/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/workday/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/google-big-query/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/google-big-query/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/mongodb/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/mongodb/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/salesforce-bulk-api/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/salesforce-bulk-api/about@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/oracle/troubleshoot+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/oracle/troubleshoot@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/salesforce-bulk-api/troubleshoot+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/salesforce-bulk-api/troubleshoot@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/google-big-query/use+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/google-big-query/use@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/mongodb/use+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/mongodb/use@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/veeva-vault/use+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/veeva-vault/use@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/postgres/failover+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/postgres/failover@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/postgres/incremental-replication+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/postgres/incremental-replication@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/salesforce-bulk-api/configure-connector+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/salesforce-bulk-api/configure-connector@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/salesforce-bulk-api/formula-fields+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/salesforce-bulk-api/formula-fields@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/salesforce-bulk-api/setup-salesforce+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/salesforce-bulk-api/setup-salesforce@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/salesforce-bulk-api/setup-snowflake+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/salesforce-bulk-api/setup-snowflake@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server-cdc/maintenance+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server-cdc/maintenance@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server-cdc/incremental-replication+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server-cdc/incremental-replication@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server/maintenance+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server/maintenance@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server/incremental-replication+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server/incremental-replication@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server/data-mapping+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server/data-mapping@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kinesis/performance-tuning+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kinesis/performance-tuning@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kafka/performance-tuning+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kafka/performance-tuning@@ -7,7 +7,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/linkedin-ads/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/linkedin-ads/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/slack/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/slack/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/snowflake-to-kafka/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/snowflake-to-kafka/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/workday/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/workday/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/google-big-query/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/google-big-query/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/veeva-vault/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/veeva-vault/setup@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kafka/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kafka/about@@ -3,7 +3,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kafka/aws-msk-iam-auth+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kafka/aws-msk-iam-auth@@ -3,7 +3,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kafka/configuring-dead-letter-queue-handling+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kafka/configuring-dead-letter-queue-handling@@ -3,7 +3,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kafka/mtls-auth+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kafka/mtls-auth@@ -3,7 +3,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/shopify/troubleshoot+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/shopify/troubleshoot@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kinesis/troubleshoot+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/kinesis/troubleshoot@@ -5,7 +5,7 @@ Snowflake connectors are supported in every region where Snowflake Openflow is available. +[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions.+ [Snowflake Openflow on BYOC deployments](/user-guide/data-integration/openflow/about-byoc) are available to all accounts in AWS Commercial Regions only ([](#label-na-general-regions)).--[Openflow Snowflake deployments](/user-guide/data-integration/openflow/about-spcs) are available to all accounts in AWS, Azure, and GCP Commercial Regions. This connector is subject to the [Snowflake Connector Terms](https://www.snowflake.com/legal/snowflake-connector-terms/).
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/tables-iceberg-data-types+++ bhttps://docs.snowflake.com/en/user-guide/tables-iceberg-data-types@@ -513,5 +513,5 @@ ``` -##### nanosecond timestamps+##### Nanosecond timestamps The following example creates a managed Iceberg table with nanosecond timestamps:
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/sql/alter-oflow-data-plane+++ bhttps://docs.snowflake.com/en/sql-reference/sql/alter-oflow-data-plane@@ -94,4 +94,4 @@ ALTER OPENFLOW DATA PLANE INTEGRATION OPENFLOW_DATAPLANE_63600E17_5D91_4C56_BFC8_54FA0AXXXXXX- SET EVENT_TABLE = 'openflow.openflow.openflow_events';+ SET EVENT_TABLE = 'openflow_db.openflow_schema.openflow_events'; ```
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-catalog-integration-delta-sharing+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-catalog-integration-delta-sharing@@ -12,6 +12,4 @@ # CREATE CATALOG INTEGRATION (Delta Sharing)--Available to all accounts. - [](/user-guide/tables-iceberg)
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-search/cortex-search-agents+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-search/cortex-search-agents@@ -79,5 +79,5 @@ ``` -For full configuration options including filters, multi-index services, and UI setup, see [Configure and interact with Agents](/user-guide/snowflake-cortex/cortex-agents-manage).+For full configuration options including filters, multi-index services, and UI setup, see [Configure and interact with agents](/user-guide/snowflake-cortex/cortex-agents-manage). ## Analytical search
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/account-admin-setup+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/account-admin-setup@@ -160,3 +160,4 @@ - [](/developer-guide/snowflake-app-runtime/privileges): privileges for deploy, sharing, and operations - [](/developer-guide/snowflake-app-runtime/access-control): grant `USAGE`, `OPERATE`, and `MONITOR` on deployed apps+- [](/developer-guide/snowflake-app-runtime/security): caller grant restrictions, feature policies, and external access controls - [](/developer-guide/snowflake-app-runtime/limitations): public preview limits
| セクション | S | A | B | C | 計 |
|---|---|---|---|---|---|
| Loading & Unloading Data | 0 | 12 | 8 | 94 | 114 |
| Snowflake CLI | 0 | 0 | 5 | 0 | 5 |
| SQL Commands | 0 | 0 | 3 | 2 | 5 |
| Release Notes | 0 | 0 | 4 | 0 | 4 |
| Cortex Code | 0 | 1 | 2 | 0 | 3 |
| User Guide | 0 | 1 | 0 | 1 | 2 |
| Developer Guide | 0 | 0 | 1 | 1 | 2 |
| Account Usage | 0 | 0 | 1 | 0 | 1 |
| Snowflake Cortex (AI & ML) | 0 | 0 | 0 | 1 | 1 |