SNOWFLAKE DOCS DIFF
総括は生成されていません（claude CLI が利用できなかった可能性があります）。
Per-user quotas が Preview から General Availability（GA） に昇格した。GA に伴い、ブロック時のメール通知制御（SET_BLOCK_ENFORCEMENT_ENABLED の第2引数）、通知閾値の月次/日次スコープ指定（ADD_NOTIFICATION_THRESHOLD の第4引数）、新ビュー ACCOUNT_USAGE.QUOTA_ACCESS_BLOCK_HISTORY、伝播時間の短縮（約5〜10分）が追加された。Preview 時の GET_ACTIVE_BLOCKS() は GET_ACTIVE_BLOCKS_V2() に置換、GET_PER_USER_USAGE_PREVIEW() と SET_REFRESH_TIER() は廃止された。
影響: Preview 版の Per-user quotas を利用中の場合、廃止されたメソッド（GET_ACTIVE_BLOCKS / GET_PER_USER_USAGE_PREVIEW / SET_REFRESH_TIER）の呼び出しを修正する必要がある。
判定根拠: Preview → GA 昇格
--- ahttps://docs.snowflake.com/en/release-notes/2026/10_29+++ bhttps://docs.snowflake.com/en/release-notes/2026/10_29@@ -21,5 +21,34 @@ For updates to these release notes, see [](#label-rel-notes-change-log-10-29). -## New features+## Cost management updates++### Per-user quotas (*General availability*)++Per-user quotas are now generally available. Per-user quotas let quota admins set monthly and+daily credit limits for individual users, and notify users at various configurable thresholds. Quotas can target all users in an account or a tag-filtered subset, and cover both warehouse compute and AI feature domains including AI Functions, Snowflake CoCo, Cortex Agents, and Snowflake CoWork.+For AI features, admins can configure quotas to automatically block AI access for users who reach their AI quota limit and release the block when the cycle resets.++With general availability, the following updates are included:++- **Configurable end-user block notifications**: When block enforcement is enabled, admins can+ now control whether blocked users receive an email notification. Pass a second boolean argument+ to `SET_BLOCK_ENFORCEMENT_ENABLED` — for example, `SET_BLOCK_ENFORCEMENT_ENABLED(TRUE, TRUE)`+ enables enforcement and sends email notifications to blocked users. Going forward, end user notification will be disabled by default and admins will have to explicitly enable end user notifications.+- **Monthly or daily notification threshold targeting**: Notification thresholds can now be+ scoped to either the monthly or daily credit limit. Pass `'MONTHLY'` or `'DAILY'` as the+ fourth argument to `ADD_NOTIFICATION_THRESHOLD`.+- **`ACCOUNT_USAGE.QUOTA_ACCESS_BLOCK_HISTORY` view**: New account-level view that shows all+ users blocked across all quotas in the account.+- **Faster enforcement propagation**: Configuration changes now propagate in approximately 5–10+ minutes (previously up to 15 minutes).++The following Public Preview methods have been replaced or removed at general availability:++- `GET_ACTIVE_BLOCKS()` is replaced by `GET_ACTIVE_BLOCKS_V2()`.+- `GET_PER_USER_USAGE_PREVIEW()` and `SET_REFRESH_TIER()` are no longer available. Quota+ evaluation now occurs within minutes for all accounts; a separate refresh tier setting is not+ required.++For more information, see [Per-user quotas](/user-guide/budgets/per-user-quotas). ### Anomaly monitors for cost anomalies (*Preview*)@@ -48,5 +77,10 @@ ## Release notes change log -| Announcement | Update | Date |-| ------------- | ----------------------------- | ------------ |-| Release notes | Initial publication (preview) | Aug 13, 2026 |+<div className="colwidths-auto">++| Announcement | Update | Date |+| ---------------------------------------- | -------------------------------------- | ------------ |+| Release notes | Initial publication (preview) | Aug 13, 2026 |+| *Per-user quotas (General availability)* | **Added** to *Cost management updates* | Aug 14, 2026 |++</div>
Open Data Sharing が Private Preview から Public Preview に昇格し、選択されたアカウント限定から全アカウント利用可能に変更された。ロール要件が拡充され、ACCOUNTADMIN 以外にも CREATE EXTERNAL CONSUMER 権限を持つカスタムロールで操作可能になった。YAML マニフェストに open_sharing.catalog_identifier フィールドが追加され、Iceberg REST Catalog API 経由で外部コンシューマーが接続する際のカタログ識別子を指定できるようになった。また、ネットワークポリシー使用時は外部コンシューマーごとにエントリ追加が必要である旨の注意書きが追加された。 影響: Public Preview への移行により全アカウントで Open Data Sharing が利用可能となり、CREATE EXTERNAL CONSUMER 権限の委譲やネットワークポリシー設定の確認など、運用手順の見直しが必要になる。
判定根拠: SQL 構文/コードブロックの増減 (+3/-0)
--- ahttps://docs.snowflake.com/en/user-guide/open-data-sharing+++ bhttps://docs.snowflake.com/en/user-guide/open-data-sharing@@ -11,7 +11,7 @@ <a id="about-listing-consumers"></a> -# Open Data Sharing (*Preview*)--Support for this feature is currently not in production and is available only to selected accounts.+# Open Data Sharing++Available to all accounts. - [](/guides-overview-sharing)@@ -22,5 +22,5 @@ need for complex ETL pipelines, data duplication, or manual file exports. -During Private Preview, the only supported target region for shared data is the region where your provider account is located.+During Public Preview, the only supported target region for shared data is the region where your provider account is located. <a id="label-why-use-open-data-sharing"></a>@@ -50,6 +50,4 @@ ## Determine your account region--During Private Preview, shared data is available only in the region where your provider account is located. Run the following command to return your account region:@@ -69,6 +67,16 @@ ## Step 1: Use a role with the required privileges -Use a role that can create external consumers, shares, listings, and the database objects you plan to share. The following example uses-`ACCOUNTADMIN`:+To complete this workflow, use a role that has one of the following:++- The `ACCOUNTADMIN` role, or+- The `CREATE EXTERNAL CONSUMER` privilege granted at the account level, along with the privileges required to create shares, listings, and the database objects you plan to share.++To grant `CREATE EXTERNAL CONSUMER` to a custom role:++```sql+GRANT CREATE EXTERNAL CONSUMER ON ACCOUNT TO ROLE my_role;+```++The following example uses `ACCOUNTADMIN`: ```sql@@ -103,6 +111,9 @@ You must save the PAT secret when Snowflake returns it. You cannot retrieve the secret later. -During Private Preview, only Programmatic Access Tokens (PATs) are supported for external consumer authentication. Other authentication+During Public Preview, only Programmatic Access Tokens (PATs) are supported for external consumer authentication. Other authentication methods will be available in later release phases.++If your account uses a network policy, you must add an entry for each external consumer you want to grant access to. If your account+does not use a network policy, external consumers can connect without any additional configuration. <a id="label-open-data-sharing-step-4"></a>@@ -180,4 +191,6 @@ title: "test open sharing" description: "test open sharing"+open_sharing:+ catalog_identifier: "test-open-sharing" listing_terms: type: "OFFLINE"@@ -231,2 +244,6 @@ Lists the external consumer identities that can access the listing.++**open_sharing.catalog_identifier**++A unique identifier for the catalog exposed to external consumers via the Iceberg REST Catalog API. This value is used by the consumer when configuring their Iceberg REST Catalog client to connect to the shared data.
Native Application Framework の Declarative Sharing において、ノートブックの直接共有が deprecated（非推奨） となり、代わりに workspace 経由での共有が必要となった。ドキュメント全体で「notebooks」への言及が「workspaces」に置き換えられ、共有可能なコードオブジェクトの説明に workspace の概念が導入された。 影響: Declarative Sharing でノートブックを共有しているプロバイダーは、workspace 経由の共有方式へ移行する必要がある。
判定根拠: 追加行に「deprecated」
--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/about+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/about@@ -25,5 +25,6 @@ Declarative Sharing in the %naf% enables providers to share not just data,-but code objects – [notebooks](/user-guide/ui-snowsight/notebooks),+but code objects – [workspaces](/developer-guide/declarative-sharing/workspaces) containing+[notebooks](/user-guide/ui-snowsight/notebooks-in-workspaces/notebooks-in-workspaces-overview), [stored procedures](/developer-guide/stored-procedure/stored-procedures-overview), and [user-defined functions](/developer-guide/udf/udf-overview) – alongside@@ -89,5 +90,6 @@ <dd> -Code objects that help consumers visualize and explore the data.+Code objects that help consumers visualize and explore the data. Sharing notebooks directly is+deprecated. Share notebooks in a workspace instead. </dd>@@ -125,9 +127,9 @@ **Data product best uses** -| Data product | Description | Best for |-| ------------------------------ | ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |-| Secure Data Sharing | Traditional read-only sharing of tables and views. | Organizations beginning data monetization or with simple sharing needs. |-| %declarative-app-short-plural% | Enhanced sharing with notebooks and other logic, role-based access control (RBAC), and declarative configuration. | Data providers ready to add value through guided experiences and documentation |-| %full-native-apps% | Apps running fully inside of a consumer account with complex business logic and interfaces. | Organizations building complex data products with advanced capabilities. |+| Data product | Description | Best for |+| ------------------------------ | ------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------ |+| Secure Data Sharing | Traditional read-only sharing of tables and views. | Organizations beginning data monetization or with simple sharing needs. |+| %declarative-app-short-plural% | Enhanced sharing with workspaces and other logic, role-based access control (RBAC), and declarative configuration. | Data providers ready to add value through guided experiences and documentation |+| %full-native-apps% | Apps running fully inside of a consumer account with complex business logic and interfaces. | Organizations building complex data products with advanced capabilities. | ## Choosing a data product@@ -175,5 +177,5 @@ - **Technical Expertise**: Intermediate Snowflake - **Development Skills**: SQL, YAML, notebooks-- **Maintenance Effort**: Low - declarative updates, notebook/ SQL changes+- **Maintenance Effort**: Low - declarative updates, workspace/ SQL changes </td>@@ -182,5 +184,5 @@ - Data stays within Snowflake-- Limited functionality–that is, notebooks, Streamlit, stored procedures, and user-defined functions+- Limited functionality–that is, workspaces, notebooks, Streamlit, stored procedures, and user-defined functions </td>
Legacy Notebooks を application_content.notebooks で共有する方法が非推奨（deprecated）となった旨の警告が追加された。2026年8月18日以降はこの方法で新規アプリケーションパッケージを作成できなくなり、2026年11月以降は Legacy Notebooks の実行・編集自体が不可となる。移行先として Snowflake Notebooks in Workspaces でのワークスペース共有が案内されており、ワークスペース内のノートブックは !pip install で Python パッケージをインストールするため environment.yml やAnacondaパッケージリストは不要と説明されている。
影響: Legacy Notebooks を Native App で共有しているユーザーは、2026年8月18日までに Workspaces ベースの共有方式へ移行する必要がある。
判定根拠: 追加行に「deprecated」
--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/add-packages+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/add-packages@@ -1,3 +1,19 @@ # Add Anaconda packages to a notebook++Sharing individual notebooks with `application_content.notebooks` shares+[Legacy Notebooks](/user-guide/ui-snowsight/notebooks), and is deprecated. Starting+August 18, 2026, you can't create new application packages that share notebooks this way. Starting+November 2026, Legacy Notebooks can no longer be run or edited. For the full timeline, see+[](/release-notes/bcr-bundles/un-bundled/bcr-disable-legacy-notebooks).++Share [Snowflake Notebooks in Workspaces](/user-guide/ui-snowsight/notebooks-in-workspaces/notebooks-in-workspaces-overview)+in a workspace instead. Consumers can run and interact with those notebooks the same way, and a+workspace can also share documentation, images, and sample data files. For more information, see+[](/developer-guide/declarative-sharing/workspaces).++This topic applies only to Legacy Notebooks shared with `application_content.notebooks`. Notebooks+shared in a workspace install their Python packages at run time with `!pip install`, so they don't+need an `environment.yml` file or an Anaconda package list. For more information, see+[](/developer-guide/declarative-sharing/workspaces#label-dsna-workspace-notebook-packages). Support for %declarative-app-plural% is available to all accounts.
application_content.notebooks フィールドが非推奨（deprecated）となった。個別ノートブックの共有は Legacy Notebooks 向けであり、2026年8月18日以降はこの方法で新規アプリケーションパッケージを作成できなくなる。2026年11月以降は Legacy Notebooks の実行・編集も不可。代替として application_content.workspaces 経由で Snowflake Notebooks in Workspaces を共有する方法が案内されている。
影響: Native App で application_content.notebooks を使ってノートブックを共有している場合、2026年8月18日までに workspace ベースの共有へ移行する必要がある。
判定根拠: 追加行に「deprecated」
--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/manifest-reference+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/manifest-reference@@ -267,5 +267,5 @@ This field includes the following fields: -- `application_content.notebooks` (List, optional): A list of named [notebooks](/user-guide/ui-snowsight/notebooks).+- `application_content.notebooks` (List, optional): A list of named [notebooks](/user-guide/ui-snowsight/notebooks). Deprecated. Share notebooks in a workspace instead. - `application_content.workspaces` (List, optional): A list of named [workspaces](/developer-guide/declarative-sharing/workspaces). @@ -273,4 +273,15 @@ #### `application_content.notebooks.{named notebook}` field++Sharing individual notebooks with `application_content.notebooks` shares+[Legacy Notebooks](/user-guide/ui-snowsight/notebooks), and is deprecated. Starting+August 18, 2026, you can't create new application packages that share notebooks this way. Starting+November 2026, Legacy Notebooks can no longer be run or edited. For the full timeline, see+[](/release-notes/bcr-bundles/un-bundled/bcr-disable-legacy-notebooks).++Share [Snowflake Notebooks in Workspaces](/user-guide/ui-snowsight/notebooks-in-workspaces/notebooks-in-workspaces-overview)+in a workspace instead. Consumers can run and interact with those notebooks the same way, and a+workspace can also share documentation, images, and sample data files. For more information, see+[](/developer-guide/declarative-sharing/workspaces). Each named notebook supports the following name value pairs:
Native Apps の宣言的共有で Notebooks（application_content.notebooks） による個別ノートブック共有が 非推奨（deprecated） となった。2026年8月18日以降、この方法で新しいアプリケーションパッケージを作成できなくなり、2026年11月以降は Legacy Notebooks の実行・編集も不可となる。移行先として Workspaces 内の Snowflake Notebooks が案内されている。
影響: 既存の application_content.notebooks でノートブックを共有しているアプリケーション提供者は、2026年8月18日までに Workspaces ベースの共有方式へ移行する必要がある。
判定根拠: 追加行に「deprecated」
--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/limitations+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/limitations@@ -30,5 +30,5 @@ - **Workspaces**-- **Notebooks**+- **Notebooks** (deprecated) - **Tables**, including: - Dynamic tables@@ -122,4 +122,15 @@ ## Notebook Limitations +Sharing individual notebooks with `application_content.notebooks` shares+[Legacy Notebooks](/user-guide/ui-snowsight/notebooks), and is deprecated. Starting+August 18, 2026, you can't create new application packages that share notebooks this way. Starting+November 2026, Legacy Notebooks can no longer be run or edited. For the full timeline, see+[](/release-notes/bcr-bundles/un-bundled/bcr-disable-legacy-notebooks).++Share [Snowflake Notebooks in Workspaces](/user-guide/ui-snowsight/notebooks-in-workspaces/notebooks-in-workspaces-overview)+in a workspace instead. Consumers can run and interact with those notebooks the same way, and a+workspace can also share documentation, images, and sample data files. For more information, see+[](/developer-guide/declarative-sharing/workspaces).+ <dl> <dt>Read-only for consumers</dt>
Declarative Native App でノートブックを個別共有する application_content.notebooks による方法が非推奨（deprecated）となった。2026年8月18日以降、この方式で新規アプリケーションパッケージを作成できなくなり、2026年11月以降は Legacy Notebooks の実行・編集も不可となる。代替として Workspaces 経由での共有が案内され、コンテンツ一覧にも Workspaces の項目が新たに追加された。
影響: Legacy Notebooks で共有しているアプリは 2026年8月18日までに Workspaces 方式へ移行する必要があり、移行しない場合 11月以降ノートブックが利用不能になる。
判定根拠: 追加行に「deprecated」
--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/consumer/access-app-content+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/consumer/access-app-content@@ -26,4 +26,5 @@ 3. Select the app you want to access. 4. Browse the app's content, which includes:+ - **Workspaces**: If the app shares a workspace, you can browse its files and run any notebooks it contains. For more information, see [](/developer-guide/declarative-sharing/consumer/access-shared-workspace). - **Notebooks**: If the app includes notebooks, you can run them to see visualizations and other content. - **Tables and views**: You can query the tables and views that are part of the app.@@ -34,4 +35,15 @@ ## Access app notebooks++Sharing individual notebooks with `application_content.notebooks` shares+[Legacy Notebooks](/user-guide/ui-snowsight/notebooks), and is deprecated. Starting+August 18, 2026, you can't create new application packages that share notebooks this way. Starting+November 2026, Legacy Notebooks can no longer be run or edited. For the full timeline, see+[](/release-notes/bcr-bundles/un-bundled/bcr-disable-legacy-notebooks).++Share [Snowflake Notebooks in Workspaces](/user-guide/ui-snowsight/notebooks-in-workspaces/notebooks-in-workspaces-overview)+in a workspace instead. Consumers can run and interact with those notebooks the same way, and a+workspace can also share documentation, images, and sample data files. For more information, see+[](/developer-guide/declarative-sharing/workspaces). You can access the app's notebooks, either through %sf-web-interface% or through [Snowflake CLI](/developer-guide/snowflake-cli/index).
application_content.notebooks による個別ノートブック共有は Legacy Notebooks 向けであり、非推奨（deprecated） となった。2026年8月18日以降、この方法で新規アプリケーションパッケージを作成できなくなり、2026年11月以降は Legacy Notebooks の実行・編集も不可となる。代替として Snowflake Notebooks in Workspaces 経由での共有が案内されている。
影響: application_content.notebooks でノートブックを共有しているプロバイダーは、2026年8月18日までに Workspaces ベースの共有へ移行する必要がある。
判定根拠: 追加行に「deprecated」
--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/package+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/package@@ -127,4 +127,15 @@ ### Get notebook files +Sharing individual notebooks with `application_content.notebooks` shares+[Legacy Notebooks](/user-guide/ui-snowsight/notebooks), and is deprecated. Starting+August 18, 2026, you can't create new application packages that share notebooks this way. Starting+November 2026, Legacy Notebooks can no longer be run or edited. For the full timeline, see+[](/release-notes/bcr-bundles/un-bundled/bcr-disable-legacy-notebooks).++Share [Snowflake Notebooks in Workspaces](/user-guide/ui-snowsight/notebooks-in-workspaces/notebooks-in-workspaces-overview)+in a workspace instead. Consumers can run and interact with those notebooks the same way, and a+workspace can also share documentation, images, and sample data files. For more information, see+[](/developer-guide/declarative-sharing/workspaces).+ If [Snowflake Notebooks](/user-guide/ui-snowsight/notebooks) are to be included in the app, download a copy of each notebook file so you can include it in the app package.
application_content.notebooks による個別ノートブック共有は Legacy Notebooks を対象としており、非推奨（deprecated） となった。2026年8月18日以降はこの方法で新規アプリケーションパッケージを作成できなくなり、2026年11月以降は Legacy Notebooks の実行・編集も不可となる。代替として Snowflake Notebooks in Workspaces をワークスペース経由で共有する方法が案内されている。
影響: application_content.notebooks で宣言的共有アプリにノートブックを含めている場合、2026年8月18日までにワークスペース方式への移行が必要となる。
判定根拠: 追加行に「deprecated」
--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/live-editing+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/live-editing@@ -1,3 +1,14 @@ # Editing Notebooks in Declarative Shared Native Applications++Sharing individual notebooks with `application_content.notebooks` shares+[Legacy Notebooks](/user-guide/ui-snowsight/notebooks), and is deprecated. Starting+August 18, 2026, you can't create new application packages that share notebooks this way. Starting+November 2026, Legacy Notebooks can no longer be run or edited. For the full timeline, see+[](/release-notes/bcr-bundles/un-bundled/bcr-disable-legacy-notebooks).++Share [Snowflake Notebooks in Workspaces](/user-guide/ui-snowsight/notebooks-in-workspaces/notebooks-in-workspaces-overview)+in a workspace instead. Consumers can run and interact with those notebooks the same way, and a+workspace can also share documentation, images, and sample data files. For more information, see+[](/developer-guide/declarative-sharing/workspaces). - [](/developer-guide/declarative-sharing/about)
application_content.notebooks による個別ノートブック共有は Legacy Notebooks を対象としており、非推奨（deprecated） となった。2026年8月18日以降、この方法でノートブックを共有する新規アプリケーションパッケージは作成不可となり、2026年11月以降はLegacy Notebooksの実行・編集も不可となる。代替として Snowflake Notebooks in Workspaces をワークスペース経由で共有する方法が案内されている。
影響: application_content.notebooks でノートブックを共有している既存パッケージは、2026年8月18日までに Workspaces ベースの共有方式へ移行する必要がある。
判定根拠: 追加行に「deprecated」
--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/tutorials/create-share-coco+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/tutorials/create-share-coco@@ -405,4 +405,15 @@ ### Notebooks +Sharing individual notebooks with `application_content.notebooks` shares+[Legacy Notebooks](/user-guide/ui-snowsight/notebooks), and is deprecated. Starting+August 18, 2026, you can't create new application packages that share notebooks this way. Starting+November 2026, Legacy Notebooks can no longer be run or edited. For the full timeline, see+[](/release-notes/bcr-bundles/un-bundled/bcr-disable-legacy-notebooks).++Share [Snowflake Notebooks in Workspaces](/user-guide/ui-snowsight/notebooks-in-workspaces/notebooks-in-workspaces-overview)+in a workspace instead. Consumers can run and interact with those notebooks the same way, and a+workspace can also share documentation, images, and sample data files. For more information, see+[](/developer-guide/declarative-sharing/workspaces).+ - Notebooks can only access data inside the same application package. - Ensure each code cell has correct `language` metadata; otherwise SQL cells
Declarative Native Apps チュートリアルの冒頭に、application_content.notebooks による Legacy Notebooks の共有が非推奨（deprecated） である旨の警告が追加された。2026年8月18日以降、この方法で新規アプリケーションパッケージを作成できなくなり、2026年11月以降は Legacy Notebooks の実行・編集も不可となる。代替として Snowflake Notebooks in Workspaces での共有が案内されている。
影響: Legacy Notebooks を Declarative Native App で共有している場合、2026年8月18日までに Workspaces ベースの共有へ移行する必要がある。
判定根拠: 追加行に「deprecated」
--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/tutorials/getting-started+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/tutorials/getting-started@@ -1,3 +1,14 @@ # Tutorial: Getting started with %declarative-app-short-plural%++Sharing individual notebooks with `application_content.notebooks` shares+[Legacy Notebooks](/user-guide/ui-snowsight/notebooks), and is deprecated. Starting+August 18, 2026, you can't create new application packages that share notebooks this way. Starting+November 2026, Legacy Notebooks can no longer be run or edited. For the full timeline, see+[](/release-notes/bcr-bundles/un-bundled/bcr-disable-legacy-notebooks).++Share [Snowflake Notebooks in Workspaces](/user-guide/ui-snowsight/notebooks-in-workspaces/notebooks-in-workspaces-overview)+in a workspace instead. Consumers can run and interact with those notebooks the same way, and a+workspace can also share documentation, images, and sample data files. For more information, see+[](/developer-guide/declarative-sharing/workspaces). - [](/developer-guide/declarative-sharing/about)
Declarative App（宣言型アプリ）における埋め込みコードオブジェクトの共有方法が変更された。Snowflake Notebooks の共有は workspace 経由で行う方式となり、従来の application_content.notebooks を使った個別ノートブック共有は非推奨（deprecated）となった。
影響: Declarative App のプロバイダーは、ノートブック共有を application_content.notebooks から workspace 経由の方式へ移行する必要がある。
判定根拠: 追加行に「deprecated」
--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/consumer/consumer-execution+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/consumer/consumer-execution@@ -27,5 +27,8 @@ ## Embedded code objects in %declarative-app-short-plural% -The only code objects currently supported for %declarative-app-short-plural% are Snowflake Notebooks.+%declarative-app-short-plural% support Snowflake Notebooks as embedded code objects. Providers+share notebooks in a [workspace](/developer-guide/declarative-sharing/workspaces). Sharing+individual notebooks with `application_content.notebooks` is deprecated.+ Currently, %declarative-app-short-plural% can't use other types of code resources for logic, such as Streamlits, stored procedures, or UDFs. The embedded code objects in a %declarative-app-short% can only do the following:
Declarative Sharing で共有できるコードオブジェクトの説明が更新された。従来の「notebooks, stored procedures, and user-defined functions」という並列表記から、Workspaces containing notebooks を中心とした記述に変更され、単体の Notebooks は (deprecated) と明記された。 影響: 単体 Notebook の宣言的共有は非推奨となったため、今後は Workspaces 経由での共有への移行が必要になる。
判定根拠: 追加行に「deprecated」
--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/introduction+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/introduction@@ -23,5 +23,6 @@ Declarative Sharing in the %naf% enables providers to share not just data,-but code objects — notebooks, stored procedures, and user-defined functions — alongside+but code objects: workspaces containing notebooks, stored procedures, and user-defined+functions, alongside tables and views as a single data product. Providers define all shared objects in a YAML manifest file, and the framework handles privilege management, object resolution, and@@ -52,5 +53,5 @@ - [Workspaces](/developer-guide/declarative-sharing/workspaces), which can include [Snowflake Notebooks in Workspaces](/user-guide/ui-snowsight/notebooks-in-workspaces/notebooks-in-workspaces-overview)-- [Notebooks](/user-guide/ui-snowsight/notebooks-working)+- [Notebooks](/user-guide/ui-snowsight/notebooks-working) (deprecated) - [Stored procedures](/developer-guide/stored-procedure/stored-procedures-overview) - [User-defined functions](/developer-guide/udf/udf-overview)
Organization Usage ページの Premium view 一覧表で、多数のビュー（ACCESS_HISTORY, ALERT_HISTORY, CLASSES, CLASS_INSTANCES, COLUMNS, COMPLETE_TASK_GRAPHS, COPY_HISTORY, DATABASES, FEATURE_POLICIES, FILE_FORMATS, FUNCTIONS, GRANTS_TO_ROLES など）のデータ遅延（Latency）が 24 hours から 3 hours に短縮された。また、新しいビュー GRANTS_TO_SHARES が Premium view として追加された（遅延は 24 hours）。 影響: Organization Usage の Premium view を利用している場合、データ反映が最大 24 時間から 3 時間に大幅短縮され、よりリアルタイムに近い監視・分析が可能になる。
変更内容: 本文を更新（53行追加・47行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage@@ -33,5 +33,5 @@ <td>[ACCESS_HISTORY](/sql-reference/organization-usage/access_history)</td> <td>Historical</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -51,5 +51,5 @@ <td>[ALERT_HISTORY](/sql-reference/organization-usage/alert_history)</td> <td>Historical</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -99,5 +99,5 @@ <td>[CLASSES](/sql-reference/organization-usage/classes)</td> <td>Object</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -105,5 +105,5 @@ <td>[CLASS_INSTANCES](/sql-reference/organization-usage/class_instances)</td> <td>Object</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -111,5 +111,5 @@ <td>[COLUMNS](/sql-reference/organization-usage/columns)</td> <td>Object</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -117,5 +117,5 @@ <td>[COMPLETE_TASK_GRAPHS](/sql-reference/organization-usage/complete_task_graphs)</td> <td>Historical</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -171,5 +171,5 @@ <td>[COPY_HISTORY](/sql-reference/organization-usage/copy_history)</td> <td>Historical</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -201,5 +201,5 @@ <td>[DATABASES](/sql-reference/organization-usage/databases)</td> <td>Object</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -207,5 +207,5 @@ <td>[FEATURE_POLICIES](/sql-reference/organization-usage/feature_policies)</td> <td>Object</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -213,5 +213,5 @@ <td>[FILE_FORMATS](/sql-reference/organization-usage/file_formats)</td> <td>Object</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -219,5 +219,5 @@ <td>[FUNCTIONS](/sql-reference/organization-usage/functions)</td> <td>Object</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -225,4 +225,10 @@ <td>[GRANTS_TO_ROLES](/sql-reference/organization-usage/grants_to_roles)</td> <td>Object</td>+ <td>3 hours</td>+ <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td>+ </tr>+ <tr>+ <td>[GRANTS_TO_SHARES](/sql-reference/organization-usage/grants_to_shares)</td>+ <td>Object</td> <td>24 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td>@@ -231,5 +237,5 @@ <td>[GRANTS_TO_USERS](/sql-reference/organization-usage/grants_to_users)</td> <td>Object</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -255,5 +261,5 @@ <td>[LOCK_WAIT_HISTORY](/sql-reference/organization-usage/lock_wait_history)</td> <td>Historical</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -261,5 +267,5 @@ <td>[LOGIN_HISTORY](/sql-reference/organization-usage/login_history)</td> <td>Historical</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -279,5 +285,5 @@ <td>[MASKING_POLICIES](/sql-reference/organization-usage/masking_policies)</td> <td>Object</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -297,5 +303,5 @@ <td>[METERING_HISTORY](/sql-reference/organization-usage/metering_history)</td> <td>Historical</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -327,5 +333,5 @@ <td>[OBJECT_DEPENDENCIES](/sql-reference/organization-usage/object_dependencies)</td> <td>Historical</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -345,5 +351,5 @@ <td>[PASSWORD_POLICIES](/sql-reference/organization-usage/password_policies)</td> <td>Object</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -357,5 +363,5 @@ <td>[PIPES](/sql-reference/organization-usage/pipes)</td> <td>Object</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -363,5 +369,5 @@ <td>[POLICY_REFERENCES](/sql-reference/organization-usage/policy_references)</td> <td>Object</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -375,5 +381,5 @@ <td>[PROCEDURES](/sql-reference/organization-usage/procedures)</td> <td>Object</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -381,5 +387,5 @@ <td>[QUERY_ACCELERATION_ELIGIBLE](/sql-reference/organization-usage/query_acceleration_eligible)</td> <td>Historical</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -393,5 +399,5 @@ <td>[QUERY_ATTRIBUTION_HISTORY](/sql-reference/organization-usage/query_attribution_history)</td> <td>Historical</td>- <td>24 hours</td>+ <td>3 hours</td> <td>[Premium view](/user-guide/organization-accounts-premium-views) (only available in organization account).</td> </tr>@@ -399,5 +405,5 @@ <td>[QUERY_HISTORY](/sql-reference/organization-usage/query_history)</td> <td>Historical</td>- <td>24 hours</td>+ <td>3 hours</td... (truncated)
差分が長いため、途中まで表示しています。
2026年8月13日付のリリースエントリが追加された。Runtime Server・Runtime Extensions・Connectors の3コンポーネントが更新され、主な修正として CDC SQL Server のChange Trackingバッチがスキップされデータ損失が起こり得る問題の修正、CDC MySQL のBinlog PositionからGTID追跡への無停止切替対応、CDC PostgreSQLの大きなINTERVAL値の不正変換修正、JiraコネクタのフィンガープリントハッシュのMD5→SHA-256変更、Salesforceコネクタのデッドロック防止などが含まれる。 影響: CDC SQL Serverを利用している場合はデータ損失リスクの修正が含まれるため早期適用が推奨され、Jiraコネクタ利用者は既存レコードが一度だけ再更新される可能性がある点に留意が必要。
変更内容: 本文を更新（29行追加・0行削除）
--- 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,33 @@ </div> +## August 13, 2026++<a id="label-runtime-server-2026-8-13-16"></a>++### Runtime Server 2026.8.13.16++- Security patches and dependency upgrades.++<a id="label-runtime-extensions-2026-8-13-17"></a>++### Runtime Extensions 2026.8.13.17++- Openflow connectors: Fixed Gen 2 connector configuration for quoted connector names so `DESCRIBE CONNECTOR` no longer adds a second pair of quotes and reports the connector as missing or unauthorized.+- CDC Iceberg: Created integer columns as `LONG` so source integer widening does not require an unsupported Iceberg type change and 64-bit values are represented safely.+- CDC Gen 2 connectors: Connector configuration verification now reports the actual Snowflake error when an External Access Integration cannot be evaluated, instead of incorrectly reporting that no egress Network Rule allows access to the source endpoint.+- CDC MySQL: `CaptureChangeMySQL` can now be switched from Binlog Position to GTID position tracking without losing or replaying events. The connector completes the switch automatically at the next binlog rotation; no manual state cleanup or re-snapshot is required.+- CDC SQL Server: Fixed a rare data-loss window where a Change Tracking batch could be silently skipped if the destination commit failed after the batch was read.+- CDC SQL Server: Snapshot loads of tables with very large rows no longer risk filling runtime disk. Batches stop at a bounded data volume and subsequent batches resume from the exact remaining rows without configuration changes.+- CDC SQL Server: Drains large single-version Change Tracking batches with `Max Batch Size = -1` using one bounded query without an unnecessary sort, reducing `tempdb` pressure during bulk updates.+- CDC PostgreSQL: Fixed replication of large hour-based `INTERVAL` values so Snowflake receives correct ISO-8601 duration strings instead of corrupted negative values.+- Jira: Jira connector record fingerprints now use SHA-256 instead of MD5. Existing records may receive a one-time update after upgrading.++<a id="label-connectors-2026-8-13-7"></a>++### Connectors 2026.8.13.7++- Veeva Vault 0.7.0: Clarified Direct Data audit-log and ingestion-mode parameter descriptions.+- Salesforce 1.14.0: Removed downstream back pressure after batched Snowpipe Streaming publishing to prevent the Salesforce connector from deadlocking when Snowpipe Streaming errors occur.+ ## August 11, 2026
v1.21.0（2026年8月）がバージョン履歴の先頭に追加された。主な内容は macOS 向けエンタープライズ MDM 適用、エージェントモードでのファイルプレビュー拡充、繰り返し開かれる SSO サインインタブの修正。既存バージョンの内容に変更はなく、表の日付列幅の微調整のみ。 影響: macOS を MDM で管理している企業環境では v1.21.0 へのアップデートにより、デバイス管理ポリシーの適用状況を確認する必要がある。
変更内容: 本文を更新（13行追加・12行削除）
--- 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,14 +12,15 @@ ## Version history -| Version | Date | Highlights |-| ---------------------------------------------------------------------------- | --------- | --------------------------------------------------------------------------------------------------------------------- |-| [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.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 |
SYSTEM$GET_LISTING_URL_FOR_EXTERNAL_CONSUMER が Private Preview から Public Preview に昇格し、全アカウントで利用可能になった。戻り値の JSON に scope と oauth_token_uri の 2 フィールドが追加され、OAuth トークン取得に必要な情報が含まれるようになった。サンプル出力も新フィールドを反映した形に更新されている。
影響: 外部コンシューマーが Iceberg REST Catalog 経由で接続する際、新たに返却される oauth_token_uri と scope を使った OAuth 認証フローの実装が必要になる。
変更内容: 本文を更新（12行追加・8行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/functions/system_get_listing_url_for_external_consumer+++ bhttps://docs.snowflake.com/en/sql-reference/functions/system_get_listing_url_for_external_consumer@@ -22,5 +22,5 @@ # SYSTEM$GET_LISTING_URL_FOR_EXTERNAL_CONSUMER -Support for this feature is currently not in production and is available only to selected accounts.+Available to all accounts. Returns the catalog URL and catalog URI for an external listing, enabling an external consumer to connect using an Iceberg REST Catalog client.@@ -58,8 +58,10 @@ Returns a JSON object containing the following fields: -| Field | Description |-| ------------- | ---------------------------------------------------------------------------- |-| `catalog` | The catalog name the external consumer uses to identify the shared data. |-| `catalog_uri` | The Iceberg REST Catalog endpoint URL the external consumer uses to connect. |+| Field | Description |+| ----------------- | -------------------------------------------------------------------------------------------------- |+| `catalog` | The catalog name the external consumer uses to identify the shared data. |+| `catalog_uri` | The Iceberg REST Catalog endpoint URL the external consumer uses to connect. |+| `scope` | The OAuth scope required when requesting an access token for the Iceberg REST Catalog session. |+| `oauth_token_uri` | The OAuth token endpoint URL the external consumer uses to obtain an access token for the catalog. | ## Access control requirements@@ -84,5 +86,5 @@ - The external consumer must authenticate using the Programmatic Access Token (PAT) generated for their external consumer identity.-- During Private Preview, the catalog URI returns data only from the region where the provider account is located.+- During Public Preview, the catalog URI returns data only from the region where the provider account is located. - Provide both the `catalog_uri` value and the PAT to the external consumer so they can connect with an Iceberg REST Catalog client. @@ -99,6 +101,8 @@ ```json {- "catalog": "TEST_LISTING",- "catalog_uri": "https://<account_identifier>.snowflakecomputing.com/polaris/api/catalog"+ "catalog": "my-listing-GZ1Z23",+ "catalog_uri": "https://myorg-myalias.snowflakecomputing.com/polaris/open-sharing/api/catalog",+ "scope": "session:role:external",+ "oauth_token_uri": "https://myorg-myalias.snowflakecomputing.com/polaris/open-sharing/api/catalog/v1/oauth/tokens" } ```
プレビュー機能一覧に Open Data Sharing が新規追加された（2026年8月、Open提供）。Snowflake外のコンシューマーに対し、標準的なIceberg REST Catalog APIを通じてIcebergテーブルデータを読み取り専用で共有できる機能。また、Trust Center AI Security タブ（Cortex Agents一覧）のリンク先URLからアンカー #label-trust-center-ai-security-ai-agents が削除され、ページトップへのリンクに変更された。
影響: Open Data Sharing により、ETLやデータ移動なしにSnowflake外部へIcebergテーブルを直接共有できるようになるため、外部連携のアーキテクチャ検討に影響する。
変更内容: 本文を更新（8行追加・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>Open Data Sharing</td>+ <td>Open</td>+ <td>August 2026</td>+ <td>[](/user-guide/open-data-sharing)</td>+ <td>Share live, read-only Iceberg table data with consumers outside of Snowflake using standard Iceberg REST Catalog APIs, without data movement or ETL pipelines.</td>+ </tr>+ <tr> <td>Workday Live Data Query for Snowflake</td> <td>On Request</td>@@ -110,5 +117,5 @@ <td>Open</td> <td>August 2026</td>- <td>[](/user-guide/trust-center/using-the-trust-center#label-trust-center-ai-security-ai-agents)</td>+ <td>[](/user-guide/trust-center/using-the-trust-center)</td> <td>View a list of all Cortex Agents directly in the Trust Center AI Security tab, with filtering by category and per-agent details. Use it to inventory and investigate agents that fall outside your governance policy.</td> </tr>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（6行追加・2行削除）
--- ahttps://docs.snowflake.com/en/user-guide/multi-party-approval+++ bhttps://docs.snowflake.com/en/user-guide/multi-party-approval@@ -12,4 +12,8 @@ # Multi-party Approval +This feature requires Business Critical (or higher).++To inquire about upgrading, please contact [Snowflake Support](https://docs.snowflake.com/user-guide/contacting-support).+ Multi-party Approval (MPA) introduces a mandatory second-person verification step for critical Snowflake operations. With MPA enabled, no single administrator can execute a@@ -65,10 +69,10 @@ **Disabling multi-factor authentication and user security settings** (`DISABLE_MULTI_FACTOR_AUTHENTICATION`) -Requires approval for disabling Multi-Factor Authentication or resetting user passwords.+Requires approval for disabling multi-factor authentication or resetting user passwords. **Managing Tri-Secret Secure keys** (`MODIFY_TRI_SECRET_SECURE`) Requires approval for activating or deactivating Tri-Secret Secure customer-managed-encryption keys. This operation requires the Business Critical Edition (or higher).+encryption keys. After a policy with this operation has been attached to an account for 72 hours, the
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（5行追加・1行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/sql/alter-multi-party-approval-policy+++ bhttps://docs.snowflake.com/en/sql-reference/sql/alter-multi-party-approval-policy@@ -6,4 +6,8 @@ # ALTER MULTI PARTY APPROVAL POLICY++This feature requires Business Critical (or higher).++To inquire about upgrading, please contact [Snowflake Support](https://docs.snowflake.com/user-guide/contacting-support). Modifies an existing Multi-party Approval policy by replacing its body with a new@@ -126,5 +130,5 @@ <dd> -Requires approval for disabling Multi-Factor Authentication or resetting user passwords.+Requires approval for disabling multi-factor authentication or resetting user passwords. </dd>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（5行追加・1行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-multi-party-approval-policy+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-multi-party-approval-policy@@ -6,4 +6,8 @@ # CREATE MULTI PARTY APPROVAL POLICY++This feature requires Business Critical (or higher).++To inquire about upgrading, please contact [Snowflake Support](https://docs.snowflake.com/user-guide/contacting-support). Creates a new Multi-party Approval policy in the current or specified schema, or replaces@@ -111,5 +115,5 @@ <dd> -Requires approval for disabling Multi-Factor Authentication or resetting user passwords.+Requires approval for disabling multi-factor authentication or resetting user passwords. </dd>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/sql/desc-multi-party-approval-policy+++ bhttps://docs.snowflake.com/en/sql-reference/sql/desc-multi-party-approval-policy@@ -6,4 +6,8 @@ # DESCRIBE MULTI PARTY APPROVAL POLICY++This feature requires Business Critical (or higher).++To inquire about upgrading, please contact [Snowflake Support](https://docs.snowflake.com/user-guide/contacting-support). Returns the definition of a Multi-party Approval policy.
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/functions/system_update_multi_party_approval_justification+++ bhttps://docs.snowflake.com/en/sql-reference/functions/system_update_multi_party_approval_justification@@ -11,4 +11,8 @@ # SYSTEM$UPDATE_MULTI_PARTY_APPROVAL_JUSTIFICATION++This feature requires Business Critical (or higher).++To inquire about upgrading, please contact [Snowflake Support](https://docs.snowflake.com/user-guide/contacting-support). Submits or updates the business justification for a Multi-party Approval request.
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/account-usage/multi_party_approval_requests+++ bhttps://docs.snowflake.com/en/sql-reference/account-usage/multi_party_approval_requests@@ -12,4 +12,8 @@ # MULTI_PARTY_APPROVAL_REQUESTS view++This feature requires Business Critical (or higher).++To inquire about upgrading, please contact [Snowflake Support](https://docs.snowflake.com/user-guide/contacting-support). This Account Usage view provides the [Multi-party Approval](/user-guide/multi-party-approval)
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/multi_party_approval_policies+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/multi_party_approval_policies@@ -11,4 +11,8 @@ # MULTI_PARTY_APPROVAL_POLICIES view++This feature requires Business Critical (or higher).++To inquire about upgrading, please contact [Snowflake Support](https://docs.snowflake.com/user-guide/contacting-support). Available in the organization account, which requires Enterprise Edition or higher. To inquire about upgrading, please contact [Snowflake Support](https://docs.snowflake.com/user-guide/contacting-support).
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/multi_party_approval_requests+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/multi_party_approval_requests@@ -11,4 +11,8 @@ # MULTI_PARTY_APPROVAL_REQUESTS view++This feature requires Business Critical (or higher).++To inquire about upgrading, please contact [Snowflake Support](https://docs.snowflake.com/user-guide/contacting-support). Available in the organization account, which requires Enterprise Edition or higher. To inquire about upgrading, please contact [Snowflake Support](https://docs.snowflake.com/user-guide/contacting-support).
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/sql/drop-multi-party-approval-policy+++ bhttps://docs.snowflake.com/en/sql-reference/sql/drop-multi-party-approval-policy@@ -6,4 +6,8 @@ # DROP MULTI PARTY APPROVAL POLICY++This feature requires Business Critical (or higher).++To inquire about upgrading, please contact [Snowflake Support](https://docs.snowflake.com/user-guide/contacting-support). Removes a Multi-party Approval policy from the system.
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/sql/show-multi-party-approval-policies+++ bhttps://docs.snowflake.com/en/sql-reference/sql/show-multi-party-approval-policies@@ -6,4 +6,8 @@ # SHOW MULTI PARTY APPROVAL POLICIES++This feature requires Business Critical (or higher).++To inquire about upgrading, please contact [Snowflake Support](https://docs.snowflake.com/user-guide/contacting-support). Lists the Multi-party Approval policies in your account, including the creation date,
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/functions/system_cast_multi_party_approval_vote+++ bhttps://docs.snowflake.com/en/sql-reference/functions/system_cast_multi_party_approval_vote@@ -11,4 +11,8 @@ # SYSTEM$CAST_MULTI_PARTY_APPROVAL_VOTE++This feature requires Business Critical (or higher).++To inquire about upgrading, please contact [Snowflake Support](https://docs.snowflake.com/user-guide/contacting-support). Casts a vote on a pending Multi-party Approval request. An approver calls this function
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・0行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/account-usage/multi_party_approval_policies+++ bhttps://docs.snowflake.com/en/sql-reference/account-usage/multi_party_approval_policies@@ -12,4 +12,8 @@ # MULTI_PARTY_APPROVAL_POLICIES view++This feature requires Business Critical (or higher).++To inquire about upgrading, please contact [Snowflake Support](https://docs.snowflake.com/user-guide/contacting-support). This Account Usage view provides the [Multi-party Approval](/user-guide/multi-party-approval)
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（2行追加・2行削除）
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/aisql-regional-availability+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/aisql-regional-availability@@ -357,5 +357,5 @@ <td>%cm%</td> <td>%cm%</td>- <td>%cm%</td>+ <td></td> <td>%cm%</td> <td>%cm%</td>@@ -946,5 +946,5 @@ <td>%cm%</td> <td>%cm%</td>- <td>%cm%</td>+ <td></td> <td>%cm%</td> <td></td>
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/object_dependencies+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/object_dependencies@@ -68,5 +68,5 @@ ## Usage notes -- Latency for this view may be up to 24 hours.+- Latency for this view may be up to 180 minutes (3 hours). - For a complete list of supported objects and their dependency type, see [](#label-object-dependencies-supported-objects).
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/password_policies+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/password_policies@@ -194,5 +194,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). -
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/pipes+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/pipes@@ -85,5 +85,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The view only displays objects for which the current role for the session has been granted access privileges.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/policy_references+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/policy_references@@ -101,3 +101,3 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours).
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/query_acceleration_eligible+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/query_acceleration_eligible@@ -60,5 +60,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - Query acceleration is supported for the following SQL commands:
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/query_attribution_history+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/query_attribution_history@@ -124,5 +124,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - This view doesn't include records for jobs executed by [Adaptive Warehouses](/user-guide/warehouses-adaptive). - The QUERY_ATTRIBUTE_HISTORY view in the ACCOUNT_USAGE schema contains most of the same columns as the QUERY_ATTRIBUTE_HISTORY view in the ORGANIZATION_USAGE schema. For sample queries against the ACCOUNT_USAGE view, see [](#label-query-attribution-history-examples). Simply replace SNOWFLAKE.ACCOUNT_USAGE with SNOWFLAKE.ORGANIZATION_USAGE in the queries to find organization-level information.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/query_history+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/query_history@@ -156,5 +156,5 @@ ### General -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The values for the columns
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/referential_constraints+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/referential_constraints@@ -69,5 +69,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The view only displays objects for which the current role for the session has been granted access privileges.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/replication_group_refresh_history+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/replication_group_refresh_history@@ -153,5 +153,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). To view real-time refresh progress, use the [](/sql-reference/functions/replication_group_refresh_history) table function.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/resource_monitors+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/resource_monitors@@ -59,5 +59,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The view only displays objects for which the current role for the session has been granted access privileges.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/roles+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/roles@@ -58,5 +58,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The view does not include database roles for databases created from shares.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/schemata+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/schemata@@ -188,5 +188,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The view only displays objects for which the current role for the session has been granted access privileges.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/session_policies+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/session_policies@@ -157,5 +157,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). -
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/table_constraints+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/table_constraints@@ -85,5 +85,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The view only displays objects for which the current role for the session has been granted access privileges.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/table_storage_metrics+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/table_storage_metrics@@ -94,5 +94,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). -
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/tables+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/tables@@ -269,5 +269,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The view does not recognize the MANAGE GRANTS privilege and consequently may show less information compared to a SHOW command executed by a user who holds the MANAGE GRANTS privilege.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/tag_references+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/tag_references@@ -140,5 +140,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The view only displays objects for which the current role for the session has been granted access privileges.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/tags+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/tags@@ -152,5 +152,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The view only displays objects for which the current role for the session has been granted access privileges.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/task_versions+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/task_versions@@ -71,5 +71,5 @@ ## Usage notes -Latency for the view may be up to 24 hours.+Latency for the view may be up to 180 minutes (3 hours). ## Examples
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/trust_center_findings+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/trust_center_findings@@ -102,3 +102,3 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours).
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/users+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/users@@ -83,5 +83,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The `LAST_SUCCESS_LOGIN` column may have a value that differs from the `last_success_login` column in the
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/views+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/views@@ -185,5 +185,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The view does not recognize the MANAGE GRANTS privilege and consequently may show less information compared to a SHOW command
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/warehouse_events_history+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/warehouse_events_history@@ -580,5 +580,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - An event can produce multiple rows in the view if it triggers additional, related events.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/warehouse_load_history+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/warehouse_load_history@@ -70,5 +70,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - Load history is shown in 5-minute intervals.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/stages+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/stages@@ -66,5 +66,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The view only displays objects for which the current role for the session has been granted access privileges.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/storage_lifecycle_policies+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/storage_lifecycle_policies@@ -143,3 +143,3 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours).
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/snapshot_sets+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/snapshot_sets@@ -74,3 +74,3 @@ ## Usage notes -- Latency for the view may be up to 180 minutes (3 hours).+- Latency for the view may be up to 360 minutes (6 hours).
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/snapshots+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/snapshots@@ -128,3 +128,3 @@ ## Usage notes -- Latency for the view may be up to 180 minutes (3 hours).+- Latency for the view may be up to 360 minutes (6 hours).
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/snowflake-cowork/reference+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/snowflake-cowork/reference@@ -122,5 +122,5 @@ When creating an agent, we recommend selecting **Auto** for the model. This lets %sf-intelligence% automatically select the highest quality model for your account and automatically improves as new models become available. -In default mode, when an incoming question is highly similar to a verified query, %sf-intelligence% uses Arctic Text2SQL R1.5 to answer the question faster without using extended thinking. This reduces latency for common questions that already have validated SQL in the verified query repository.+In default mode, when an incoming question is highly similar to a verified query, %sf-intelligence% uses a verified-query fast path to answer the question with lower latency. If the question exactly matches a verified query, %sf-intelligence% runs that verified query's validated SQL directly, without generating new SQL. For other highly similar questions, the model that's selected for the agent generates the SQL, using the matching verified query as a reference. This reduces latency for common questions that already have validated SQL in the verified query repository. While the listed models may not be available in [all regions](#label-cortex-llm-availability), you can use %sf-intelligence% in any cloud or region by using Cortex Cross-region inference. This includes clouds and regions where the models are not available. For more information about configuring Cortex Cross-region inference, see [](/user-guide/snowflake-cortex/cross-region-inference).
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/feature_policies+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/feature_policies@@ -63,5 +63,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The LAST_ALTERED column is updated when the following operations are performed on an object:
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/file_formats+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/file_formats@@ -76,5 +76,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The view only displays objects for which the current role for the session has been granted access privileges.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/grants_to_roles+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/grants_to_roles@@ -62,5 +62,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The GRANTS_TO_ROLES view shows a subset of all supported objects. The supported set is subject to change. The view is updated periodically
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/metering_history+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/metering_history@@ -204,3 +204,3 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours).
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/sessions+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/sessions@@ -61,5 +61,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The SESSIONS view does not currently track SQL API transient sessions.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/snapshot_policies+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/snapshot_policies@@ -138,3 +138,3 @@ ## Usage notes -- Latency for the view may be up to 180 minutes (3 hours).+- Latency for the view may be up to 360 minutes (6 hours).
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/versioning+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/versioning@@ -36,5 +36,5 @@ Neither providers nor consumers can revert to a previous version of the app. -Notebooks are embedded in the application package and versioned along with the manifest.+Workspaces and notebooks are embedded in the application package and versioned along with the manifest. Notebook versioning commands, such as ALTER NOTEBOOK CREATE LIVE VERSION FROM LAST, aren't supported for these notebooks.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/classes+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/classes@@ -117,5 +117,5 @@ ## Usage notes -Latency for the view may be up to 24 hours.+Latency for the view may be up to 180 minutes (3 hours). ## Examples
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/row_access_policies+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/row_access_policies@@ -67,5 +67,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The view only returns rows if at least one row access policy has been created.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/task_history+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/task_history@@ -216,5 +216,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - For increased performance, filter queries on the COMPLETED_TIME or SCHEDULED_TIME column.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/command-reference+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/command-reference@@ -85,5 +85,5 @@ <dd> -Create a live version of the application package that can be edited. This live version is used to add or update files, such as the manifest file and notebook files.+Create a live version of the application package that can be edited. This live version is used to add or update files, such as the manifest file and workspace files. </dd>
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/dependency-databases+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/dependency-databases@@ -27,5 +27,5 @@ - Secure views in the shared database that JOIN/SELECT from tables or views in other provider databases - Views referencing UDFs or procedures that live in other databases-- Notebooks included via `application_content` if notebook logic or views queried by the notebook depend on objects in other databases+- Notebooks shared through `application_content`, if notebook logic or views queried by the notebook depend on objects in other databases - Semantic views whose underlying physical tables or views are in another database
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/class_instances+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/class_instances@@ -64,5 +64,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The view only displays the instances for which the current role for the session has been granted access privileges.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/columns+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/columns@@ -363,5 +363,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The view does not recognize the MANAGE GRANTS privilege and consequently may show less information compared to a SHOW command executed by a user who holds the MANAGE GRANTS privilege.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/complete_task_graphs+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/complete_task_graphs@@ -184,5 +184,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The view only displays objects for which the current role for the session has been granted access privileges.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/copy_history+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/copy_history@@ -76,5 +76,5 @@ ## Usage notes -- In most cases, latency for the view may be up to 24 hours. The latency for a given table's copy history may be up to 2 days+- In most cases, latency for the view may be up to 180 minutes (3 hours). The latency for a given table's copy history may be up to 2 days if both of the following conditions are true: - Fewer than 32 DML statements have been added to the given table since it was last updated in COPY_HISTORY.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/databases+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/databases@@ -142,5 +142,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The view displays all of the databases in an account.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/grants_to_users+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/grants_to_users@@ -53,5 +53,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The GRANTS_TO_USERS view **does not** include grants of privileges and non-account roles to users. For that information, see the
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/functions+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/functions@@ -91,5 +91,5 @@ ## Usage notes -- Latency for the view can be up to 24 hours.+- Latency for the view can be up to 180 minutes (3 hours). - The view only displays objects for which the current role for the session has been granted access privileges.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/storage_lifecycle_policy_history+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/storage_lifecycle_policy_history@@ -125,5 +125,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The view contains historical data for the past 12 months (one year).
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/login_history+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/login_history@@ -72,5 +72,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - `INTERNAL_SNOWFLAKE_IP/0.0.0.0` appears as the client IP for login events triggered by internal Snowflake operations that support
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/masking_policies+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/masking_policies@@ -65,5 +65,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - The view only displays objects for which the current role for the session has been granted access privileges.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/alert_history+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/alert_history@@ -206,5 +206,5 @@ ## Usage notes -- Latency for the view may be up to 24 hours.+- Latency for the view may be up to 180 minutes (3 hours). - For increased performance, filter queries on the COMPLETED_TIME or SCHEDULED_TIME column.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/udfs-sprocs+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/udfs-sprocs@@ -43,5 +43,5 @@ names of the objects and their permissions to the `manifest.yaml` file. You don't need to add the objects using separate files, as you do with-notebooks.+workspace files. The following example shows how to include a UDF and a stored procedure in the
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/anomalies_in_currency_daily+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/anomalies_in_currency_daily@@ -118,3 +118,3 @@ ## Usage notes -Latency for the view might be up to 8 hours.+Latency for the view might be up to 24 hours.
| セクション | S | A | B | C | 計 |
|---|---|---|---|---|---|
| Organization Usage | 0 | 0 | 3 | 49 | 52 |
| Developer Guide | 0 | 11 | 0 | 4 | 15 |
| SQL Commands | 0 | 0 | 5 | 0 | 5 |
| SQL Functions | 0 | 0 | 3 | 0 | 3 |
| Release Notes | 0 | 1 | 1 | 0 | 2 |
| User Guide | 0 | 1 | 1 | 0 | 2 |
| Account Usage | 0 | 0 | 2 | 0 | 2 |
| Snowflake Cortex (AI & ML) | 0 | 0 | 1 | 1 | 2 |
| Loading & Unloading Data | 0 | 0 | 1 | 0 | 1 |
| Cortex Code | 0 | 0 | 1 | 0 | 1 |