SNOWFLAKE DOCS DIFF
2026-08-25 は全8439ページ中45ページが改訂され、削除はありませんでした。重要度Aの仕様変更が5件あり、特に Snowflake CLI、App Runtime、CLI設定、dbtチュートリアル、MFA運用に更新が集中しています。重要度Bも22件あり、実質的な機能・手順の更新が一定数発生しました。破壊的変更はなく、全体としては利用開始手順と開発・運用設定の現行化が中心です。
snow connection test で確認する手順へ変更されました。process.env から接続先やApplication Service情報を取得できるようになりました。use_mixin から use_mixins に変更され、mixinの利用例も拡充されました。チュートリアルのコマンドラインクライアントが SnowSQL から Snowflake CLI（%sf-cli%） に置き換わり、インストール手順も変更されました。事前に接続を設定し、snowsql -a <account_identifier> -u <user_name> の実行とパスワード入力ではなく、snow connection test で接続を確認してから SQL を実行する流れになっています。
影響: 実務では、チュートリアルに従う利用者は Snowflake CLI のインストール と 接続設定 が必要になり、従来の SnowSQL の起動パラメータや認証手順はこのページの記載から削除されています。
判定根拠: SQL 構文/コードブロックの増減 (+17/-8)
--- ahttps://docs.snowflake.com/en/user-guide/tutorials/snowflake-in-20minutes+++ bhttps://docs.snowflake.com/en/user-guide/tutorials/snowflake-in-20minutes@@ -3,5 +3,5 @@ ## Introduction -This tutorial uses the Snowflake command-line client, [SnowSQL](/user-guide/snowsql), to introduce key concepts and tasks, including:+This tutorial uses the Snowflake command-line client, [%sf-cli%](/developer-guide/snowflake-cli/index), to introduce key concepts and tasks, including: - Creating Snowflake objects—You create a database and a table for storing data.@@ -22,7 +22,7 @@ - Create Snowflake objects—You create a database and a table for storing data.-- Install SnowSQL—You install and use SnowSQL, the Snowflake command-line query tool.-- Users of Visual Studio Code might consider using the [](/user-guide/vscode-ext) instead of SnowSQL.+- Install %sf-cli%—You install and use %sf-cli%, the Snowflake command-line client.++ Users of Visual Studio Code might consider using the [](/user-guide/vscode-ext) instead of a command-line client. - Load CSV data files—You use various mechanisms to load data into tables from CSV files.@@ -35,5 +35,5 @@ This tutorial requires a database, table, and virtual warehouse to load and query data. Creating these Snowflake objects requires a Snowflake user with a role with the-necessary access control privileges. In addition, [SnowSQL](/user-guide/snowsql)+necessary access control privileges. In addition, [%sf-cli%](/developer-guide/snowflake-cli/index) is required to execute the SQL statements in the tutorial. Lastly, the tutorial requires CSV files that contain sample data to load. @@ -54,9 +54,13 @@ Users with the ACCOUNTADMIN or SECURITYADMIN role can create users. -2. Install SnowSQL-- To install SnowSQL, see [](/user-guide/snowsql-install-config).--3. Download sample data files+2. Install %sf-cli%++ To install %sf-cli%, see [](/developer-guide/snowflake-cli/installation/installation).++3. Configure a connection++ Before you can run SQL, define a connection to your Snowflake account. See [](/developer-guide/snowflake-cli/connecting/connect).++4. Download sample data files For this tutorial you download sample employee data files in CSV format that Snowflake provides.@@ -83,56 +87,76 @@ <a id="label-tutorial-snowflake-in-20-mins-login"></a> -## Log in to SnowSQL--After you have [SnowSQL](/user-guide/snowsql), start SnowSQL to connect to Snowflake:+## Run SQL with %sf-cli%++After you have installed %sf-cli% and [configured a connection](/developer-guide/snowflake-cli/connecting/connect), confirm the connection, then run SQL. 1. Open a command-line window.-2. Start SnowSQL:-- ```bash- $ snowsql -a <account_identifier> -u <user_name>+2. Confirm the connection:++ ```snowcli+ snow connection test ``` - Where:-- --- <dl>- <dt>`<account_identifier>` is the unique identifier for your Snowflake account.</dt>- <dd>-- The preferred format of the [account identifier](/user-guide/admin-account-identifier) is as follows:--- <dl>- <dt><code className="samp"><em>organization_name</em>-<em>account_name</em></code></dt>- <dd>-- Names of your Snowflake organization and account. For more information, see [](#label-account-name).-- </dd>- </dl>-- If you don't know your account identifier, see [](#label-account-name-find).-- </dd>- </dl>-- - `<user_name>` is the login name for your Snowflake user.--- If your account has an identity provider (IdP) that has been defined for your account, you can use a web browser to authenticate instead of a password, as the following example demonstrates:-- ```bash- $ snowsql -a <account_identifier> -u <user_name> --authenticator externalbrowser- ```--- For more information, see [](#label-snowsql-web-browser-sso).--3. When SnowSQL prompts you, enter the password for your Snowflake user.--If you log in successfully, SnowSQL displays a command prompt that includes-your current warehouse, database, and schema.+ This command uses your default connection. To use a named connection, add `-c <connection_name>`. A successful test reports `Status` as `OK`.++ If you have not defined a connection yet, see [](/developer-guide/snowflake-cli/connecting/configure-connections).++ If your account uses an identity provider (IdP), configure the connection for browser-based authentication first. See [Use an external browser](/developer-guide/snowflake-cli/connecting/configure-connections#label-snowcli-externalbrowser).++3. When the client prompts you, complete any remaining authentication steps, such as entering your password or approving MFA.++You can run SQL statements in any of these ways:++- Pass a SQL string (`snow sql -q`)+- Run statements from a file (`snow sql -f`)+- Enter statements in interactive mode (`snow sql`)++This tutorial uses `snow sql -q` so you can copy each step and get a result.++### Pass a SQL string++Use `-q` to pass one or more statements as a string. End each statement with a semicolon (`;`):++```snowcli+snow sql -q "SELECT CURRENT_USER();"+```++To run several statements in one command:++```snowcli+snow sql -q "SELECT CURRENT_USER(); SELECT CURRENT_VERSION();"+```++### Run SQL from a file++Save one or more statements in a file, then pass the path with `-f`. For example, save the following statements in `queries.sql`:++```sql+SELECT CURRENT_USER();+SELECT CURRENT_VERSION();+```++```snowcli+snow sql -f queries.sql+```++### Interactive mode++To enter SQL one statement at a time, run `snow sql` with no `-q` or `-f`:++```snowcli+snow sql+```++At the `>` prompt, enter a statement and press ENTER. End each statement with a semicolon (`;`). To leave interactive mode, enter `exit`, `quit`, or `CTRL-D`:++```text+> SELECT CURRENT_USER();+> exit+```++Each `snow sql -q` or `snow sql -f` invocation is a new session. After you create the database and warehouse in the next step, later commands pass `--database sf_tuts` and `--warehouse sf_tuts_wh` so they use those objects. You can also set `database` and `warehouse` in your `connections.toml` file instead of passing those options on every command. For more information, see [](/developer-guide/snowflake-cli/connecting/configure-connections).++Interactive mode keeps one session until you exit. If you get locked out of the account and can't obtain the account identifier, you can find it in the Welcome email that Snowflake sent to@@ -142,18 +166,5 @@ in the Welcome email. -If your Snowflake user doesn't have a default warehouse, database, and schema, or if-you didn't configure SnowSQL to specify a default warehouse, database, and schema,-the prompt displays `no warehouse`, `no database`, and `no schema`. For example:--```-user-name#(no warehouse)@(no database).(no schema)>-```--This prompt indicates that there is no warehouse, database, and schema-selected for the current session. You create these objects-in the next step. As you follow the next steps in this tutorial to create-these objects, the prompt automatically updates to include the names of these objects.--For more information, see [](/user-guide/snowsql-start).+For more information about executing SQL, including interactive mode, see [](/developer-guide/snowflake-cli/sql/execute-sql). <a id="label-tutorial-snowflake-in-20-mins-create-snowflake-objects"></a>@@ -172,19 +183,11 @@ ### Create a database -Create the `sf_tuts` database using the [](/sql-reference/sql/create-database) command:--```sql-CREATE OR REPLACE DATABASE sf_tuts;+Create the `sf_tuts` database using the [](/sql-reference/sql/create-database) command. Both statements run in the same invocation, so the context functions see the database you just created:++```snowcli+snow sql -q "CREATE OR REPLACE DATABASE sf_tuts; SELECT CURRENT_DATABASE(), CURRENT... (truncated)
差分が長いため、途中まで表示しています。
Built-in environment variables の説明が追加され、アプリケーションコンテナに PORT、HOSTNAME、SNOWFLAKE_ACCOUNT、SNOWFLAKE_HOST、SNOWFLAKE_DATABASE、SNOWFLAKE_SCHEMA、SNOWFLAKE_SERVICE_NAME、SNOWFLAKE_HOME などが設定されるようになりました。SNOWFLAKE_DATABASE、SNOWFLAKE_SCHEMA、SNOWFLAKE_SERVICE_NAME は Application Service の完全修飾名を構成し、app.yml の environment_variables で同名変数を指定した場合はユーザー指定値が優先されます。
影響: アプリケーションは process.env から Snowflake の接続先や Application Service 情報を取得できますが、値はサービス作成・更新や再デプロイなどの契機で更新され、実行中サービスには直ちに反映されません。
判定根拠: SQL 構文/コードブロックの増減 (+2/-0)
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/getting-started+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/getting-started@@ -448,4 +448,116 @@ [](/developer-guide/snowpark-container-services/tutorials/advanced/tutorial-7-callers-rights). +<a id="label-getting-started-builtin-env-vars"></a>++### Built-in environment variables++Snowflake sets the following built-in environment variables in your+application container:++<div className="colwidths-given">++ <colgroup>+ <col style={{ width: "40.0%" }} />+ <col style={{ width: "60.0%" }} />+ </colgroup>+ <thead>+ <tr>+ <th>Environment variable</th>+ <th>Value</th>+ </tr>+ </thead>+ <tbody>+ <tr>+ <td>+ <code>PORT</code>+ </td>+ <td>Port your application must listen on</td>+ </tr>+ <tr>+ <td>+ <code>HOSTNAME</code>+ </td>+ <td>Hostname your application must listen on</td>+ </tr>+ <tr>+ <td>+ <code>SNOWFLAKE_ACCOUNT</code>+ </td>+ <td>Name of the account</td>+ </tr>+ <tr>+ <td>+ <code>SNOWFLAKE_HOST</code>+ </td>+ <td>Hostname for the Snowflake account</td>+ </tr>+ <tr>+ <td>+ <code>SNOWFLAKE_PORT</code>+ </td>+ <td>+ Port for the Snowflake account connection. Snowflake sets this+ variable only when the port is greater than 0.+ </td>+ </tr>+ <tr>+ <td>+ <code>SNOWFLAKE_PROTOCOL</code>+ </td>+ <td>+ Protocol for the Snowflake account connection. Snowflake sets this+ variable only when the protocol isn't <code>https</code>.+ </td>+ </tr>+ <tr>+ <td>+ <code>SNOWFLAKE_DATABASE</code>+ </td>+ <td>Database that contains the Application Service</td>+ </tr>+ <tr>+ <td>+ <code>SNOWFLAKE_SCHEMA</code>+ </td>+ <td>Schema that contains the Application Service</td>+ </tr>+ <tr>+ <td>+ <code>SNOWFLAKE_SERVICE_NAME</code>+ </td>+ <td>Name of the Application Service</td>+ </tr>+ <tr>+ <td>+ <code>SNOWFLAKE_HOME</code>+ </td>+ <td>Mount root of the application</td>+ </tr>+ </tbody>++</div>++The values of `SNOWFLAKE_DATABASE`, `SNOWFLAKE_SCHEMA`, and+`SNOWFLAKE_SERVICE_NAME` are the unquoted identifiers of the Application+Service object. Together, they compose the fully qualified name of the+Application Service+(`SNOWFLAKE_DATABASE.SNOWFLAKE_SCHEMA.SNOWFLAKE_SERVICE_NAME`).++These names aren't reserved. If you set the same name under+[`environment_variables`](/developer-guide/snowflake-app-runtime/app-yml#label-snowflake-apps-manifest-environment-variables)+in `app.yml`, your value takes precedence. Snowflake fills the variable only when+you don't set it.++Snowflake refreshes these values when it creates or upgrades the Application+Service, redeploys it, or changes settings such as auto-suspend. An+already-running service keeps its previous environment until one of those+operations runs.++```javascript+const database = process.env.SNOWFLAKE_DATABASE;+const schema = process.env.SNOWFLAKE_SCHEMA;+const serviceName = process.env.SNOWFLAKE_SERVICE_NAME;+```+ <a id="label-getting-started-other-cli-commands"></a>
mixin を使わずに stage と artifacts を各エンティティへ重複記述する例と、共有値を一度だけ定義して meta.use_mixins で適用する例が追加されました。また、パラメータ名が use_mixin から use_mixins に変更されました。
影響: 複数の mixin を利用する設定では、従来の use_mixin ではなく use_mixins を指定する必要があります。
判定根拠: SQL 構文/コードブロックの増減 (+4/-0)
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/project-definitions/specify-entities+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/project-definitions/specify-entities@@ -76,4 +76,47 @@ Mixin values are overridden by explicitly-declared entity attributes. +Without a mixin, you copy the same `stage` and `artifacts` onto every entity:++```yaml+definition_version: 2+entities:+ my_function:+ type: function+ stage: my_stage+ artifacts:+ - app/+ ...+ my_procedure:+ type: procedure+ stage: my_stage+ artifacts:+ - app/+ ...+```++A mixin lets you declare those shared values once and apply them with `meta.use_mixins`:++```yaml+definition_version: 2+mixins:+ snowpark_shared:+ stage: my_stage+ artifacts:+ - app/+entities:+ my_function:+ type: function+ ...+ meta:+ use_mixins:+ - snowpark_shared+ my_procedure:+ type: procedure+ ...+ meta:+ use_mixins:+ - snowpark_shared+```+ The following example includes two mixins: `stage_mixin` and `snowpark_shared`. The `my_dashboard` entity uses only `stage_mixin`, while the `my_function` entity uses both of the mixins. @@ -115,5 +158,5 @@ foo: meta:- use_mixin:+ use_mixins: - mixin_1 - mixin_2
ウェアハウス作成時に AUTO_SUSPEND = 60 を追加し、初回のソースデータ作成後は WAREHOUSE_SIZE = SMALL にリサイズする手順を追加しました。また、dbt タスクの実行頻度を毎時から 12時間ごと（Cron 1 */12 * * *）へ変更し、クリーンアップではタスクの停止・削除も対象にしています（具体的なSQLはdiffからは詳細不明）。
影響: 初回セットアップ後のウェアハウスを小さくし、タスクを12時間間隔にすることで、クレジット消費の削減と実行頻度の低下が見込まれます。
判定根拠: SQL 構文/コードブロックの増減 (+7/-2)
--- ahttps://docs.snowflake.com/en/user-guide/tutorials/dbt-projects-on-snowflake-getting-started-tutorial+++ bhttps://docs.snowflake.com/en/user-guide/tutorials/dbt-projects-on-snowflake-getting-started-tutorial@@ -50,10 +50,10 @@ A dedicated warehouse assigned to your workspace can help you log, trace, and identify actions initiated from within that workspace. In this tutorial, we use a warehouse named TASTY_BYTES_DBT_WH. Alternatively, you can use an existing warehouse in your account. For more information about creating a warehouse, see [](#label-warehouse-create). -The Tasty Bytes data model that you create for source data is fairly large, so we recommend using an XL warehouse.+The Tasty Bytes data model that you create for source data is fairly large, so we recommend using an XL warehouse for that one-time setup. Snowflake warehouses bill for the time they are running, including idle time before auto-suspend. After you finish creating the source data, you can resize the warehouse to SMALL for compiling, running, and scheduling the dbt project. To create a warehouse, run the following SQL command: ```sql-CREATE WAREHOUSE tasty_bytes_dbt_wh WAREHOUSE_SIZE = XLARGE;+CREATE WAREHOUSE tasty_bytes_dbt_wh WAREHOUSE_SIZE = XLARGE AUTO_SUSPEND = 60; ``` @@ -234,4 +234,10 @@ `tasty_bytes_dbt_db setup is now complete` +5. After the source data is created, resize the warehouse to SMALL:++ ```sql+ ALTER WAREHOUSE tasty_bytes_dbt_wh SET WAREHOUSE_SIZE = SMALL;+ ```+ <a id="label-dbt-get-started-enable-logging-tracing-metrics"></a> @@ -421,10 +427,10 @@ Now that you have deployed your dbt project object, you can use the workspace or SQL to set up a task that executes a dbt command on your dbt project object. -The following steps set up a schedule to execute the dbt project object every hour at one minute after the hour. The task executes the dbt `run` command with the `--select` option to run the `customer_loyalty_metrics` model in the dbt project.+The following steps set up a schedule to execute the dbt project object every 12 hours at one minute after the hour. The task executes the dbt `run` command with the `--select` option to run the `customer_loyalty_metrics` model in the dbt project. 1. From the dbt project menu on the right side of the project pane, choose **Create schedule**. 2. In the **Schedule a dbt run** dialog box, do the following: - For **Schedule name**, enter a name for the task; for example, *run_prepped_data_dbt*.- - For **Frequency**, leave **Hourly** at **01** for your time zone selected.+ - For **Frequency**, select **Custom**, and then enter the Cron expression `1 */12 * * *` for your time zone selected. - Under **dbt properties**: - For **Operation**, select **run**.@@ -443,5 +449,5 @@ CREATE OR REPLACE TASK tasty_bytes_dbt_db.dev.run_prepped_data_dbt WAREHOUSE=tasty_bytes_dbt_wh- SCHEDULE ='USING CRON 1 * * * * America/Los_Angeles'+ SCHEDULE ='USING CRON 1 */12 * * * America/Los_Angeles' AS EXECUTE DBT PROJECT tasty_bytes_dbt_project ARGS='run --select customer_loyalty_metrics --target dev';@@ -452,9 +458,14 @@ ## Clean up -You can delete the databases, workspaces, and warehouse that you created to clean up after this tutorial.--Run the following SQL commands from your `dbt_sandbox.sql` worksheet to remove the warehouse, the TASTY_BYTES_DBT_DB and TB_101 databases that you created, and all schemas and objects created in the databases:--```sql+To minimize credit consumption, you can delete the task, databases, workspaces, and warehouse that you created.++Run the following SQL commands from your `dbt_sandbox.sql` worksheet to suspend and remove the task, and to remove the warehouse, the TASTY_BYTES_DBT_DB and TB_101 databases that you created, and all schemas and objects created in the databases:++```sql+-- If you want to keep this setup, suspend the task to stop scheduled runs:+ALTER TASK IF EXISTS tasty_bytes_dbt_db.dev.run_prepped_data_dbt SUSPEND;++-- If you want to remove this setup, drop the task, warehouse, and databases:+DROP TASK IF EXISTS tasty_bytes_dbt_db.dev.run_prepped_data_dbt; DROP WAREHOUSE IF EXISTS tasty_bytes_dbt_wh; DROP DATABASE IF EXISTS tasty_bytes_dbt_db;
MFA キャッシュ有効化手順に、ALTER ACCOUNT SET ALLOW_CLIENT_MFA_CACHING = TRUE; の SQL 例と、authenticator = "USERNAME_PASSWORD_MFA" を含む config.toml の設定例が追加された。さらに、キャッシュ済みトークンの有効期限まで後続の snow コマンドで MFA 承認を再利用する動作と、Linux では keyring などの Secret Service バックエンドによる安全な認証情報保存が必要であることが明記された。
影響: 設定例に従えば MFA プロンプトの繰り返しを減らせるが、Linux では secure credential storage がない場合、毎回の接続で MFA を求められる。
判定根拠: SQL 構文/コードブロックの増減 (+5/-0)
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/connecting/configure-connections+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/connecting/configure-connections@@ -570,6 +570,27 @@ To enable MFA caching: -1. For your account, set `ALLOW_CLIENT_MFA_CACHING = true`.-2. In your `config.toml` file, add `authenticator = "USERNAME_PASSWORD_MFA"` to your connection.+1. For your account, set `ALLOW_CLIENT_MFA_CACHING = true`:++ ```sql+ ALTER ACCOUNT SET ALLOW_CLIENT_MFA_CACHING = TRUE;+ ```++2. In your `config.toml` file, add `authenticator = "USERNAME_PASSWORD_MFA"` to your connection:++ ```toml+ [connections.myconnection]+ account = "my_account"+ user = "jdoe"+ password = "my_password"+ authenticator = "USERNAME_PASSWORD_MFA"+ ```++With MFA caching enabled, you approve the MFA prompt once, and subsequent `snow` commands reuse the+cached token until it expires. Without it, every `snow` command that opens a new connection issues a+new MFA prompt.++On Linux, token caching also requires secure credential storage, such as keyring with a Secret+Service backend. Without it, you are prompted on every connection even when the account parameter+and the connection are both configured as described. For more information, see [](#label-mfa-token-caching).
2026年8月20日のリリースとして、Control Plane Core 0.129.0 など複数コンポーネントのセキュリティ修正・依存関係更新を追加しました。主な実質変更は、ランタイム診断バンドルのダウンロードに OWNERSHIP 権限を必須化し、Snowpipe Streaming v2 有効時に DB CDC コネクタを小規模ランタイムへデプロイ可能にしたことです。ほかにランタイム再起動、AWS デプロイ作成・削除、UI のキーボード操作に関する不具合修正と、既存記述の表記・句読点調整があります。 影響: 診断バンドルの取得には OWNERSHIP 権限が必要となり、Snowpipe Streaming v2 を使う DB CDC では小規模ランタイムを選択できるようになります。
変更内容: 本文を更新（58行追加・5行削除）
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/version-history+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/version-history@@ -254,4 +254,57 @@ </div> +## August 20, 2026++<a id="label-control-plane-core-0-129-0"></a>++### Control Plane Core 0.129.0++- Security patches and dependency upgrades.+- Tightened permissions on runtime diagnostic bundle download: OWNERSHIP privilege is now required.+- DB CDC connectors can now be deployed on small runtimes with Snowpipe Streaming v2 enabled.+- Fixed a rare issue where a Runtime restart could show success before all pods were healthy.++<a id="label-data-plane-service-0-129-0"></a>++### Data Plane Service 0.129.0++- Security patches and dependency upgrades.+- Fixed a rare issue where a Runtime restart could show success before all pods were healthy.++<a id="label-control-plane-ui-0-88-0"></a>++### Control Plane UI 0.88.0++- Security patches and dependency upgrades.+- Fixed keyboard usability for searchable select controls with grouped options.++<a id="label-runtime-operator-0-74-0"></a>++### Runtime Operator 0.74.0++- Security patches and dependency upgrades.++<a id="label-ingress-controller-2026-8-18-17"></a>++### Ingress Controller 2026.8.18-17++- Security patches and dependency upgrades.++<a id="label-spcs-data-plane-agent-1-45-0"></a>++### SPCS Data Plane Agent 1.45.0++- Security patches and dependency upgrades.++<a id="label-aws-data-plane-agent-1-61-0"></a>++### AWS Data Plane Agent 1.61.0++- Security patches and dependency upgrades.+- Fixed an intermittent deployment creation failure caused by IAM role availability+ delays due to eventual consistency.+- Fixed a rare deployment deletion failure that occurred when Custom Resource+ Definitions (CRDs) were absent at destroy time.+ ## August 18, 2026 @@ -672,5 +725,5 @@ - Fix alignment in Create Endpoint Target form.-- Enhancements and usability improvements for Gen2 Connectors and Runtimes (Private Preview).+- Enhancements and usability improvements for Gen 2 Connectors and Runtimes (Private Preview). <a id="label-aws-data-plane-agent-1-55-0"></a>@@ -989,5 +1042,5 @@ - Security patches and dependency upgrades.-- 2nd Gen Connectors — You can now use secrets stored in AWS Secrets Manager (through Snowflake) for connector credentials.+- Gen 2 Connectors: You can now use secrets stored in AWS Secrets Manager (through Snowflake) for connector credentials. <a id="label-runtime-extensions-2026-6-30-15"></a>@@ -1051,5 +1104,5 @@ - Enabled Gen 2 connector troubleshooting workflow using NiFi troubleshooting mode. - Connector deletion now purges NiFi queues and drains active processing before removing resources.-- Improved support for installing Gen 1 connectors for users with many roles+- Improved support for installing Gen 1 connectors for users with many roles. - Security patches and dependency upgrades. @@ -1290,5 +1343,5 @@ - CDC PostgreSQL: Added WAL level validation during connector setup with clearer error messages when the replication level is insufficient.-- CDC MySQL: Added a TableStorageFormat configuration option to the Gen2 MySQL Connector for+- CDC MySQL: Added a TableStorageFormat configuration option to the Gen 2 MySQL Connector for controlling the destination table storage format. @@ -3257,5 +3310,5 @@ - Fixed an issue validating Oracle licenses that prevented the OracleCapture processor from starting.-- Improved change detection for large schemas+- Improved change detection for large schemas. ## December 17, 2025
--cloud により Snowflake 管理コンテナでツールを実行できる構文が追加され、--no-workspace、--github <secret>（--cloud を暗黙指定）も新設されました。さらに、cloud 環境でマウント済みワークスペースを参照・切り替える /workspace コマンドが追加され、詳細説明へのリンクも追記されています。
影響: --cloud 利用時はワークスペース名や GitHub シークレットを指定でき、cloud 環境の操作対象を /workspace で切り替えられるようになります。
変更内容: 本文を更新（23行追加・14行削除）
--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/cli-reference+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/cli-reference@@ -18,12 +18,13 @@ ## Starting CoCo -| Command | Description |-| ---------------------------------- | ------------------------------ |-| `cortex` | Start in current directory |-| `cortex -c production` | Start with specific connection |-| `cortex -w /path/to/project` | Start in specific directory |-| `cortex -w /new/project -c myconn` | Combine workdir and connection |-| `cortex --continue` | Continue last session |-| `cortex --resume <session_id>` | Resume specific session |+| Command | Description |+| ---------------------------------- | -------------------------------- |+| `cortex` | Start in current directory |+| `cortex -c production` | Start with specific connection |+| `cortex -w /path/to/project` | Start in specific directory |+| `cortex -w /new/project -c myconn` | Combine workdir and connection |+| `cortex --continue` | Continue last session |+| `cortex --resume <session_id>` | Resume specific session |+| `cortex --cloud` | Run tools in a managed container | ## CLI options@@ -41,4 +42,7 @@ | `-p, --print "<prompt>"` | Pass specified prompt, print response, and exit | | `--output-format stream-json` | JSON output (for scripting) |+| `--cloud [<workspace>]` | Run tools in a Snowflake-managed container |+| `--no-workspace` | With `--cloud`, use an ephemeral workspace |+| `--github <secret>` | With `--cloud`, allow authenticated GitHub access | | `-V, --version` | Show installed version | | `--help` | Show CLI help |@@ -50,4 +54,6 @@ Bypass mode approves every tool call without prompting you first. Use it only when you trust every action the agent might take.++See [](/user-guide/cortex-code/cloud-sandbox) for details on `--cloud`, `--no-workspace`, and `--github`. `--cloud` optionally takes a workspace name (`DATABASE.SCHEMA.NAME`) to mount; `--github` takes the name of a Snowflake secret (`DATABASE.SCHEMA.SECRET`) holding a GitHub personal access token, and implies `--cloud`. ### Examples@@ -223,10 +229,11 @@ #### Configuration -| Command | Description |-| ----------------- | ----------------------- |-| `/settings` | View/modify settings |-| `/theme` | Select color theme |-| `/sandbox` | Manage sandbox settings |-| `/add-dir <path>` | Add working directory |+| Command | Description |+| ----------------- | ---------------------------------------------------- |+| `/settings` | View/modify settings |+| `/theme` | Select color theme |+| `/sandbox` | Manage sandbox settings |+| `/workspace` | Browse and switch the mounted workspace (cloud only) |+| `/add-dir <path>` | Add working directory | #### Extensibility@@ -317,4 +324,6 @@ | `/sandbox mode auto` | Auto-allow sandboxed commands | | `/sandbox mode regular` | Prompt for all commands |++To run tools in a Snowflake-managed container instead of on your machine, start CoCo CLI with `--cloud`. See [](/user-guide/cortex-code/cloud-sandbox). #### `/mcp`: MCP servers
definition_version: 2でpackagesフィールドが追加され、型が単一文字列から文字列シーケンスに変更されました。packagesを使う場合はartifact_repositoryの設定が必須となり、AnacondaチャネルおよびPyPIパッケージはプロジェクトルートのrequirements.txtにも指定できるよう、依存関係の宣言方法が明確化されました。
影響: v1から移行する場合はpackagesを追加せず、既存どおりrequirements.txtを使用する必要があり、v2でpackagesを使う際はartifact_repositoryも設定する必要があります。
変更内容: 本文を更新（21行追加・7行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/snowpark/create+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/snowpark/create@@ -70,4 +70,13 @@ Files inside a project directory are processed by %sf-cli% and could be uploaded to Snowflake when executing other `snow snowpark` commands. You should use caution when putting any sensitive information inside files in a project directory. +**Specifying Python dependencies in `definition_version: 2`**++Python dependencies are declared in two places, depending on where the package comes from:++- **Anaconda-channel packages** (such as `snowflake-snowpark-python`, `pandas`, or `numpy`) must be listed in a `requirements.txt` file in the project root. This file is automatically picked up by `snow snowpark deploy`.+- **PyPI packages** can go in that same `requirements.txt` file (Snowflake CLI packages them into a zip) or under the entity `packages:` field, which **requires the `artifact_repository:` field to also be set** (typically to `snowflake.snowpark.pypi_shared_repository`). Specifying `packages:` without `artifact_repository:` returns the error: *"You specified packages / artifact_repository_packages without setting artifact_repository."*++The `packages:` field is new in `definition_version: 2` and is only for artifact-repository packages. v1 projects declare dependencies in `requirements.txt` only. If you are migrating an existing v1 project, see [](/developer-guide/snowflake-cli/command-reference/helpers-commands/v1-to-v2).+ <a id="label-snowcli-func-proc-properties"></a> @@ -221,15 +230,20 @@ **packages** -*optional*, *string*--</td>- <td>--List of packages to install from the artifact_repository. For example:+*optional*, *string sequence*++</td>+ <td>++List of PyPI packages to install from the artifact repository specified in `artifact_repository`. This field requires `artifact_repository` to be set; using `packages` alone returns an error.++You can also list PyPI packages in a project-root `requirements.txt` file. Snowflake CLI downloads packages that are not on the Anaconda channel and includes them in the application zip.++For Anaconda-channel packages (such as `snowflake-snowpark-python`, `pandas`, or `numpy`), declare them in `requirements.txt`. The `requirements.txt` file is automatically picked up by `snow snowpark deploy`.++For example: ```yaml artifact_repository: snowflake.snowpark.pypi_shared_repository packages:- - Faker - rich
変更内容は、前提条件や権限付与手順の英語表現を明確化する文言修正です。AWS 認証では use the EC2 instance role と明記され、HashiCorp の表記や、取り込み対象を指す「raw」の表現、Box への言及が整理されました。
影響: 機能・パラメータ・構文の変更はなく、設定手順の実務上の動作は変わりません。
変更内容: 本文を更新（12行追加・12行削除）
--- 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@@ -21,5 +21,5 @@ 1. Ensure that you have reviewed [](/user-guide/data-integration/openflow/connectors/box/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 have reviewed [configuring requireddomains](/user-guide/data-integration/openflow/setup-openflow-spcs-sf-allow-list)+3. If using %ofsfspcs-plural%, ensure that you have 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-box) connector. @@ -39,5 +39,5 @@ - **Read all files and folders stored in Box**. - **Write all files and folders stored in Box**: To download files and folders. Note that the connector can't upload any files.- Snowflake recommends granting the service account with only the Viewer role.+ Snowflake recommends granting the service account only the Viewer role. To grant the application access to files in Box, select a folder that you want to synchronize. Share it with the app service account using the email of the service account from step n. %box% is able to discover and download files from the specified folder and all its subfolders, but it cannot modify the files.@@ -63,5 +63,5 @@ 3. Grant the Snowflake service user the role you created in the previous steps. 4. Configure with [key-pair auth](/user-guide/key-pair-auth) for the Snowflake SERVICE user from step 2.-5. Snowflake strongly recommends this step. Configure a secrets manager supported by Openflow, for example, AWS, Azure, and Hashicorp, and store the public and private keys in the secret store.+5. Snowflake strongly recommends this step. Configure a secrets manager supported by Openflow, for example, AWS, Azure, and HashiCorp, and store the public and private keys in the secret store. @@ -70,11 +70,11 @@ - 1. Once the secrets manager is configured, determine how you will authenticate to it. On AWS, it's recommended that you the- EC2 instance role associated with Openflow as this way no other secrets have to be persisted.+ 1. Once the secrets manager is configured, determine how you will authenticate to it. On AWS, it's recommended that you use the+ EC2 instance role associated with Openflow, so no other secrets have to be persisted. 2. In Openflow, configure a Parameter Provider associated with this Secrets Manager, from the hamburger menu in the upper right. Navigate to **Controller Settings** %raa% **Parameter Provider** and then fetch your parameter values. 3. At this point all credentials can be referenced with the associated parameter paths and no sensitive values need to be persisted within Openflow. -6. If any other Snowflake users require access to the raw ingested documents and tables ingested by the connector (for example, for custom processing in Snowflake),+6. If any other Snowflake users require access to the raw documents and tables ingested by the connector (for example, for custom processing in Snowflake), then grant those users the role created in step 1. 7. Designate a warehouse for the connector to use. Start with the smallest warehouse size, then experiment with size depending on the number of tables being replicated,@@ -688,5 +688,5 @@ Run the following SQL code in a SQL worksheet to query-the Cortex Search service with files ingested from your Box site.+the Cortex Search service with files ingested from Box. Replace the following:@@ -731,5 +731,5 @@ <td>`full_name`</td> <td>String</td>- <td>A full path to the file from the Box site documents root. Example: `folder_1/folder_2/file_name.pdf`.</td>+ <td>A full path to the file from the Box folder root. Example: `folder_1/folder_2/file_name.pdf`.</td> </tr> <tr>@@ -756,5 +756,5 @@ <td>`user_emails`</td> <td>Array</td>- <td>An array of user email IDs that have access to the document. It also includes user email IDs from all the Microsoft 365 groups that are assigned to the document.</td>+ <td>An array of user email IDs that have access to the document.</td> </tr> </tbody>@@ -871,5 +871,5 @@ Use the connector definition to: -- Extract metadata about your Box files and ingest them to into a Snowflake table+- Extract metadata about your Box files and ingest it into a Snowflake table - Perform operations on the metadata of your files stored in Box @@ -885,5 +885,5 @@ The name of this column is required to be entered as the Box File Identifier Column parameter in later steps.- The list of supported columns types for the metadata table is VARCHAR, STRING, TEXT, FLOAT, DOUBLE, and DATE.+ The list of supported column types for the metadata table is VARCHAR, STRING, TEXT, FLOAT, DOUBLE, and DATE. Here is an example of the table that you can create for this connector:@@ -1176,5 +1176,5 @@ The name of this column is required to be entered as the Box File Identifier Column parameter in later steps.- The list of supported columns types for the metadata table is VARCHAR, STRING, TEXT, FLOAT, DOUBLE, and DATE.+ The list of supported column types for the metadata table is VARCHAR, STRING, TEXT, FLOAT, DOUBLE, and DATE. #### Set up the connector
Google Drive の共有情報について、user_ids と user_emails の説明を Microsoft 365／Microsoft 365 Groups から Google Drive／Google Groups 向けに修正しました。あわせて、Google Workspace のドメイン委任、HashiCorp の表記、AWS の認証手順、見出しや表現の誤記を修正していますが、機能・パラメータ・構文の追加や変更はありません。
影響: 設定手順と出力メタデータの説明が正確になり、Google Drive コネクタの構成や共有ユーザー情報を確認する際の混乱が減りますが、既存の動作変更は diff からは読み取れません。
変更内容: 本文を更新（11行追加・11行削除）
--- 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@@ -90,5 +90,5 @@ 3. In the left navigation, expand **Security** and then **Access** and select **Data control** then click on **API Controls**.-4. On the API **Controls** screen, select **Manage domain wild+4. On the API **Controls** screen, select **Manage domain-wide delegation**. 5. Click **Add new**.@@ -113,5 +113,5 @@ 3. Grant the Snowflake service user the role you created in the previous steps. 4. Configure with [key-pair auth](/user-guide/key-pair-auth) for the Snowflake SERVICE user from step 2.-5. Snowflake strongly recommends this step. Configure a secrets manager supported by Openflow, for example, AWS, Azure, and Hashicorp, and store the public and private keys in the secret store.+5. Snowflake strongly recommends this step. Configure a secrets manager supported by Openflow, for example, AWS, Azure, and HashiCorp, and store the public and private keys in the secret store. @@ -120,6 +120,6 @@ - 1. Once the secrets manager is configured, determine how you will authenticate to it. On AWS, it's recommended that you the- EC2 instance role associated with Openflow as this way no other secrets have to be persisted.+ 1. Once the secrets manager is configured, determine how you will authenticate to it. On AWS, it's recommended that you use the+ EC2 instance role associated with Openflow, so no other secrets have to be persisted. 2. In Openflow, configure a Parameter Provider associated with this Secrets Manager, from the hamburger menu in the upper right. Navigate to **Controller Settings** %raa% **Parameter Provider** and then fetch your parameter values.@@ -432,5 +432,5 @@ <tr> <td>Google Domain</td>- <td>The Google Workspace Domain that the Google Groups and Drive resides in.</td>+ <td>The Google Workspace Domain that the Google Groups and Drive reside in.</td> </tr> <tr>@@ -616,5 +616,5 @@ <tr> <td>Google Domain</td>- <td>The Google Workspace Domain that the Google Groups and Drive resides in.</td>+ <td>The Google Workspace Domain that the Google Groups and Drive reside in.</td> </tr> <tr>@@ -648,5 +648,5 @@ 3. [](#label-openflow-gdrive-cortex). -## Use case 3: Customise the connector definition+## Use case 3: Customize the connector definition Customize the connector definition to perform custom processing on ingested files.@@ -695,5 +695,5 @@ 1. Start the process group. The flow will create all required objects inside of Snowflake.- 2. Right click on the imported process group and select **Start**.+ 2. Right-click on the imported process group and select **Start**. 2. [](#label-openflow-gdrive-cortex).@@ -781,10 +781,10 @@ <td>`user_ids`</td> <td>Array</td>- <td>An array of Microsoft 365 user IDs that have access to the document. It also includes user IDs from all the Microsoft 365 groups that are assigned to the document. To find a specific user ID, see [Get a user](https://learn.microsoft.com/en-us/graph/api/user-get?view=graph-rest-1.0&tabs=http).</td>+ <td>An array of Google Drive user IDs that have access to the document. It also includes user IDs from all the Google Groups that are assigned to the document.</td> </tr> <tr> <td>`user_emails`</td> <td>Array</td>- <td>An array of Microsoft 365 user email IDs that have access to the document. It also includes user email IDs from all the Microsoft 365 groups that are assigned to the document.</td>+ <td>An array of Google Drive user email IDs that have access to the document. It also includes user email IDs from all the Google Groups that are assigned to the document.</td> </tr> </tbody>@@ -864,5 +864,5 @@ Execute the following code in a command-line interface to query the Cortex Search service with files ingested from your Google Drive.-You will need to authentication through key pair authentication and OAuth to access the+You'll need to authenticate through key pair authentication and OAuth to access the Snowflake REST APIs. For more information, see [](#label-cortex-search-query-syntax-rest)
runtime_environment_version が任意指定となり、省略時は既定の WH-RUNTIME-1.0（Python 3.9） を使用する仕様に更新されました。指定可能な値として WH-RUNTIME-1.0 と WH-RUNTIME-2.0（Python 3.10） が明記され、ノートブック識別子の例がハイフン形式からアンダースコア形式（my_notebook_id、my_schema、my_db）に変更されました。
影響: 実務では、必要に応じて WH-RUNTIME-2.0 を明示指定できる一方、既存設定で runtime_environment_version を省略すると既定の WH-RUNTIME-1.0 が適用されます。
変更内容: 本文を更新（11行追加・9行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/notebooks/use-notebooks+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/notebooks/use-notebooks@@ -47,9 +47,11 @@ query_warehouse: xsmall notebook_file: notebook.ipynb- runtime_environment_version: "2025.07"+ runtime_environment_version: "WH-RUNTIME-2.0" # optional; omit to use the default warehouse runtime artifacts: - notebook.ipynb - data.csv ```++Valid warehouse runtime values are `WH-RUNTIME-1.0` (Python 3.9, the default) and `WH-RUNTIME-2.0` (Python 3.10). For more information, see [](/user-guide/ui-snowsight/notebooks-create). The following table describes the properties of a notebook [project definition](/developer-guide/snowflake-cli/project-definitions/about):@@ -165,5 +167,5 @@ <td> -Runtime environment version for a notebook entity in your project definition file.+Runtime environment version for a notebook entity in your project definition file. This field is optional; if omitted, the notebook uses the default warehouse runtime (`WH-RUNTIME-1.0`, Python 3.9). Allowed values are `WH-RUNTIME-1.0` and `WH-RUNTIME-2.0` (Python 3.10). For more information, see [](/user-guide/ui-snowsight/notebooks-create). Notebook entity deployments will be rejected if both `compute_pool` and `runtime_environment_version` are specified in the configuration, leading to a validation failure.@@ -188,5 +190,5 @@ ```yaml-identifier: my-notebook-id+identifier: my_notebook_id ``` @@ -197,10 +199,10 @@ ```yaml identifier:- name: my-notebook-id- schema: my-schema # optional- database: my-db # optional-```--An error occurs if you specify a `schema` or `database` and use a fully qualified name in the `name` property (such as `mydb.schema1.my-notebook`).+ name: my_notebook_id+ schema: my_schema # optional+ database: my_db # optional+```++An error occurs if you specify a `schema` or `database` and use a fully qualified name in the `name` property (such as `mydb.schema1.my_notebook`). </td>
主に文法・表記を修正し、秘密鍵の参照元を手順4から手順5へ訂正しました。あわせて、AWSでの認証推奨文、単一テーブルの表現、SASL版の説明、Source Schema や Kafka キーストア関連の説明、実行手順の「plane」を「canvas」に修正しています。
影響: 機能・パラメータ・動作の変更はなく、手順番号と用語の明確化によって設定時の誤解を減らします。
変更内容: 本文を更新（9行追加・9行削除）
--- 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@@ -59,5 +59,5 @@ 5. Configure with [key-pair auth](/user-guide/key-pair-auth) for the Snowflake SERVICE user from step 3. 6. Snowflake strongly recommends this step. Configure a secrets manager supported by Openflow, for example, AWS, Azure, and Hashicorp,- and store the public and private keys in the secret store. However, note that the private key generated in step 4 can be used+ and store the public and private keys in the secret store. However, note that the private key generated in step 5 can be used directly as a configuration parameter for the connector configuration. In such a case, the private key is stored in Openflow runtime configuration. @@ -67,11 +67,11 @@ - 1. Once the secrets manager is configured, determine how you will authenticate to it. On AWS, it's recommended that you the- EC2 instance role associated with Openflow as this way no other secrets have to be persisted.+ 1. Once the secrets manager is configured, determine how you will authenticate to it. On AWS, it's recommended that you use the+ EC2 instance role associated with Openflow, so that no other secrets have to be persisted. 2. In Openflow, configure a Parameter Provider associated with this Secrets Manager, from the hamburger menu in the upper right. Navigate to **Controller Settings** %raa% **Parameter Provider** and then fetch your parameter values. 3. At this point all credentials can be referenced with the associated parameter paths and no sensitive values need to be persisted within Openflow. -7. Designate a warehouse for the connector to use. One connector can replicate single table to a single Kafka Topic.+7. Designate a warehouse for the connector to use. One connector can replicate a single table to a single Kafka Topic. For this kind of processing, you can select the smallest warehouse. @@ -84,5 +84,5 @@ - mTLS version: Choose this connector if you are using the SSL (mutual TLS) security protocol, or if you are using the SASL_SSL protocol and connecting to the broker that is using self-signed certificates.- - SASL version: Choose this connector if you are using any other security protocol+ - SASL version: Choose this connector if you are using any other security protocol. 3. Select **Install**.@@ -203,5 +203,5 @@ <tr> <td>Source Schema</td>- <td>The source schema. This schema should contain Snowflake Stream object that will be consumed.</td>+ <td>The source schema. This schema should contain the Snowflake Stream object that will be consumed.</td> <td>Yes</td> </tr>@@ -320,10 +320,10 @@ <tr> <td>Kafka Keystore Password</td>- <td>The password used to secure keystore file.</td>+ <td>The password used to secure the keystore file.</td> <td>No</td> </tr> <tr> <td>Kafka Key Password</td>- <td>A password for the private key stored in the keystore. Required for mTLS authentication.</td>+ <td>A password for the private key stored in the keystore. Required for mTLS authentication.</td> <td>No</td> </tr>@@ -389,4 +389,4 @@ ## Run the flow -1. Right-click on the plane and select **Enable all Controller Services**.+1. Right-click on the canvas and select **Enable all Controller Services**. 2. Right-click on the imported process group and select **Start**. The connector starts the data ingestion.
Git リポジトリ概要ページに、セットアップ手順と 制限事項 への案内が追加され、トラブルシューティングおよび制限事項ページへのリンクも追加されました。末尾に Next steps セクションが新設され、セットアップ、操作、例、トラブルシューティング、制限事項への導線が整理されています。 影響: 利用者は セットアップ手順 や制限事項を確認しやすくなり、Git 連携の導入・運用時の参照先を見つけやすくなります。
変更内容: 本文を更新（13行追加・0行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/git/git-overview+++ bhttps://docs.snowflake.com/en/developer-guide/git/git-overview@@ -7,4 +7,6 @@ - [](/developer-guide/git/git-operations) - [](/developer-guide/git/git-examples)+- [](/developer-guide/git/git-troubleshooting)+- [](/developer-guide/git/git-limitations) - [](/sql-reference/sql/create-git-repository) - [](/sql-reference/sql/alter-git-repository)@@ -17,4 +19,7 @@ You can integrate your remote Git repository with Snowflake so that files from the remote repository are synchronized to a Git repository clone in Snowflake. The clone includes all branches, tags, and commits from the remote repository.++To get started, see [](/developer-guide/git/git-setting-up).+For a complete list of limitations, see [](/developer-guide/git/git-limitations). ## Supported platforms@@ -54,2 +59,10 @@ [Snowflake notebooks](/user-guide/ui-snowsight/notebooks-snowgit). - Import files from the repository clone into code you run in Snowflake, such as procedures and UDFs.++## Next steps++- [](/developer-guide/git/git-setting-up)+- [](/developer-guide/git/git-operations)+- [](/developer-guide/git/git-examples)+- [](/developer-guide/git/git-troubleshooting)+- [](/developer-guide/git/git-limitations)
Organization Usage の権限一覧に、GRANTS_TO_SHARES view と LISTINGS view を追加し、いずれも必要な権限を ORGANIZATION_SECURITY_VIEWER と記載しました。また、SESSIONS view の権限も ORGANIZATION_SECURITY_VIEWER として明示され、同権限の対象ビューとして整理されています。
影響: 該当ビューを利用するには、ORGANIZATION_SECURITY_VIEWER 権限が必要であることが明確になりました。
変更内容: 本文を更新（12行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage@@ -868,4 +868,8 @@ </tr> <tr>+ <td>[GRANTS_TO_SHARES view](/sql-reference/organization-usage/grants_to_shares)</td>+ <td>ORGANIZATION_SECURITY_VIEWER</td>+ </tr>+ <tr> <td>[GRANTS_TO_USERS view](/sql-reference/organization-usage/grants_to_users)</td> <td>ORGANIZATION_SECURITY_VIEWER</td>@@ -876,4 +880,8 @@ </tr> <tr>+ <td>[LISTINGS view](/sql-reference/organization-usage/listings)</td>+ <td>ORGANIZATION_SECURITY_VIEWER</td>+ </tr>+ <tr> <td>[LOAD_HISTORY view](/sql-reference/organization-usage/load_history)</td> <td>ORGANIZATION_USAGE_VIEWER</td>@@ -1040,4 +1048,8 @@ <tr> <td>[SESSIONS view](/sql-reference/organization-usage/sessions)</td>+ <td>ORGANIZATION_SECURITY_VIEWER</td>+ </tr>+ <tr>+ <td>[SHARES view](/sql-reference/organization-usage/shares)</td> <td>ORGANIZATION_SECURITY_VIEWER</td> </tr>
vCPU の表記を統一し、「VCPU」を「vCPU」、「1vCPU」などを「1 vCPU」に修正しました。あわせて英文の文法・句読点を調整した体裁上の改訂であり、料金計算やスケーリング仕様の変更は diff からは確認できません。 影響: 実務上の動作や料金への影響はなく、ドキュメントの可読性と表記統一が改善されます。
変更内容: 本文を更新（4行追加・4行削除）
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/cost-byoc+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/cost-byoc@@ -43,5 +43,5 @@ Credits are billed per-second with a 60-second minimum. -For an example of using of VCPU and the impacts of scaling see [](#label-openflow-byoc-scaling-overview).+For an example of using vCPU and the impacts of scaling, see [](#label-openflow-byoc-scaling-overview). For information on the rate per vCPU per hour, refer to Table 1(g) in the [Snowflake Service Consumption Table](https://www.snowflake.com/legal-files/CreditConsumptionTable.pdf).@@ -115,8 +115,8 @@ | ---------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------- | | No runtimes | None | No cost | Compute and storage of Dataplane |-| 1 small runtime (1vCPU) <br /> (min 1 max 2) | Active for 1 hour <br /> Runtime does not scale to 2. | 1 runtime x 1 node x 1 vCPU x 1 hour = 1 <br /> Total = 1 vCPU-hour | Compute and storage of Dataplane |+| 1 small runtime (1 vCPU) <br /> (min 1 max 2) | Active for 1 hour <br /> Runtime does not scale to 2. | 1 runtime x 1 node x 1 vCPU x 1 hour = 1 <br /> Total = 1 vCPU-hour | Compute and storage of Dataplane | | 2 small runtimes (1 vCPU) (min/max=2) <br /> 1 large runtime (8 vCPU) (min/max=10) | Small: 2 nodes active for 1 hour <br /> Large: 10 nodes active for 1 hour | 2 runtimes x 2 nodes x 1 vCPU x 1 hour = 4 vCPU <br /> 1 runtime x 10 nodes x 8 vCPU x 1 hour = 80 vCPU <br /> Total = 84 vCPU-hours | Compute and storage of Dataplane |-| 1 medium (4vCPU) <br /> (min =1 max=2) | First 20 minutes, 1 node is running <br /> Scales to 2 nodes for the remaining 40 minutes of the hour <br /> Total 1 hour <br /> | 20 minutes = 1/3 hour <br /> 1 runtime x 1 node x 4 vCPU x 1/3 hour = 4/3 <br /> 1 runtime x 2 nodes x 4 vCPU x 2/3 hour = 16/3 <br /> Total = 6 2/3 vCPU-hours | Compute and storage of Dataplane |-| 1 medium (4vCPU) <br /> (min/max=2) | First 30 minutes 2 nodes running <br /> Suspends after first 30 minutes. | 30 minutes = 1/2 hour <br /> 1 runtime x 2 nodes x 4 vCPU x 1/2 hour = 4 <br /> Total = 4 vCPU-hours | Compute and storage of Dataplane |+| 1 medium (4 vCPU) <br /> (min =1 max=2) | First 20 minutes, 1 node is running <br /> Scales to 2 nodes for the remaining 40 minutes of the hour <br /> Total 1 hour <br /> | 20 minutes = 1/3 hour <br /> 1 runtime x 1 node x 4 vCPU x 1/3 hour = 4/3 <br /> 1 runtime x 2 nodes x 4 vCPU x 2/3 hour = 16/3 <br /> Total = 6 2/3 vCPU-hours | Compute and storage of Dataplane |+| 1 medium (4 vCPU) <br /> (min/max=2) | First 30 minutes 2 nodes running <br /> Suspends after first 30 minutes. | 30 minutes = 1/2 hour <br /> 1 runtime x 2 nodes x 4 vCPU x 1/2 hour = 4 <br /> Total = 4 vCPU-hours | Compute and storage of Dataplane | ### Mapping runtimes to EC2 instance types
UUID を Iceberg の VARIANT (v3) 列に保存できることに加え、Iceberg の構造化型（struct、list、map）の要素型または値型としても保存できることを明記しました。
影響: UUID を含む Iceberg structured types の利用可否が明確になり、該当するスキーマ設計に適用できます。
変更内容: 本文を更新（3行追加・3行削除）
--- ahttps://docs.snowflake.com/en/user-guide/tables-iceberg-data-types+++ bhttps://docs.snowflake.com/en/user-guide/tables-iceberg-data-types@@ -257,5 +257,5 @@ <td>`uuid`</td> <td>[UUID](/sql-reference/data-types-uuid)</td>- <td></td>+ <td>You can also store UUID values in Iceberg VARIANT (v3) columns and as the element or value type of Iceberg structured types (`struct`, `list`, and `map`).</td> </tr> <tr>@@ -438,6 +438,6 @@ be used to load data into OBJECT, ARRAY, or MAP columns that contain a nested VARIANT column. - Nested variants aren't supported.- - You can store [UUID](/sql-reference/data-types-uuid) values in a VARIANT column, and in structured type columns- (`struct`, `list`, and `map`).+ - You can store [UUID](/sql-reference/data-types-uuid) values in a VARIANT column. UUID is also supported as the+ element or value type of Iceberg structured types (`struct`, `list`, and `map`). - Also see [](/user-guide/semistructured-considerations).
Openflow for Oracle の表示場所の表現が、「Admin > Terms タブ」から「Admin > Terms ページ」内のタブへ変更されました。また、手順中のタブ名に定冠詞 the が追加されています。いずれも機能・設定内容ではなく、表現上の修正です。 影響: 操作内容に実質的な変更はなく、Openflow for Oracle タブを従来どおり選択します。
変更内容: 本文を更新（3行追加・3行削除）
--- 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@@ -48,5 +48,5 @@ - The %oracleofc% listing becomes visible in the list of available connectors.-- A new tab titled **Openflow for Oracle** appears in the **Admin** %raa% **Terms** tab.+- A new **Openflow for Oracle** tab appears in the **Admin** %raa% **Terms** page. <a id="label-oracle-license-setup"></a>@@ -74,5 +74,5 @@ 1. Sign in to %sf-web-interface-link%. 2. In the navigation menu, select **Admin** %raa% **Terms**.-3. Select **Openflow for Oracle** tab.+3. Select the **Openflow for Oracle** tab. 4. Locate the **Trial Status** card (status: "Ready to Activate"). 5. Select **Start Trial**.@@ -155,5 +155,5 @@ 1. Sign in to %sf-web-interface-link%. 2. In the navigation menu, select **Admin** %raa% **Terms**.-3. Select **Openflow for Oracle** tab.+3. Select the **Openflow for Oracle** tab. 4. Locate the **Trial Status** card (status: "Ready to Activate"). 5. Select **Start Trial**.
機能や SQL 構文の変更はなく、connector-specific resources の箇条書き末尾にピリオドを追加し、Control Pane UI を Control Plane UI に修正しました。また、利用規約の表現を Openflow terms of service に変更しました。 影響: 実務上の機能・設定への影響はなく、文法・用語の明確化のみです。
変更内容: 本文を更新（3行追加・3行削除）
--- 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@@ -93,5 +93,5 @@ - Grant access to Snowflake resources.-- Grant access to connector-specific resources+- Grant access to connector-specific resources. Snowflake roles are linked to Openflow Snowflake Managed Token, avoiding the need for customers to create separate service users and key pairs for authentication to Snowflake.@@ -168,5 +168,5 @@ grant create openflow data plane integration on account to role deployment_manager; - -- Assign create runtime privilege to roles. (This privilege cannot be granted in the Control Pane UI.)+ -- Assign create runtime privilege to roles. (This privilege cannot be granted in the Control Plane UI.) grant create openflow runtime integration on account to role deployment1_runtime_manager_1;@@ -249,5 +249,5 @@ 1. Sign in to Snowflake as a user with the ORGADMIN role. 2. In the navigation menu, select **Ingestion** %raa% **Openflow**.-3. Accept Openflow terms of services.+3. Accept the Openflow terms of service. <a id="label-setup-deployment"></a>
Git リポジトリの制約として、2 GB 超のリポジトリは非対応であることが追記されました。また、Git の概要および制限事項一覧へのリンクが追加されました。 影響: 2 GB を超えるリポジトリは Git-synced workspace で利用できないため、事前にサイズと制限事項を確認する必要があります。
変更内容: 本文を更新（5行追加・1行削除）
--- ahttps://docs.snowflake.com/en/user-guide/ui-snowsight/workspaces-git+++ bhttps://docs.snowflake.com/en/user-guide/ui-snowsight/workspaces-git@@ -2,4 +2,5 @@ - [](/user-guide/ui-snowsight/workspaces)+- [](/developer-guide/git/git-overview) Starting in September 2025, Snowflake is gradually upgrading accounts from Worksheets to Workspaces. Workspaces will become the default@@ -25,5 +26,8 @@ To develop and maintain files directly in %sf-web-interface%, you can create a workspace connected to a Git repository. -A Git repository must contain at least one branch; empty repositories aren't supported.+- A Git repository must contain at least one branch; empty repositories aren't supported.+- Git repositories larger than 2 GB aren't supported.++For a complete list of limitations, see [](/developer-guide/git/git-limitations). To create a new Git-synced workspace, follow these steps:
MFA が必要なアカウントでは、snow connection test 実行時にログイン承認を求め、以後の新規接続を開く snow コマンドでも同様に求める説明が追加されました。MFA caching によりトークンを再利用でき、Linux では安全な認証情報ストレージも必要です。また、プッシュ通知の代わりに --mfa-passcode でパスコードを直接指定できます。
影響: MFA 利用環境ではコマンド実行時の承認操作が発生するため、MFA caching または --mfa-passcode の利用を検討する必要があります。
変更内容: 本文を更新（6行追加・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@@ -291,4 +291,10 @@ For more information, see [](/developer-guide/snowflake-cli/connecting/connect). +If your account requires multi-factor authentication (MFA), this command prompts you to approve+the login, and so does every subsequent `snow` command that opens a new connection. To approve+once and reuse the cached token, enable [MFA caching](#label-snowcli-mfa-caching). On Linux,+caching also requires secure credential storage.+To supply a passcode directly instead of using the push mechanism, use the `--mfa-passcode` option.+ ## Examples
実行時に Application Service を識別する Snowflake の組み込み環境変数として、SNOWFLAKE_DATABASE、SNOWFLAKE_SCHEMA、SNOWFLAKE_SERVICE_NAME などが追加で説明された。これらはアプリ側で未定義の場合のみ Snowflake が設定し、アプリ側で設定した値が常に優先される。 影響: Application Service の識別情報を独自の環境変数名で設定している場合でも、その値が Snowflake の組み込み値で上書きされないことが明確になった。
変更内容: 本文を更新（6行追加・0行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/app-yml+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/app-yml@@ -194,4 +194,10 @@ log_level = os.getenv("LOG_LEVEL", "INFO") ```++Beyond the names you set here, Snowflake provides built-in environment variables+(such as `SNOWFLAKE_DATABASE`, `SNOWFLAKE_SCHEMA`, and `SNOWFLAKE_SERVICE_NAME`)+that identify the Application Service at runtime. Snowflake sets those only when+you don't define them yourself, so a name you set here always wins. See+[Built-in environment variables](/developer-guide/snowflake-app-runtime/getting-started#label-getting-started-builtin-env-vars). <a id="label-snowflake-apps-manifest-secrets"></a>
ページ末尾に Next steps セクションが追加され、インストールと 接続に関するドキュメントへのリンクが新設された。 影響: 利用者が Snowflake CLI の導入および接続手順へ進みやすくなる。
変更内容: 本文を更新（5行追加・0行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/introduction/introduction+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/introduction/introduction@@ -66,2 +66,7 @@ Some %sf-cli% commands execute code from your project directory, including subdirectories, or fetch and execute content from remote URLs. Only run %sf-cli% commands on projects, packages, and SQL sources you trust.++## Next steps++- [](/developer-guide/snowflake-cli/installation/installation)+- [](/developer-guide/snowflake-cli/connecting/connect)
CoCo CLI cloud sandboxへのナビゲーションリンクが追加されました。また、このページが対象とするのは、コマンドを分離しつつユーザーのマシン上で実行するローカル sandboxであり、Snowflake 管理コンテナでエージェントのツールを実行する場合は別ページを参照する旨が追記されました。 影響: ローカル実行と Snowflake 管理コンテナ実行の使い分けが明確になり、後者を利用する場合の参照先が分かりやすくなりました。
変更内容: 本文を更新（5行追加・0行削除）
--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/sandbox+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/sandbox@@ -5,4 +5,5 @@ - [CoCo](/user-guide/cortex-code/cortex-code) - [CoCo CLI](/user-guide/cortex-code/cortex-code-cli)+- [CoCo CLI cloud sandbox](/user-guide/cortex-code/cloud-sandbox) - [Security](/user-guide/cortex-code/security) - [Settings](/user-guide/cortex-code/settings)@@ -13,4 +14,8 @@ Support for this feature is experimental and may be subject to change.++This page covers the local sandbox, which isolates commands but still runs them on your+machine. To run the agent's tools in a Snowflake-managed container instead, see+[](/user-guide/cortex-code/cloud-sandbox). <a id="label-cortex-code-sandbox-platforms"></a>
SQL コマンドの説明が更新され、%sf-cli% で利用できる SQL コマンドは snow sql のみであることが明記されました。クエリは -q、ファイルは -f、または標準入力から渡せることが示され、詳細説明およびコマンドリファレンスへのリンクが追加されています。
影響: snow sql の入力方法と詳細ドキュメントへの導線が明確になり、利用者は実行方法を確認しやすくなります。
変更内容: 本文を更新（3行追加・2行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/sql-commands/overview+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/sql-commands/overview@@ -2,7 +2,8 @@ - [](/developer-guide/snowflake-cli/index)+- [](/developer-guide/snowflake-cli/sql/execute-sql) - [Snowflake CLI command reference](/developer-guide/snowflake-cli/command-reference/overview) -SQL commands provide developers the ability to execute SQL queries with %sf-cli%.+`snow sql` is the only SQL command in %sf-cli%. Pass a query with `-q`, a file with `-f`, or pipe SQL on stdin. -- [](/developer-guide/snowflake-cli/command-reference/sql-commands/sql)+See [](/developer-guide/snowflake-cli/sql/execute-sql) and the [](/developer-guide/snowflake-cli/command-reference/sql-commands/sql) command reference.
本文中の表記を flow files から FlowFiles に統一し、Snowflake Support へのリンクを絶対 URL から相対パス（/user-guide/contacting-support）に変更しました。機能や処理内容の変更はありません。
影響: 実務上の動作変更はなく、用語表記とリンク指定方法のみの更新です。
変更内容: 本文を更新（2行追加・2行削除）
--- 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@@ -77,5 +77,5 @@ If the status is `IN_PROGRESS`, a FlowFile is still being processed for that object type. -Do not delete flow files manually. This can cause a job to remain in the `IN_PROGRESS` status indefinitely because the state cannot be manually updated.+Do not delete FlowFiles manually. This can cause a job to remain in the `IN_PROGRESS` status indefinitely because the state cannot be manually updated. If this occurs, you must perform a full reload for that object type.@@ -107,3 +107,3 @@ If the state is stuck in `IN_PROGRESS` but no FlowFiles were manually deleted, contact-[Snowflake Support](https://docs.snowflake.com/user-guide/contacting-support).+[Snowflake Support](/user-guide/contacting-support).
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-git-repository+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-git-repository@@ -4,4 +4,5 @@ - [](/developer-guide/git/git-setting-up) - [](/developer-guide/git/git-operations)+- [](/developer-guide/git/git-limitations) - [](/sql-reference/sql/create-api-integration) @@ -153,4 +154,7 @@ CREATE OR REPLACE *<object>* statements are atomic. That is, when an object is replaced, the old object is deleted and the new object is created in a single transaction. +- Git repositories larger than 2 GB aren't supported. For a complete list of limitations, see+ [](/developer-guide/git/git-limitations).+ ## Examples
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（2行追加・2行削除）
--- 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@@ -241,5 +241,5 @@ 3. Configure the destination table - We highly recommend using server-side schema evolution for schema changes and+ Snowflake recommends using server-side schema evolution for schema changes and [an error table for DML error logging](#label-kinesis-dml-error-logging). @@ -685,5 +685,5 @@ ## Using the connector with a customer-defined schema for the destination table -The connector treats each Kinesis record as a row to be inserted into a Snowflake table. For example, if you have a Kinesis topic with the content of the message structured like the following JSON:+The connector treats each Kinesis record as a row to be inserted into a Snowflake table. For example, if you have a Kinesis stream with the content of the message structured like the following JSON: ```json
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/zero-copy/workday/cortex-code+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/zero-copy/workday/cortex-code@@ -8,5 +8,5 @@ Workday Live Data Query for Snowflake is in Early Adopter (EA) for Workday and in Preview for Snowflake. To request access, contact your Workday account representative. -Cortex Code is an AI coding assistant built into Snowflake Workspaces. Because your Workday LDQ notebook runs inside a Workspace, you can use Cortex Code to accelerate your work with Workday data — from writing queries to analyzing results and building visualizations.+Cortex Code is an AI coding assistant built into Snowflake Workspaces. Because your Workday LDQ notebook runs inside a Workspace, you can use Cortex Code to accelerate your work with Workday data: from writing queries to analyzing results and building visualizations. ## Prerequisites@@ -35,5 +35,5 @@ > "Using `workers_df`, create a bar chart showing headcount by management level, sorted descending." -> "Summarize the `workers_df` DataFrame — show column types, null counts, and basic statistics."+> "Summarize the `workers_df` DataFrame: show column types, null counts, and basic statistics." ### Transform and join with Snowflake data@@ -65,5 +65,5 @@ > "Show me the distribution of workers hired in the last 12 months, broken down by quarter." -> "Compare headcount across management levels — are we top-heavy?"+> "Compare headcount across management levels. Are we top-heavy?" ### Data quality@@ -79,4 +79,4 @@ - Cortex Code is aware of your notebook's context and can see your existing cells and variables. - It works best after data is loaded into a DataFrame. It can't call the Workday LDQ connector directly, but it can generate the Python code for you to run.-- Use the **Fix** button in the results panel if a cell fails — Cortex Code will suggest corrections.+- Use the **Fix** button in the results panel if a cell fails. Cortex Code will suggest corrections. - Type `@` in the chat to reference Snowflake tables or views as additional context for your prompts.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/migrations/aim-for-datawarehouses/data-migration-validation/data-validation+++ bhttps://docs.snowflake.com/en/migrations/aim-for-datawarehouses/data-migration-validation/data-validation@@ -3,5 +3,5 @@ The Data Validation feature provides a fault-tolerant, scalable way to verify that data migrated into Snowflake matches the data in the original source system. It runs on the same infrastructure used by Data Migration, so you can migrate and validate with the same Orchestrator and Workers. -AIM DMV data validation is designed for migration scenarios where you need confidence that migrated data is correct before cutting over. Supported source platforms are **SQL Server**, **Amazon Redshift**, **Teradata**, **Oracle**, and **PostgreSQL**.+AIM DMV data validation is designed for migration scenarios where you need confidence that migrated data is correct before cutting over. Supported source platforms are **SQL Server**, **Azure Synapse Analytics**, **Amazon Redshift**, **Teradata**, **Oracle**, and **PostgreSQL**. For shared architecture, deployment options, prerequisites, and Worker tuning, see [Data Migration & Validation overview](./overview).@@ -40,4 +40,5 @@ - [Validating Data from Amazon Redshift](./validate-redshift) - [Validating Data from SQL Server](./validate-sql-server)+- [Validating Data from Azure Synapse Analytics](./validate-synapse) - [Validating Data from Teradata](./validate-teradata) - [Validating Data from Oracle](./validate-oracle)
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/data-types-uuid+++ bhttps://docs.snowflake.com/en/sql-reference/data-types-uuid@@ -24,4 +24,7 @@ - You can store UUID values in [semi-structured data types](/sql-reference/data-types-semistructured) (such as VARIANT) and [structured data types](/sql-reference/data-types-structured) (such as ARRAY, OBJECT, and MAP).+- Apache Iceberg™ tables support UUID as a column type. You can also store UUID values in Iceberg VARIANT (v3) columns+ and as the element or value type of Iceberg structured types (ARRAY, OBJECT, and MAP). For more information, see+ [](/user-guide/tables-iceberg-data-types). <a id="label-uuid-type-specifying"></a>
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/migrations/aim-for-datawarehouses/data-migration-validation/data-migration+++ bhttps://docs.snowflake.com/en/migrations/aim-for-datawarehouses/data-migration-validation/data-migration@@ -7,8 +7,9 @@ ## Supported source platforms -AIM DMV cloud data migration supports **SQL Server**, **Amazon Redshift**, **Teradata**, **Oracle**, and **PostgreSQL**. Each platform page covers prerequisites, auth methods, extraction strategies, data type mappings, and platform-specific suggestions:+AIM DMV cloud data migration supports **SQL Server**, **Azure Synapse Analytics**, **Amazon Redshift**, **Teradata**, **Oracle**, and **PostgreSQL**. Each platform page covers prerequisites, auth methods, extraction strategies, data type mappings, and platform-specific suggestions: - [Migrating Data from Amazon Redshift](./migrate-redshift) - [Migrating Data from SQL Server](./migrate-sql-server)+- [Migrating Data from Azure Synapse Analytics](./migrate-synapse) - [Migrating Data from Teradata](./migrate-teradata) - [Migrating Data from Oracle](./migrate-oracle)
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- 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@@ -1128,4 +1128,4 @@ ## Run the flow -1. Right-click on the plane and select **Enable all Controller Services**.+1. Right-click on the canvas and select **Enable all Controller Services**. 2. Right-click on the imported process group and select **Start**. The connector starts the data ingestion.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- 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@@ -98,5 +98,5 @@ <tbody> <tr>- <td>On premise</td>+ <td>On-premises</td> <td>
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- 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@@ -207,5 +207,5 @@ ``` - Use the SQL Server authentication login that administers the logical server (for example the login you specified when you created the server), not the connector login.+ Use the SQL Server authentication login that administers the logical server (for example, the login you specified when you created the server), not the connector login.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- 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@@ -342,5 +342,5 @@ This allows the new instance to catch up and continue replicating existing tables without having to snapshot each again. -Switching a running connector from latest to earliest position causes the entire available redo logs+Switching a running connector from latest to earliest position causes all available redo logs to be re-read, re-processed, and re-applied to the destination table.
（この変更は要約対象外です。diff を参照してください）
判定根拠: 書式・空白のみの変更
--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/byoc-validate-vpc-config+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/byoc-validate-vpc-config@@ -49,5 +49,5 @@ - Required resource tags -- Network Connectivity+- Network connectivity - Access to Openflow services and endpoints - Image registry access for required containers
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/grants_to_shares+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/grants_to_shares@@ -24,5 +24,5 @@ Each row in this view corresponds to a privilege granted on an object to a share. -This view is available only in the [organization account](/user-guide/organization-accounts). Users with the GLOBALORGADMIN role, or users granted the SNOWFLAKE.ORGANIZATION_USAGE_VIEWER application role, can access it. For details, see [Accessing the ORGANIZATION_USAGE schema](/sql-reference/organization-usage#label-org-usage-access-org-account).+This view is available only in the [organization account](/user-guide/organization-accounts). Users with the GLOBALORGADMIN role, or users granted the SNOWFLAKE.ORGANIZATION_SECURITY_VIEWER application role, can access it. For details, see [Accessing the ORGANIZATION_USAGE schema](/sql-reference/organization-usage#label-org-usage-access-org-account). ## Columns
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/developer-guide/git/git-limitations+++ bhttps://docs.snowflake.com/en/developer-guide/git/git-limitations@@ -24,3 +24,3 @@ - Snowflake doesn't currently support submodules, so you won't be able to see submodule files. Snowflake won't download those files from the remote repository nor upload them to the remote repository.-- Git repositories larger than 2GB aren't supported.+- Git repositories larger than 2 GB aren't supported.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/listings+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/listings@@ -24,5 +24,5 @@ Each row in this view corresponds to a different listing. -This view is available only in the [organization account](/user-guide/organization-accounts). Users with the GLOBALORGADMIN role, or users granted the SNOWFLAKE.ORGANIZATION_USAGE_VIEWER application role, can access it. For details, see [Accessing the ORGANIZATION_USAGE schema](/sql-reference/organization-usage#label-org-usage-access-org-account).+This view is available only in the [organization account](/user-guide/organization-accounts). Users with the GLOBALORGADMIN role, or users granted the SNOWFLAKE.ORGANIZATION_SECURITY_VIEWER application role, can access it. For details, see [Accessing the ORGANIZATION_USAGE schema](/sql-reference/organization-usage#label-org-usage-access-org-account). ## Columns
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/shares+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/shares@@ -24,5 +24,5 @@ Each row in this view corresponds to a different share. -This view is available only in the [organization account](/user-guide/organization-accounts). Users with the GLOBALORGADMIN role, or users granted the SNOWFLAKE.ORGANIZATION_USAGE_VIEWER application role, can access it. For details, see [Accessing the ORGANIZATION_USAGE schema](/sql-reference/organization-usage#label-org-usage-access-org-account).+This view is available only in the [organization account](/user-guide/organization-accounts). Users with the GLOBALORGADMIN role, or users granted the SNOWFLAKE.ORGANIZATION_SECURITY_VIEWER application role, can access it. For details, see [Accessing the ORGANIZATION_USAGE schema](/sql-reference/organization-usage#label-org-usage-access-org-account). ## Columns
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/parameters+++ bhttps://docs.snowflake.com/en/sql-reference/parameters@@ -71,5 +71,5 @@ <tr> <td>[ALLOW_CLIENT_MFA_CACHING](#allow-client-mfa-caching)</td>- <td></td>+ <td>Used to enable Multi-Factor Authentication (MFA) token caching for Snowflake-provided clients.</td> </tr> <tr>
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- 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@@ -313,5 +313,5 @@ it already sent. For example, records sent before a new column was detected don't include a value for that column, so the connector replays the affected rows to populate the new column. Because the-connector applies changes idempotently by primary key, replaying these records doesn't create+connector applies changes idempotently by replication key, replaying these records doesn't create duplicate rows in the destination table.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/migrations/aim-for-datawarehouses/data-migration-validation/required-privileges+++ bhttps://docs.snowflake.com/en/migrations/aim-for-datawarehouses/data-migration-validation/required-privileges@@ -419,5 +419,5 @@ ### Azure Synapse -Azure Synapse (Dedicated SQL Pool and Serverless SQL Pool) uses the same T-SQL system views as SQL Server and connects through the same `connections.source.sqlserver` configuration. Apply the SQL Server grants above, with these differences:+Azure Synapse (Dedicated SQL Pool and Serverless SQL Pool) uses the same T-SQL system views as SQL Server, but connects through its own `connections.source.azure_synapse` configuration. Apply the SQL Server grants above, with these differences: - Dedicated Pool: same as SQL Server, using `sys.indexes`, `sys.index_columns`, and `INFORMATION_SCHEMA.COLUMNS`.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- 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@@ -328,5 +328,5 @@ This section describes how to reinstall the connector.-It covers situations where the new connector is installed in the same runtime, or when it is moved to a new runtime.+It covers situations where the new connector is installed in the same runtime, or where it is moved to a new runtime. Reinstall is often used in conjunction with [Incremental replication without snapshots](/user-guide/data-integration/openflow/connectors/postgres/incremental-replication).
（この変更は要約対象外です。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@@ -256,5 +256,5 @@ 2. Open the **Incremental Load** process group. 3. Right-click the **MultiDatabaseCaptureChangeCdcSqlServer** processor, then select **View state**.-4. Check the state entries for every table with keys starting with `position.`. If a value is `0/0/0` then the connector has not yet finished re-reading the changes for this table.+4. Check the state entries for every table with keys starting with `position.`. If a value is `0/0/0`, then the connector has not yet finished re-reading the changes for this table. ### Usage notes
| セクション | S | A | B | C | 計 |
|---|---|---|---|---|---|
| Loading & Unloading Data | 0 | 0 | 9 | 9 | 18 |
| Snowflake CLI | 0 | 2 | 5 | 0 | 7 |
| Developer Guide | 0 | 1 | 2 | 1 | 4 |
| Organization Usage | 0 | 0 | 1 | 3 | 4 |
| User Guide | 0 | 2 | 1 | 0 | 3 |
| Migrations | 0 | 0 | 0 | 3 | 3 |
| Cortex Code | 0 | 0 | 2 | 0 | 2 |
| SQL General Reference | 0 | 0 | 0 | 2 | 2 |
| Snowsight UI | 0 | 0 | 1 | 0 | 1 |
| SQL Commands | 0 | 0 | 1 | 0 | 1 |