SNOWFLAKE DOCS DIFF
本日は全8,474ページ中10ページが改訂され、削除はありませんでした。変更の中心はSnowflake Cortex(AI & ML)で、分析検索に関する仕様と設定手順が更新されています。重要度はAが2件、Bが6件、Cが2件で、破壊的変更はなく、既存エージェントへの影響を抑えた機能設定の明確化が主な傾向です。
orchestration.capabilities配下で明示的に有効化する仕様へ整理されました。analytical_search が既定値 false の無効状態として明記され、エージェントの orchestration.capabilities 配下で有効化する仕様に変更されました(単独の ALTER AGENT プロパティではありません)。有効化後は SQL、REST API、Snowflake Intelligence で利用でき、Auto-routing も有効化後にのみ分析検索ループを選択します。
影響: 既存エージェントは標準検索のまま動作するため、コーパス全体の集計・傾向分析を行うには analytical_search を明示的に有効化する必要があります。
判定根拠: SQL 構文/コードブロックの増減 (+12/-2)
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-analytical-search+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-analytical-search@@ -4,4 +4,7 @@ - [](/user-guide/snowflake-cortex/cortex-agents-manage)+- [](/user-guide/snowflake-cortex/cortex-agents-rest-api)+- [](/user-guide/snowflake-cortex/snowflake-cowork/build-agents)+- [](/user-guide/snowflake-cortex/cortex-search/cortex-search-agents) - [](/user-guide/snowflake-cortex/cortex-search/cortex-search-overview) - [](/sql-reference/sql/create-cortex-search)@@ -14,4 +17,6 @@ questions requiring comprehensive analysis across hundreds or thousands of documents, including counts, aggregates, and trends. Analytical search addresses this by combining semantic search, AI functions, and SQL into one loop to answer those questions with analytical rigor over unstructured data.+After you enable it on an agent, analytical search is available wherever that agent runs: the Cortex Agents SQL commands, the REST API, and+[%sf-intelligence%](/user-guide/snowflake-cortex/snowflake-cowork). ## How analytical search works@@ -57,5 +62,6 @@ **Auto-routing** classifies query intent at runtime: simple, single-passage questions stay on the standard RAG path;-corpus-wide analytical questions trigger the analytical search loop. You don't need to specify which mode to use.+corpus-wide analytical questions trigger the analytical search loop. Auto-routing runs only after you enable analytical+search on the agent. ## Analytical search vs. traditional RAG@@ -105,34 +111,196 @@ rather than summarizing a small sample. +<a id="label-enable-analytical-search"></a>+ ## Set up analytical search -Analytical search triggers implicitly based on query intent. To set up the prerequisites, complete the following steps:+Analytical search is disabled by default (`analytical_search` is `false`). Agents that have a Cortex Search tool continue+to answer search questions using standard retrieval, but they don't run the analytical search loop. Queries that need+corpus-wide counts, aggregates, or trends then return answers based on a small retrieved sample only.++You enable analytical search once on the agent object. The same setting applies when you run the agent with SQL or the+REST API and when users interact with the agent in %sf-intelligence%.++To use analytical search, complete these steps:++1. Create a Cortex Search service, or reuse an existing one.+2. Add that Cortex Search service as a tool on the agent, and enrich the tool resources with column descriptions so the+ agent can filter and extract effectively. For the YAML and REST `columns_and_descriptions` fields, see+ [Connect Cortex Search to an agent](/user-guide/snowflake-cortex/cortex-search/cortex-search-agents#label-cortex-search-connect-agent).+ For the Snowsight **Columns Description** fields, see+ [Configure and interact with Agents](/user-guide/snowflake-cortex/cortex-agents-manage).+ For what to include in each description, see [Add detailed column descriptions](#label-analytical-search-column-descriptions).+3. Enable `analytical_search` on the agent in %sf-web-interface%, with SQL, or with the REST API. - If you already have a Cortex Search service, you can reuse it; you don't need to create a new service specifically for analytical search. - If your agent already has a Cortex Search tool configured, you don't need to add another one.--1. Create a Cortex Search service:+- `analytical_search` is a field in the agent specification under `orchestration.capabilities`. It isn't a standalone+ ALTER AGENT property.++### Create a Cortex Search service++```sql+CREATE OR REPLACE CORTEX SEARCH SERVICE <database>.<schema>.<name>+ TEXT INDEXES CHUNK, DOC_ID [, <other_text_search_columns>]+ VECTOR INDEXES CHUNK (model = 'snowflake-arctic-embed-l-v2.0') [, <other_vector_search_columns>]+ ATTRIBUTES <filter_column> [, <other_filter_columns>]+ WAREHOUSE = <warehouse_name>+ TARGET_LAG = '1 day'+ AS+ SELECT <columns>+ FROM <chunks_table>;+```++Then create an agent and add the Cortex Search service as a tool. Include column descriptions in the tool resources.+For more information, see [Configure and interact with Agents](/user-guide/snowflake-cortex/cortex-agents-manage)+and [Connect Cortex Search to an agent](/user-guide/snowflake-cortex/cortex-search/cortex-search-agents#label-cortex-search-connect-agent).++For more information on the commands used, see [](/sql-reference/sql/create-cortex-search) and [](/sql-reference/sql/create-agent).++### Enable analytical search on the agent++Set `analytical_search` to `true` on each agent where you want the analytical search loop. Set it to `false` to disable+analytical search. Use any of the following methods. They all update the same agent object, so the agent can use+analytical search from SQL, the REST API, and %sf-intelligence%.++**Method 1: Snowsight UI:**++1. In the navigation menu, select **AI & ML** %raa% **Agents**.+2. Select the agent, then select **Edit**.+3. Select **Tools**.+4. After you add a Cortex Search service, toggle **Analytical Search** on.+5. Select **Save**.++Additional costs apply when the agent uses AI functions. For more information, see [Cost considerations](#label-analytical-search-cost).++**Method 2: REST API:**++To enable analytical search on an existing agent, call the+[Update Agent](/user-guide/snowflake-cortex/cortex-agents-rest-api#label-snowflake-agents-rest-api-update)+endpoint. If the agent already has budget or other orchestration settings, include those fields in the same+`orchestration` object so they aren't removed.++```bash+curl -X PUT "$SNOWFLAKE_ACCOUNT_BASE_URL/api/v2/databases/<database>/schemas/<schema>/agents/<name>" \+ --header 'Content-Type: application/json' \+ --header 'Accept: application/json' \+ --header "Authorization: Bearer $PAT" \+ --data '{+ "orchestration": {+ "capabilities": {+ "analytical_search": true+ }+ }+ }'+```++For a new agent, include the same `orchestration.capabilities` object in the+[Create Agent](/user-guide/snowflake-cortex/cortex-agents-rest-api)+request body, along with a Cortex Search tool:++```json+{+ "name": "my_agent",+ "orchestration": {+ "capabilities": {+ "analytical_search": true+ }+ },+ "tools": [+ {+ "tool_spec": {+ "type": "cortex_search",+ "name": "my_search_tool",+ "description": "Search documents"+ }+ }+ ],+ "tool_resources": {+ "my_search_tool": {+ "search_service": "my_db.my_schema.my_search_svc"+ }+ }+}+```++**Method 3: SQL:**++For an existing agent, retrieve the complete LIVE specification, add or update `orchestration.capabilities`, then apply+the complete updated specification. `ALTER AGENT ... SET SPECIFICATION` replaces the entire specification; fields that+you omit are removed.++1. Run [](/sql-reference/sql/desc-agent) to retrieve the complete LIVE specification.+2. Add or update the following in the specification:++ ```json+ "orchestration": {+ "capabilities": {+ "analytical_search": true+ }+ }+ ```++3. Apply the complete updated specification: ```sql- CREATE OR REPLACE CORTEX SEARCH SERVICE <database>.<schema>.<name>- TEXT INDEXES CHUNK, DOC_ID [, <other_text_search_columns>]- VECTOR INDEXES CHUNK (model = 'snowflake-arctic-embed-l-v2.0') [, <other_vector_search_columns>]- ATTRIBUTES <filter_column> [, <other_filter_columns>]- WAREHOUSE = <warehouse_name>- TARGET_LAG = '1 day'- AS- SELECT <columns>- FROM <chunks_table>;+ ALTER AGENT <database>.<schema>.<agent>+ MODIFY LIVE VERSION SET SPECIFICATION = $$+ models:+ orchestration: auto++ orchestration:+ capabilities:+ analytical_search: true+ budget:+ ... (truncated)
差分が長いため、途中まで表示しています。
Analytical search が既定で無効であることを明記し、Cortex Search ツール追加後に有効化する手順へのリンクへ更新されました。UI では3つの方法すべてで設定できるよう説明が改訂され、REST API では orchestration.capabilities.analytical_search を true に設定する手順と curl 構文が追加されました。
影響: 分析検索を利用するには、追加後にUIまたはAPIで明示的に有効化する必要があります。
判定根拠: SQL 構文/コードブロックの増減 (+2/-0)
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-manage+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-manage@@ -147,5 +147,5 @@ - **Cortex Search:** Provide the Cortex Search services, along with the filters, the columns and column descriptions for filterable and searchable columns, and the maximum number of results to return.-- **Analytical search:** Enables the agent to run extensive analytics over large document collections, producing lists, counts, aggregates, and trends. Analytical search extends Cortex Search by orchestrating multi-index queries with configurable limits and using AISQL on the full result set. For more information, see [Analytical search](/user-guide/snowflake-cortex/cortex-agents-analytical-search).+- **Analytical search:** Enables the agent to run extensive analytics over large document collections, producing lists, counts, aggregates, and trends. Analytical search extends Cortex Search by orchestrating multi-index queries with configurable limits and using AISQL on the full result set. Analytical search is disabled by default. Enable it on the agent after you add a Cortex Search tool. For more information, see [Analytical search](/user-guide/snowflake-cortex/cortex-agents-analytical-search#label-enable-analytical-search). - **[Code execution](/user-guide/snowflake-cortex/cortex-agents-code-execution-tool):** Enable the built-in tool so the agent can run Python in a secure, isolated sandbox. No additional resources are required. - **Data to Chart:** Enable the tool so the agent can generate visualizations from data returned by other tools. No additional resources are required.@@ -181,5 +181,5 @@ <tr> <td>Analytical search (Public Preview)</td>- <td>The %sf-web-interface% tab that follows, as a toggle on a Cortex Search tool. See [](/user-guide/snowflake-cortex/cortex-agents-analytical-search).</td>+ <td>The tabs that follow, in all three methods. See [](/user-guide/snowflake-cortex/cortex-agents-analytical-search#label-enable-analytical-search).</td> </tr> <tr>@@ -256,5 +256,5 @@ 6. Select **Add**. - - **To enable analytical search for a Cortex Search service**: After adding a Cortex Search service, toggle **Analytical search** on to allow the agent to run extensive analytics on your search indexes. Additional costs apply when using AI Functions. For more information, see [Analytical search](/user-guide/snowflake-cortex/cortex-agents-analytical-search).+ - **To enable analytical search for a Cortex Search service**: After adding a Cortex Search service, toggle **Analytical Search** on to allow the agent to run extensive analytics on your search indexes. Analytical search is off by default. Additional costs apply when using AI functions. For more information, see [Analytical search](/user-guide/snowflake-cortex/cortex-agents-analytical-search#label-enable-analytical-search). - **To add a custom tool to the agent**: By adding custom tools, you can extend the functionality of your agents. With custom tools, the agent can call stored procedures and functions that you have defined to perform actions or do computations. This section assumes that you've already created a custom tool. For information about procedures and functions, see [](/developer-guide/extensibility).@@ -389,4 +389,20 @@ - `filterable` (boolean): Set to `true` for attribute columns that can be used in filter conditions. +- **Enable analytical search**: After the agent has a Cortex Search tool, set `orchestration.capabilities.analytical_search` to `true`. Analytical search is disabled by default. If the agent already has budget or other orchestration settings, include those fields in the same `orchestration` object so they aren't removed.++ ```bash+ curl -X PUT "$SNOWFLAKE_ACCOUNT_BASE_URL/api/v2/databases/<database-name>/schemas/<schema-name>/agents/<agent-name>" \+ --header 'Content-Type: application/json' \+ --header 'Accept: application/json' \+ --header "Authorization: Bearer $PAT" \+ --data '{+ "orchestration": {+ "capabilities": {+ "analytical_search": true+ }+ }+ }'+ ```+ - **Add data_to_chart tool**: The following example shows how to add the data to chart tool to an existing agent object. 1. Add the data_to_chart tool@@ -478,4 +494,6 @@ orchestration:+ capabilities:+ analytical_search: true tool_not_accessible: accept budget:@@ -615,4 +633,6 @@ orchestration:+ capabilities:+ analytical_search: true tool_not_accessible: accept budget:@@ -653,4 +673,9 @@ $$; ```++To enable analytical search, set `orchestration.capabilities.analytical_search` to `true` as shown in the example.+Analytical search is disabled by default. The new specification completely replaces the existing one, so include the+complete LIVE specification from `DESCRIBE AGENT`. For more information, see+[Analytical search](/user-guide/snowflake-cortex/cortex-agents-analytical-search#label-enable-analytical-search). <a id="label-snowflake-agents-review"></a>
OrchestrationConfig の説明に、analytical_search などの機能が追加されました。新たに capabilities オブジェクトが定義され、Cortex Search ツール設定時に analytical_search: true を指定すると分析検索を有効化できます(既定値は false)。
影響: 分析検索を利用するエージェントでは、リクエストの OrchestrationConfig に capabilities.analytical_search の明示的な設定が必要です。
変更内容: 本文を更新(17行追加・4行削除)
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-rest-api+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-rest-api@@ -160,6 +160,6 @@ <td>[OrchestrationConfig](#label-snowflake-agent-object-orchestrationconfig)</td> <td>- Orchestration configuration, including budget constraints (e.g.,- seconds, tokens).+ Orchestration configuration, including budget constraints (for example,+ seconds, tokens) and capabilities such as `analytical_search`. </td> </tr>@@ -479,6 +479,6 @@ <td>[OrchestrationConfig](#label-snowflake-agent-object-orchestrationconfig)</td> <td>- Orchestration configuration, including budget constraints (e.g.,- seconds, tokens).+ Orchestration configuration, including budget constraints (for example,+ seconds, tokens) and capabilities such as `analytical_search`. </td> </tr>@@ -1078,4 +1078,14 @@ </td> </tr>+ <tr>+ <td>`capabilities`</td>+ <td>object</td>+ <td>+ Optional orchestration capabilities. Set `analytical_search` to `true`+ to allow the agent to run analytical search when a Cortex Search tool is+ configured. Default: `false`. See+ [Analytical search](/user-guide/snowflake-cortex/cortex-agents-analytical-search#label-enable-analytical-search).+ </td>+ </tr> </tbody> @@ -1089,4 +1099,7 @@ "seconds": 30, "tokens": 16000+ },+ "capabilities": {+ "analytical_search": true } }
Analytical search は既定で無効であり、有効化後にのみ auto-routing がクエリ意図を判定し、標準検索または分析検索ループへ振り分けることが明記されました。設定手順として、%sf-web-interface%、SQL、REST API での有効化方法へのリンクも追加されました。 影響: 分析検索を利用するには、事前に Analytical search の有効化が必要です。
変更内容: 本文を更新(5行追加・3行削除)
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-search/cortex-search-agents+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-search/cortex-search-agents@@ -45,5 +45,7 @@ - **Corpus-wide aggregation**: "What percentage of sales calls mentioned product X in EMEA versus the US?" -For details, see [Analytical search](/user-guide/snowflake-cortex/cortex-agents-analytical-search).+For details, including how to enable analytical search, see [Analytical search](/user-guide/snowflake-cortex/cortex-agents-analytical-search#label-enable-analytical-search).++<a id="label-cortex-search-connect-agent"></a> ## Connect Cortex Search to an agent@@ -94,5 +96,5 @@ - **SQL** — Groups, counts, joins, ranks, trends, and calculates deltas. -Before executing, the agent presents an execution plan for review. **Auto-routing** classifies query intent at runtime. Simple questions stay on the standard retrieval path; corpus-wide analytical questions trigger the full analytical search loop automatically.+Before executing, the agent presents an execution plan for review. After you enable analytical search, **auto-routing** classifies query intent at runtime. Simple questions stay on the standard retrieval path; corpus-wide analytical questions trigger the full analytical search loop. -For setup instructions, recommendations, and performance considerations, see [Analytical search](/user-guide/snowflake-cortex/cortex-agents-analytical-search).+Analytical search is disabled by default. For setup instructions, including how to enable it in %sf-web-interface%, SQL, or the REST API, see [Analytical search](/user-guide/snowflake-cortex/cortex-agents-analytical-search#label-enable-analytical-search).
orchestration に capabilities.analytical_search: true を追加し、YAML と JSON の構文例に反映しました。説明文にも analytical_search などの capability が含まれることを追記しています。
影響: ALTER AGENT の orchestration 設定で analytical_search を明示的に有効化できるようになりましたが、diff からは詳細な動作は不明です。
変更内容: 本文を更新(6行追加・1行削除)
--- ahttps://docs.snowflake.com/en/sql-reference/sql/alter-agent+++ bhttps://docs.snowflake.com/en/sql-reference/sql/alter-agent@@ -101,4 +101,6 @@ orchestration:+ capabilities:+ analytical_search: true tool_not_accessible: <accept | reject | legacy> budget:@@ -142,4 +144,7 @@ }, "orchestration": {+ "capabilities": {+ "analytical_search": true+ }, "tool_not_accessible": "<accept | reject | legacy>", "budget": {@@ -209,5 +214,5 @@ <td>`orchestration`</td> <td>[](/user-guide/snowflake-cortex/cortex-agents-rest-api#label-snowflake-agent-object-orchestrationconfig)</td>- <td>An optional orchestration configuration, including budget constraints (seconds, tokens) and `tool_not_accessible` (`accept`, `reject`, or `legacy`). If `tool_not_accessible` is omitted, the default is `accept`. For details, see [](/user-guide/snowflake-cortex/cortex-agents-inaccessible-tool-handling).</td>+ <td>An optional orchestration configuration, including budget constraints (seconds, tokens), capabilities such as `analytical_search`, and `tool_not_accessible` (`accept`, `reject`, or `legacy`). If `tool_not_accessible` is omitted, the default is `accept`. For details, see [](/user-guide/snowflake-cortex/cortex-agents-inaccessible-tool-handling).</td> </tr> <tr>
orchestration に capabilities.analytical_search: true を指定できる構文例が追加され、説明にも analytical_search が利用可能な capability として追記されました。
影響: 分析検索機能を有効化する設定を CREATE AGENT の orchestration 構成に追加できますが、diff からは機能の詳細や既定値は不明です。
変更内容: 本文を更新(5行追加・1行削除)
--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-agent+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-agent@@ -84,4 +84,6 @@ orchestration:+ capabilities:+ analytical_search: true tool_not_accessible: <accept | reject | legacy> budget:@@ -142,5 +144,5 @@ <td>`orchestration`</td> <td>[](/user-guide/snowflake-cortex/cortex-agents-rest-api#label-snowflake-agent-object-orchestrationconfig)</td>- <td>An optional orchestration configuration, including budget constraints (seconds, tokens) and `tool_not_accessible` (`accept`, `reject`, or `legacy`). If `tool_not_accessible` is omitted, the default is `accept`. For details, see [](/user-guide/snowflake-cortex/cortex-agents-inaccessible-tool-handling).</td>+ <td>An optional orchestration configuration, including budget constraints (seconds, tokens), capabilities such as `analytical_search`, and `tool_not_accessible` (`accept`, `reject`, or `legacy`). If `tool_not_accessible` is omitted, the default is `accept`. For details, see [](/user-guide/snowflake-cortex/cortex-agents-inaccessible-tool-handling).</td> </tr> <tr>@@ -204,4 +206,6 @@ orchestration:+ capabilities:+ analytical_search: true tool_not_accessible: accept budget:
CoCo に与える自然言語プロンプトと、CoCo がノートブックまたはセッション内で Python コードを生成・実行する仕組みについて説明が追加されました。生成コードの確認・再利用方法としてノートブックのセルを参照すること、CoCo を使わず直接実装する場合の Snowflake ML Python API reference と概要へのリンクも追加されています。 影響: 利用者は 生成されたコードを確認・再利用でき、直接 ML コードを書く場合の参照先も明確になります。
変更内容: 本文を更新(4行追加・0行削除)
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-ml/agentic-ml+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-ml/agentic-ml@@ -10,4 +10,8 @@ CoCo is available in the CoCo CLI, CoCo Desktop, and CoCo in %sf-web-interface%, which is directly integrated with [Snowflake Notebooks](/user-guide/ui-snowsight/notebooks-in-workspaces/notebooks-in-workspaces-overview). Data scientists can use CoCo to automate the full ML lifecycle, including data exploration, feature engineering, model training, evaluation, deployment, monitoring, and debugging.++This page shows the natural-language prompts you give to CoCo. CoCo writes and runs the actual Python code for you inside your notebook or session. To see or reuse that code, check the notebook cells CoCo generates during a session.++If you prefer to write ML code directly without CoCo, see the [Snowflake ML Python API reference](/developer-guide/snowflake-ml/snowpark-ml) and the [Snowflake ML overview](/developer-guide/snowflake-ml/overview) for hands-on examples. Try out these quickstarts to get started:
インタラクティブウェアハウスは、従来のインタラクティブテーブル専用から、標準テーブル、Icebergテーブル、動的テーブル、インタラクティブテーブルを含むあらゆるテーブル種類を、コピーや変換なしで直接クエリできるよう変更されました。詳細情報への参照リンクも追加されています。 影響: 標準テーブルなどを利用する際に、標準ウェアハウスへ切り替えたりデータをコピー・変換したりする必要がなくなります。
変更内容: 本文を更新(2行追加・2行削除)
--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-interactive-warehouse+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-interactive-warehouse@@ -312,6 +312,6 @@ - When you specify the TABLES clause, cache warming begins immediately for the specified interactive tables. This process may take significant time depending on data size.-- Interactive warehouses can only query interactive tables. To query standard tables, use a standard- warehouse created with [](/sql-reference/sql/create-warehouse).+- Interactive warehouses can query any table type (standard tables, Iceberg tables, dynamic tables, and interactive tables) directly,+ without copying or transforming data. For more information, see [](/user-guide/interactive#all-table-format-support-preview). - Interactive warehouses support auto-suspend and auto-resume. The minimum AUTO_SUSPEND value is 86400 seconds (24 hours). For more information, see [](#label-interactive-resume-and-suspend-a-warehouse).
(この変更は要約対象外です。diff を参照してください)
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/snowflake-cowork/build-agents+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/snowflake-cowork/build-agents@@ -207,5 +207,5 @@ To process unstructured data, you can connect a Cortex Search tool to an agent by specifying the Cortex Search tool in the YAML specification as part of the tool resources. Cortex Search services retrieve documents and records from unstructured data sources using semantic search. The two primary use cases for Cortex Search are retrieval augmented generation (RAG) and enterprise search. For information about creating a Cortex Search service, see [](/user-guide/snowflake-cortex/cortex-search/cortex-search-overview). You can also use a Cortex Knowledge Extension (CKE) that is shared with you. -You can also use **analytical search** to go beyond standard RAG retrieval. Analytical search lets the agent run extensive analytics over large document collections, returning lists, counts, aggregates, and trends rather than just a few relevant passages. To configure analytical search, see [Analytical search](/user-guide/snowflake-cortex/cortex-agents-analytical-search). For information about powering agents with Cortex Search more broadly, see [](/user-guide/snowflake-cortex/cortex-search/cortex-search-agents).+You can also use **analytical search** to go beyond standard RAG retrieval. Analytical search lets the agent run extensive analytics over large document collections, returning lists, counts, aggregates, and trends rather than just a few relevant passages. Analytical search is supported in %sf-intelligence% and for Cortex Agents you call with SQL or the REST API. Enable it once on the agent; the same setting applies in both places. It is disabled by default. For steps, see [Analytical search](/user-guide/snowflake-cortex/cortex-agents-analytical-search#label-enable-analytical-search). For information about powering agents with Cortex Search more broadly, see [](/user-guide/snowflake-cortex/cortex-search/cortex-search-agents). When you connect a Cortex Search tool to an agent, it is especially important to include the following information about the parameters and their expected values:
(この変更は要約対象外です。diff を参照してください)
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents@@ -555,5 +555,5 @@ - Cortex Search charges depend on the size of the index and the time it has persisted. - Custom tools incur [warehouse costs](/user-guide/cost-understanding-compute), which depend on the size of the warehouse and how long it runs.-- [Analytical search](/user-guide/snowflake-cortex/cortex-agents-analytical-search) adds warehouse compute for SQL execution, plus the [AI functions](/user-guide/snowflake-cortex/aisql-cost#label-cortex-llm-cost-considerations) it calls.+- [Analytical search](/user-guide/snowflake-cortex/cortex-agents-analytical-search) adds warehouse compute for SQL execution, plus the [AI functions](/user-guide/snowflake-cortex/aisql-cost#label-cortex-llm-cost-considerations) it calls. These extra costs apply only when analytical search is enabled on the agent and the agent runs the analytical search loop. This list isn't exhaustive. Tools that run their own compute or call other services, including
| セクション | S | A | B | C | 計 |
|---|---|---|---|---|---|
| Snowflake Cortex (AI & ML) | 0 | 2 | 2 | 2 | 6 |
| SQL Commands | 0 | 0 | 3 | 0 | 3 |
| Snowflake ML | 0 | 0 | 1 | 0 | 1 |