ドキュメント変更履歴 2026-08-22

--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-rest-api+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-rest-api@@ -75,5 +75,5 @@ Before you begin, you need: -1. Your **Snowflake account URL** (e.g., `https://<account-identifier>.snowflakecomputing.com`).+1. Your **Snowflake account URL** (for example, `https://<account-identifier>.snowflakecomputing.com`). 2. A **Snowflake Programmatic Access Token (PAT)** for authentication. See [](#label-pat-generate). 3. A **model name** to use in requests. See [](#label-cortex-complete-llm-model-availability) for available models.@@ -350,4 +350,79 @@   <tbody>     <tr>+      <td>`claude-opus-5`</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+    </tr>+    <tr>+      <td>`claude-opus-4-8`</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+    </tr>+    <tr>+      <td>`claude-opus-4-7`</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+    </tr>+    <tr>+      <td>`claude-opus-4-6`</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+    </tr>+    <tr>+      <td>`claude-opus-4-5`</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+    </tr>+    <tr>       <td>`claude-sonnet-5`</td>       <td>%cm%</td>@@ -365,133 +440,88 @@     </tr>     <tr>-      <td>`claude-opus-5`</td>+      <td>`claude-sonnet-4-6`</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+    </tr>+    <tr>+      <td>`claude-sonnet-4-5`</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td>%cm%</td>+      <td></td>+    </tr>+    <tr>+      <td>`claude-4-sonnet`</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+    </tr>+    <tr>+      <td>`claude-haiku-4-5`</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+    </tr>+    <tr>+      <td>`openai-gpt-5.6`</td>       <td>\*</td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+    </tr>+    <tr>+      <td>`openai-gpt-5.5`</td>       <td>\*</td>-      <td>\*</td>-      <td></td>-      <td></td>-      <td></td>-      <td>\*</td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-    </tr>-    <tr>-      <td>`claude-opus-4-8`</td>-      <td>\*</td>-      <td>\*</td>-      <td>\*</td>-      <td></td>-      <td></td>-      <td></td>-      <td>\*</td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-    </tr>-    <tr>-      <td>`claude-opus-4-7`</td>-      <td>\*</td>-      <td>\*</td>-      <td>\*</td>-      <td></td>-      <td></td>-      <td></td>-      <td>\*</td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-    </tr>-    <tr>-      <td>`claude-sonnet-4-6`</td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td></td>-      <td></td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-    </tr>-    <tr>-      <td>`claude-opus-4-6`</td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td></td>-      <td></td>-      <td></td>-      <td>%cm%</td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-    </tr>-    <tr>-      <td>`claude-sonnet-4-5`</td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td></td>-      <td></td>-      <td>%cm%</td>-      <td></td>-    </tr>-    <tr>-      <td>`claude-opus-4-5`</td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td></td>-      <td></td>-      <td></td>-      <td>%cm%</td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-    </tr>-    <tr>-      <td>`claude-haiku-4-5`</td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td></td>-      <td></td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td></td>-      <td></td>-      <td></td>-      <td></td>-    </tr>-    <tr>-      <td>`claude-4-sonnet`</td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td></td>-      <td></td>-      <td>%cm%</td>-      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>+      <td></td>       <td></td>       <td></td>@@ -919,5 +949,5 @@ </div> -***** Indicates a preview function or model. Preview features are not suitable for production workloads.+\* Indicates a preview function or model. Preview features are not suitable for production workloads.  You can also use any [fine-tuned](/user-guide/snowflake-cortex/cortex-finetuning) model in any supported region.@@ -2837,5 +2867,5 @@ | Field      | Type   | Description                                                                                                                                                                                                                                                                                 | | ---------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |-| `model`    | string | The model to use (see [](#label-cortex-complete-llm-model-availability)). You may also use the fully-qualified name of any [fine-tuned](/user-guide/snowflake-cortex/cortex-finetuning) model in the format <code className="samp"><em>database</em>.<em>schema</em>.<em>model</em></code>. |+| `model`    | string | The model to use (see [](#label-cortex-complete-llm-model-availability)). You may also use the fully qualified name of any [fine-tuned](/user-guide/snowflake-cortex/cortex-finetuning) model in the format <code className="samp"><em>database</em>.<em>schema</em>.<em>model</em></code>. | | `messages` | array  | An array of message objects representing the conversation. Each message must have a `role` (`system`, `user`, `assistant`, or `tool`) and `content` (string or array of content parts).                                            ... (truncated) 

差分が長いため、途中まで表示しています。

--- ahttps://docs.snowflake.com/en/migrations/sma-docs/issue-analysis/issue-codes-by-source/spark-scala/README+++ bhttps://docs.snowflake.com/en/migrations/sma-docs/issue-analysis/issue-codes-by-source/spark-scala/README@@ -1,11 +1,2 @@-<dl className="field-list">-<dt>description<span className="colon">:</span></dt>-<dd>--org.apache.spark.sql.functions.covar_pop--</dd>-</dl>- # Snowpark Migration Accelerator: Issue Codes for Spark - Scala @@ -532,11 +523,11 @@ ### Description -This issue appears when the SMA detects a SQL-embedded code that can not be processed. Then, the SQL-embedded code can not be converted to Snowflake.--#### Scenario--**Input**--Below is an example of a SQL-embedded code that can not be processed.+This issue appears when the SMA detects a SQL-embedded code that can't be processed. Then, the SQL-embedded code can't be converted to Snowflake.++#### Scenario++**Input**++Below is an example of a SQL-embedded code that can't be processed.  ```scala@@ -546,5 +537,5 @@ **Output** -The SMA adds the EWI `SPRKSCL1173` to the output code to let you know that the SQL-embedded code can not be processed.+The SMA adds the EWI `SPRKSCL1173` to the output code to let you know that the SQL-embedded code can't be processed.  ```scala@@ -570,11 +561,11 @@ ### Description -This issue occurs when the current processing element is not a literal, then it can not be evaluated by SMA.--#### Scenario--**Input**--Below is an example when element to process is not a literal and it can not be evaluated by SMA.+This issue occurs when the current processing element is not a literal, then it can't be evaluated by SMA.++#### Scenario++**Input**++Below is an example when element to process is not a literal and it can't be evaluated by SMA.  ```scala@@ -585,5 +576,5 @@ **Output** -The SMA adds the EWI `SPRKSCL1163` to the output code to let you know that `format_type` parameter is not a literal and it can not be evaluated by the SMA.+The SMA adds the EWI `SPRKSCL1163` to the output code to let you know that `format_type` parameter is not a literal and it can't be evaluated by the SMA.  ```scala@@ -906,17 +897,17 @@ ## SPRKSCL1172 -Message: Snowpark does not support StructFiled with metadata parameter.--Category: Warning--### Description--This issue appears when the SMA detects that [org.apache.spark.sql.types.StructField.apply](https://spark.apache.org/docs/latest/api/scala/org/apache/spark/sql/types/StructField.html) with [org.apache.spark.sql.types.Metadata](https://spark.apache.org/docs/latest/api/scala/org/apache/spark/sql/types/Metadata.html) as parameter. This is because Snowpark does not supported the metadata parameter.--#### Scenario--**Input**--Below is an example of the `org.apache.spark.sql.types.StructField.apply` function that generates this EWI. In this example, the `apply` function is used to generate and instance of StructField.+Message: Snowpark does not support StructField with metadata parameter.++Category: Warning++### Description++This issue appears when the SMA detects that [org.apache.spark.sql.types.StructField.apply](https://spark.apache.org/docs/latest/api/scala/org/apache/spark/sql/types/StructField.html) with [org.apache.spark.sql.types.Metadata](https://spark.apache.org/docs/latest/api/scala/org/apache/spark/sql/types/Metadata.html) as parameter. This is because Snowpark does not support the metadata parameter.++#### Scenario++**Input**++Below is an example of the `org.apache.spark.sql.types.StructField.apply` function that generates this EWI. In this example, the `apply` function is used to generate an instance of StructField.  ```scala@@ -929,5 +920,5 @@  ```scala-/*EWI: SPRKSCL1172 => Snowpark does not support StructFiled with metadata parameter.*/+/*EWI: SPRKSCL1172 => Snowpark does not support StructField with metadata parameter.*/ val result = StructField("f1", StringType(), True, metadata) ```@@ -1230,5 +1221,5 @@ ### Description -This issue appears when the SMA detects some statement that cannot correctly read or understand in the code of a file, it is called as **parsing error**, however the SMA can recovery from that parsing error and continue analyzing the code of the file. In this case, the SMA is able to process the code of the file without errors.+This issue appears when the SMA detects some statement that it cannot correctly read or understand in the code of a file — this is called a **parsing error**. However, the SMA can recover from that parsing error and continue analyzing the code of the file. In this case, the SMA is able to process the code of the file without errors.  #### Scenario@@ -1407,5 +1398,5 @@ ### Description -This issue appears when the SMA detects a method that is not supported by Snowflake in the SparkBuilder method chaining. Therefore, it might affects the migration of the reader statement.+This issue appears when the SMA detects a method that is not supported by Snowflake in the SparkBuilder method chaining. Therefore, it might affect the migration of the reader statement.  The following are the not supported SparkBuilder methods:@@ -1433,5 +1424,5 @@ **Output** -The SMA adds the EWI `SPRKSCL1103` to the output code to let you know that master, appName and enableHiveSupport methods are not supported by Snowpark. Then, it might affects the migration of the Spark Session statement.+The SMA adds the EWI `SPRKSCL1103` to the output code to let you know that master, appName and enableHiveSupport methods are not supported by Snowpark. Then, it might affect the migration of the Spark Session statement.  ```scala@@ -1619,5 +1610,5 @@ **Output** -Since the tool can not determine the value of the variable in runtime, shows the EWI `SPRKSCL1163` indicating that the value is not supported.+Since the tool can't determine the value of the variable in runtime, shows the EWI `SPRKSCL1163` indicating that the value is not supported.  ```scala@@ -1877,5 +1868,5 @@ **Output** -Since the tool can not determine the value of the variable in runtime, shows the EWI `SPRKSCL1163` indicating that the value is not supported.+Since the tool can't determine the value of the variable in runtime, shows the EWI `SPRKSCL1108` indicating that the value is not supported.  ```scala@@ -1968,5 +1959,5 @@ **Output** -The SMA adds the EWI `SPRKSCL1169` to the output code to let you know that load function call is missing on the method chaining and SMA can not analyze the statement.+The SMA adds the EWI `SPRKSCL1169` to the output code to let you know that load function call is missing on the method chaining and SMA can't analyze the statement.  ```scala@@ -2576,5 +2567,5 @@ **Recommended fix** -Since Snowflake does not supported regex patterns, try to replace the pattern by a not regex pattern string.+Since Snowflake does not support regex patterns, try to replace the pattern by a not regex pattern string.  ##### Scenario 3@@ -2601,5 +2592,5 @@ **Recommended fix** -Since Snowflake does not supported split function with more than two parameters, try to use the split function supported by Snowflake.+Since Snowflake does not support split function with more than two parameters, try to use the split function supported by Snowflake.  #### Additional recommendations@@ -2721,10 +2712,4 @@  - For more support, you can email us at [sma-support@snowflake.com](mailto:sma-support@snowflake.com) or post an issue [in the SMA](/migrations/sma-docs/user-guide/project-overview/configuration-and-settings).-------description: &gt;--Snowpark and Snowpark Extensions were not added to the project configuration-file.  ---@@ -3003,5 +2988,5 @@ **Output** -The SMA adds the EWI `SPRKSCL1104` to the output code to let you know config method is not supported by Snowpark. Then, it is not possible to set options in the Spark Session via config function and it might affects the migration of the ... (truncated) 

差分が長いため、途中まで表示しています。

--- ahttps://docs.snowflake.com/en/user-guide/intro-regions+++ bhttps://docs.snowflake.com/en/user-guide/intro-regions@@ -72,5 +72,5 @@       <td>us-west-2</td>       <td>US West (Oregon)</td>-      <td>Also supports some U.S. government compliance. See [](#label-us-gov-regions).</td>+      <td>Supports U.S. government compliance (see next section for details).</td>     </tr>     <tr>@@ -82,5 +82,5 @@       <td>us-east-1</td>       <td>US East (N. Virginia)</td>-      <td>Also supports some U.S. government compliance. See [](#label-us-gov-regions).</td>+      <td>Supports U.S. government compliance (see next section for details).</td>     </tr>     <tr>@@ -130,5 +130,5 @@       <td>southcentralus</td>       <td>South Central US (Texas)</td>-      <td>Also supports some U.S. government compliance (see next section for details).</td>+      <td>Supports U.S. government compliance (see next section for details).</td>     </tr>     <tr>@@ -148,7 +148,7 @@ ![Map of U.S. cloud regions that support public sector/government workloads](/static/images/snowflake-regions-us-gov.png) -Snowflake makes the following regions available to customers that require compliance with common U.S. Federal and state government-standards. These regions are only supported for Snowflake accounts on [Business Critical Edition](/user-guide/intro-regions)-(or higher).+Snowflake makes the following regions available to customers that require compliance with common U.S.+Federal and state government standards. Compliance with such standards is only supported for Snowflake accounts+on Business Critical Edition (or higher).  If your Snowflake account is in a [U.S. government region](#label-us-gov-regions) and you want to access data products that are@@ -176,5 +176,5 @@       <th>Cloud Region ID</th>       <th>Region Name</th>-      <th>Compliance standards</th>+      <th>Supported Workloads</th>     </tr>   </thead>@@ -190,11 +190,11 @@       <td> -- [FedRAMP (Moderate)](/user-guide/cert-fedramp)+- [FedRAMP Class C (Moderate)](/user-guide/cert-fedramp) - [GovRAMP (Moderate)](/user-guide/cert-stateramp) - [TX-RAMP (Level 2)](/user-guide/cert-txramp)-- FIPS 140-2-- DOJ Criminal Justice Information Systems (CJIS) Security Policy - Requires Supplemental Contract Terms+- FIPS 140-2 and 140-3+- NIST 800-171+- [DOJ CJIS Security Policy](/user-guide/cert-cjis) - Requires Supplemental Contract Terms - IRS Publication 1075 - Requires Supplemental Contract Terms-- NIST 800-171  </td>@@ -203,5 +203,7 @@       <td>us-east-1</td>       <td>US East (N. Virginia)</td>-      <td>- [TX-RAMP (Level 2)](/user-guide/cert-txramp)</td>+      <td>+- [TX-RAMP (Level 2)](/user-guide/cert-txramp)+</td>     </tr>     <tr>@@ -210,10 +212,11 @@       <td> -- [FedRAMP (Moderate)](/user-guide/cert-fedramp)+- [FedRAMP Class C (Moderate)](/user-guide/cert-fedramp) - [GovRAMP (Moderate)](/user-guide/cert-stateramp) - [TX-RAMP (Level 2)](/user-guide/cert-txramp)-- FIPS 140-2-- DOJ Criminal Justice Information Systems (CJIS) Security Policy - Requires Supplemental Contract Terms+- FIPS 140-2 and 140-3+- [DOJ CJIS Security Policy](/user-guide/cert-cjis) - Requires Supplemental Contract Terms - IRS Publication 1075 - Requires Supplemental Contract Terms+ - NIST 800-171 @@ -247,18 +250,13 @@ <dd> -Snowflake makes the following SnowGov Regions on AWS GovCloud (US) and Microsoft Azure Government-available to customers who require additional security designed for US government regulated workloads and other types of sensitive data.-These regions are operated by Snowflake personnel who are U.S. persons located within the U.S. Certain features that are available in-Snowflake's commercial regions might not be available or might be different in its SnowGov Regions. Use of and access to Snowflake in any of-the SnowGov Regions are limited solely to U.S. Government Customers or U.S. Government Contractors (unless otherwise agreed upon by-Snowflake in its sole discretion) and are subject to Snowflake's [U.S. SnowGov Region Terms of Service](https://www.snowflake.com/en/legal-gov/terms-of-service/us-snowgov-terms-of-service/). As used here, a-"U.S. Government Customer" means a Snowflake customer that is: (a) a U.S. Federal, state, or local government entity or (b) a tribal-government entity; and a "U.S. Government Contractor" means a commercial entity that is required to process data provided by a U.S.-Government Customer to perform a prime contract or subcontract with or for such entity.--The SnowGov Regions support U.S. government standards, such as FedRAMP, Department of War Impact Levels, GovRAMP, TX-RAMP, FIPS-140-2, and the-International Traffic in Arms Regulations (ITAR) among others. As noted in the table below, certain standards require the customer to-accept supplemental contract terms. You must contact Snowflake and agree to the supplemental terms before uploading workloads covered by-these standards.+Snowflake makes the following SnowGov Regions on AWS GovCloud (US) and Microsoft Azure Government available to customers who require additional+security designed for US government regulated workloads and other types of sensitive data. Certain features that are available in Snowflake’s+commercial regions might not be available or might be different in its SnowGov Regions. Use of and access to Snowflake in any of the SnowGov+Regions are limited solely to U.S. Government Customers or U.S. Government Contractors+(unless otherwise agreed upon by Snowflake in its sole discretion) and are subject to Snowflake’s U.S. SnowGov Region Terms of Service.++The SnowGov Regions support U.S. government standards, such as FedRAMP, Department of War (DoW) Impact Levels, GovRAMP, TX-RAMP, FIPS, and+the International Traffic in Arms Regulations (ITAR) among others. As noted in the table below, certain standards require the customer to+accept supplemental contract terms. You must contact Snowflake and agree to the supplemental terms before uploading workloads covered by these standards.  Self-provisioning of initial Snowflake accounts is not available in the SnowGov Regions. To provision an initial account in these regions,@@ -293,6 +291,6 @@       <td> -- [FedRAMP (High)](/user-guide/cert-fedramp)-- [Department of War (DoW) Impact Level 4 (IL4)](/user-guide/cert-dodIL5)+- [FedRAMP Class D (High)](/user-guide/cert-fedramp)+- [DoW Impact Level 4 (IL4)](/user-guide/cert-dodIL5) - [GovRAMP (High)](/user-guide/cert-stateramp) - [TX-RAMP (Level 2)](/user-guide/cert-txramp)@@ -306,6 +304,6 @@ - DFARS 252.204-7012 - DFARS 252.239-7010-- DoJ [CJIS](/user-guide/cert-cjis) Security Policy-- IRS Publication 1075+- [DOJ CJIS Security Policy](/user-guide/cert-cjis) - Requires Supplemental Contract Terms+- IRS Publication 1075 - Requires Supplemental Contract Terms  </td>@@ -316,6 +314,6 @@       <td> -- [FedRAMP High](/user-guide/cert-fedramp)-- [DoW IL4](/user-guide/cert-dodIL5)+- [FedRAMP Class D (High)](/user-guide/cert-fedramp)+- [DoW Impact Level 4 (IL4)](/user-guide/cert-dodIL5) - [GovRAMP (High)](/user-guide/cert-stateramp) - [TX-RAMP (Level 2)](/user-guide/cert-txramp)@@ -329,6 +327,6 @@ - DFARS 252.204-7012 - DFARS 252.239-7010-- DoJ [CJIS](/user-guide/cert-cjis) Security Policy-- IRS Publication 1075+- [DOJ CJIS Security Policy](/user-guide/cert-cjis) - Requires Supplemental Contract Terms+- IRS Publication 1075 - Requires Supplemental Contract Terms  </td>@@ -339,7 +337,6 @@       <td> -- [DoW IL5](/user-guide/cert-dodIL5)-- BCAP-- FIPS 140-2+- [DoW Impact Level 5 (IL5)](/user-guide/cert-dodIL5)+- FIPS 140-2 and 140-3 - NIST 800-171 - [](/user-guide/cert-itar)@@ -350,6 +347,6 @@ - DFARS 252.204-7012 - DFARS 252.239-7010-- DoJ [CJIS](/user-guide/cert-cjis) Security Policy-- IRS Publication 1075+- [DOJ CJIS Security Policy](/user-guide/cert-cjis) - Requires Supplemental Contract Terms+- IRS Publica... (truncated) 

差分が長いため、途中まで表示しています。

--- ahttps://docs.snowflake.com/en/migrations/snowconvert-docs/general/technical-documentation/issues-and-troubleshooting/conversion-issues/generalEWI+++ bhttps://docs.snowflake.com/en/migrations/snowconvert-docs/general/technical-documentation/issues-and-troubleshooting/conversion-issues/generalEWI@@ -19,5 +19,5 @@ #### Example Code -The following example illustrates different parsing error scenarios where invalid syntax is placed in the input. Notice how the message varies between every scenario, these contents may be helpful on isolating and fixing the issue. For more information check "Message Contents" below.+The following example illustrates different parsing error scenarios where invalid syntax is placed in the input. Notice how the message varies between every scenario; these contents may be helpful in isolating and fixing the issue. For more information check "Message Contents" below.  ##### Input Code:&#x20;@@ -99,5 +99,5 @@ Default Parameters May Need To Be Reordered -This EWI is deprecated. SnowConvert AI now automatically reorders default parameters to the end of the parameter list instead of emitting this warning. Please refer to [SSC-FDM-0041](../functional-difference/generalFDM#ssc-fdm-0041) for the updated behavior.+This EWI is deprecated. SnowConvert AI now automatically reorders default parameters to the end of the parameter list instead of emitting this warning. Please refer to [SSC-FDM-0041](/migrations/snowconvert-docs/general/technical-documentation/issues-and-troubleshooting/functional-difference/generalFDM#ssc-fdm-0041) for the updated behavior.  ### Severity@@ -215,5 +215,5 @@ #### Description -This error is added because Snowflake does not support date/numeric formats in some functions as is supported in the source language.+This error is added because Snowflake does not support date/numeric formats in some functions as the source language does.  The following format elements are the ones that may behave differently in [Snowflake](https://docs.snowflake.com/en/sql-reference/functions-conversion#label-date-time-format-conversion):&#x20;@@ -225,11 +225,11 @@ For more information please refer to [PostgreSQL Date/Time formats](https://www.postgresql.org/docs/current/functions-formatting.html#FUNCTIONS-FORMATTING-DATETIME-TABLE). -The transformation of the TO\_CHAR function supports most of this format elements, for a full list of suppported format elements and their equivalent mappings please refer to the [Translation specification](../../../../translation-references/redshift/redshift-functions#for-datetime-values)--### BigQuery Format <a href="#r_numeric_formating" id="r_numeric_formating"></a>+The transformation of the TO\_CHAR function supports most of these format elements, for a full list of supported format elements and their equivalent mappings please refer to the [Translation specification](/migrations/snowconvert-docs/translation-references/redshift/redshift-functions#for-datetime-values)++### BigQuery Format <a href="#r_bigquery_format" id="r_bigquery_format"></a>  Review the [BigQuery format elements reference](https://cloud.google.com/bigquery/docs/reference/standard-sql/format-elements). -### Numeric <a href="#r_numeric_formating" id="r_numeric_formating"></a>+### Numeric <a href="#r_numeric_formatting" id="r_numeric_formatting"></a>  | Pattern  | Description                                  |@@ -339,5 +339,5 @@ #### Description -Currently, there is no support in Snowflake for extended regular expression beyond the [POSIX Basic Regular Expression syntax](https://en.wikipedia.org/wiki/Regular_expression#POSIX_basic_and_extended).+Currently, there is no support in Snowflake for extended regular expressions beyond the [POSIX Basic Regular Expression syntax](https://en.wikipedia.org/wiki/Regular_expression#POSIX_basic_and_extended).  This EWI is added every time a function call to _REGEX\_SUBSTR, REGEX\_REPLACE,_ or _REGEX\_INSTR_  is transformed to Snowflake to warn the user about possible unsupported regular expressions. Some of the features **not supported** are lookahead, lookbehind, and non-capturing groups.&#x20;@@ -679,5 +679,5 @@ #### MULTIPLE FUNCTION -Multiple function is not supported for PIVOT clauses, sometimes multiple function queries could be re-written using case statements, see the following Teradata sample for more information [https://docs.teradata.com/r/756LNiPSFdY\~4JcCCcR5Cw/L0kKSOrOeu\_68mcW3o8ilw](https://docs.teradata.com/r/756LNiPSFdY~4JcCCcR5Cw/L0kKSOrOeu_68mcW3o8ilw)+Multiple function is not supported for PIVOT clauses, sometimes multiple function queries could be re-written using case statements. See the following Teradata sample for more information [https://docs.teradata.com/r/756LNiPSFdY\~4JcCCcR5Cw/L0kKSOrOeu\_68mcW3o8ilw](https://docs.teradata.com/r/756LNiPSFdY~4JcCCcR5Cw/L0kKSOrOeu_68mcW3o8ilw)  ##### Example Code@@ -960,5 +960,5 @@ #### Best Practices -* If this error happens is because there is no Snowflake equivalent for the node that is being converted.&#x20;+* If this error happens, it is because there is no Snowflake equivalent for the node that is being converted.&#x20; * If you need more support, you can email us at [snowconvert-support@snowflake.com](mailto:snowconvert-support@snowflake.com) @@ -1065,5 +1065,5 @@ #### Best Practices -* Make sure all the dependencies(tables and views) related to the procedure statement are being migrated.+* Make sure all the dependencies (tables and views) related to the procedure statement are being migrated. * If you need more support, you can email us at [snowconvert-support@snowflake.com](mailto:snowconvert-support@snowflake.com) @@ -1394,5 +1394,4 @@ #### Best Practices -* Check if a cast to a Date, Time, or Timestamp is necessary for the binding. Some cases are not necessary because an implicit conversion is done to the value. * If you need more support, you can email us at [snowconvert-support@snowflake.com](mailto:snowconvert-support@snowflake.com) @@ -1442,5 +1441,5 @@ ## SSC-EWI-0029 -External table data format not supported in snowflake+External table data format not supported in Snowflake  ### Severity@@ -1856,7 +1855,7 @@  * Please refer to the following links to check the current transformation of the specific function you are trying to convert:-  * [Oracle built-in functions](../../../../translation-references/oracle/functions/README)-  * [Teradata built-in functions](../../../../translation-references/teradata/sql-translation-reference/teradata-built-in-functions)-  * [SQL Server built-in functions](../../../../translation-references/transact/transact-built-in-functions)+  * [Oracle built-in functions](/migrations/snowconvert-docs/translation-references/oracle/functions/README)+  * [Teradata built-in functions](/migrations/snowconvert-docs/translation-references/teradata/sql-translation-reference/teradata-built-in-functions)+  * [SQL Server built-in functions](/migrations/snowconvert-docs/translation-references/transact/transact-built-in-functions) * If you need more support, you can email us at [snowconvert-support@snowflake.com](mailto:snowconvert-support@snowflake.com) @@ -1969,5 +1968,5 @@ #### Best Practices -* Make sure all the dependencies(tables and views) related to the procedure statement are being migrated.+* Make sure all the dependencies (tables and views) related to the procedure statement are being migrated. * If you need more support, you can email us at [snowconvert-support@snowflake.com](mailto:snowconvert-support@snowflake.com) @@ -2031,5 +2030,5 @@ #### Description -_**CHECK**_ constraint is not supported by Snowflake but it does not affect functionally.&#x20;+_**CHECK**_ constraint is not supported by Snowflake but it does not affect functionality.&#x20;  #### Example Code@@ -2207,5 +2206,5 @@ The file has an unexpected encoding and was not translated -This `EWI` is deprecated, please refer to [SSC... (truncated) 

差分が長いため、途中まで表示しています。

--- ahttps://docs.snowflake.com/en/migrations/aim-for-datawarehouses/code-conversion/function-references/teradata+++ bhttps://docs.snowflake.com/en/migrations/aim-for-datawarehouses/code-conversion/function-references/teradata@@ -14,5 +14,5 @@ ### Parameters -`INPUT` TimeSTAMP_TZ+`INPUT` TIMESTAMP_TZ  The method to extract the quarter number.@@ -58,5 +58,5 @@ ### Returns -A whole number from 1 to 371.+A whole number from 1 to 365 (or 366 in leap years).  ### Example@@ -366,5 +366,5 @@ `RESULTCASE` VARCHAR -The format in which the result should be displayed. Valid options are 'uppercase', 'lowercase', or 'capitalized'.+The format in which the result should be displayed. Valid options are 'uppercase', 'lowercase', or 'firstOnly'.  ### Returns@@ -490,5 +490,5 @@ The time duration that will be converted into seconds. -`INPUT_VALUE` VARCHAR - The input parameter that accepts text data. - The input parameter that accepts text data.+`INPUT_VALUE` VARCHAR - The input parameter that accepts text data.  The time interval type for conversion. Examples include 'DAY', 'DAY TO HOUR', and other valid interval types.@@ -674,5 +674,5 @@ ### Parameters -`TIME` is a data type used to store time values in hours, minutes, seconds, and fractions of seconds. is a data type that represents a time value stored as a text string.+`TIME` is a data type used to store time values in hours, minutes, seconds, and fractions of seconds.  The timestamp that will be used as an anchor point.@@ -821,5 +821,5 @@ ### Returns -A `varchar` containing the abbreviated name of a month (e.g., "Jan", "Feb", etc.).+A `varchar` containing the abbreviated name of a month (for example, "Jan", "Feb", and so on).  ### Usage example@@ -930,5 +930,5 @@ A user-defined function (UDF) that replicates the P_INTERSECT operator. This function compares two or more time periods and identifies where they overlap, returning the common time interval between them. -Creates a string representation of a period's start and end values (for `TIMESTAMP` represents a data type that stores both date and time information., `TIME`, or `DATE` is a data type used to store calendar dates (year, month, and day) without time information. data types). This function emulates Teradata's period value constructor function. The output string follows Snowflake's default format for `PERIOD` values. To adjust the precision of the output, you can either:+Creates a string representation of a period's start and end values (for `TIMESTAMP`, `TIME`, or `DATE` data types). This function emulates Teradata's period value constructor function. The output string follows Snowflake's default format for `PERIOD` values. To adjust the precision of the output, you can either:  - Modify the session parameter `timestamp_output_format`@@ -1102,5 +1102,5 @@ ### Returns -The function returns either 0 or 1.+The function returns a score between 0 (completely different) and 1 (identical).  ### Usage example@@ -1365,5 +1365,5 @@ ### Definition -UDFs (User-Defined Functions) that handle subtraction operations between an interval value and a column reference of type interval.+UDFs (User-Defined Functions) that handle addition and subtraction operations between an interval value and a column reference of type interval.  ```sql@@ -1401,5 +1401,5 @@ ### Returns -A `varchar` value that represents the result of subtracting two time intervals.+A `varchar` value that represents the result of adding or subtracting two time intervals.  ### Migration example@@ -1710,5 +1710,5 @@ ```sql :force:-SELECT ROW_COUNT_UDF(DIFFTTIME_PERIOD('SECONDS','2022-11-26 10:15:20.000*2022-11-26 10:15:25.000'));+SELECT ROW_COUNT_UDF(DIFF_TIME_PERIOD_UDF('SECONDS','2022-11-26 10:15:20.000*2022-11-26 10:15:25.000')); ``` @@ -1801,7 +1801,5 @@ ### Parameters -`MINUEND` A timestamp value that will be subtracted from--Time to be subtracted from the original value.+`MINUEND` The time value from which `SUBTRAHEND` will be subtracted.  `SUBTRAHEND` The timestamp value to be subtracted from another timestamp@@ -1900,9 +1898,9 @@ `INPUT` TIMESTAMP_TZ -A date value that will be used to determine the corresponding day of the week.--### Returns--A whole number from 1 to 33 (inclusive).+A date value that will be used to determine the corresponding day of the month.++### Returns++A whole number from 1 to 31 (inclusive).  ### Example@@ -1927,5 +1925,5 @@ ### Definition -UDF (User-Defined Function) that processes December 31st and returns the corresponding ISO year. This function is used as a component of the PUBLIC.YEAR_END_IDO_UDF calculation.+UDF (User-Defined Function) that processes December 31st and returns the corresponding ISO year. This function is used as a component of the PUBLIC.YEAR_END_ISO_UDF calculation.  ```sql@@ -1970,5 +1968,5 @@ ```sql :force:-PUBLIC.DATE_ADD_UDF(FIRST_DATE DATE, SECOND_DATE DATE)+PUBLIC.DATEADD_UDF(FIRST_DATE DATE, SECOND_DATE DATE) ``` @@ -1982,6 +1980,4 @@  Add the second date value together with first_date.--###  ### Returns@@ -2133,5 +2129,5 @@ ### Parameters -`MINUEND` A timestamp value that will be subtracted from represents the timestamp value that will be subtracted from+`MINUEND` The timestamp value from which `SUBTRAHEND` will be subtracted.  The date being used as the starting point for subtraction.@@ -2471,5 +2467,5 @@ `OCCURRENCE` DOUBLE - A numeric data type that represents the number of times an event occurs, stored as a double-precision floating-point number. -The position in the text where the search will begin (starting from position 1).+The occurrence number to search for (for example, 2 finds the second match).  ### Returns@@ -2602,5 +2598,5 @@ ### Parameters -`SEARCHNAME` VARCHAR - A variable of type VARCHAR used to store search terms or names. - A variable of type VARCHAR used to store search terms or names.+`SEARCHNAME` VARCHAR - A variable of type VARCHAR used to store search terms or names.  The name to search for within the key-value pairs.@@ -2671,6 +2667,6 @@ ```sql :force:-SELECT PUBLIC.WEEK_OF_YEAR_UDF(DATE '2024-05-10'),-PUBLIC.WEEK_OF_YEAR_UDF(DATE '2020-01-03')+SELECT PUBLIC.TD_WEEK_OF_YEAR_UDF(DATE '2024-05-10'),+PUBLIC.TD_WEEK_OF_YEAR_UDF(DATE '2020-01-03') ``` @@ -3032,5 +3028,5 @@ ### Definition -Identify the month from a given date.+Identify the week number of the month from a given date.  ```sql@@ -3043,9 +3039,9 @@ `INPUT` TIMESTAMP_TZ -The date from which to calculate the month number.--### Returns--A numeric value representing the month (1-12) of a given date.+The date from which to calculate the week of the month.++### Returns++A numeric value representing the week of the month (1-4) for the given date.  ### Usage example 

--- ahttps://docs.snowflake.com/en/developer-guide/logging-tracing/event-table-columns+++ bhttps://docs.snowflake.com/en/developer-guide/logging-tracing/event-table-columns@@ -176,12 +176,12 @@ <div className="colwidths-auto"> -| Attribute                                                               | Description                                                                                                    |-| ----------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |-| [TIMESTAMP](#label-event-table-observed-timestamp-column)               | The timestamp when the event was created.                                                                      |-| [RESOURCE_ATTRIBUTES](#label-event-table-resource-attributes-column)    | Attributes that identify the Iceberg Auto Refresh event, such as database, schema, table, and catalog names.   |-| [RECORD_TYPE](#label-event-table-record-type-column)                    | The event type `EVENT`.                                                                                        |-| [RECORD](#label-event-table-record-column)                              | Detailed information about the status of the operation associated with the event, including name and severity. |-| [RECORD_ATTRIBUTES](#label-event-table-record-attributes-event-iceberg) | Attributes associated with the event.                                                                          |-| [VALUE](#label-event-table-value-column)                                | Additional information specific to the event.                                                                  |+| Attribute                                                               | Description                                                                                                       |+| ----------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |+| [TIMESTAMP](#label-event-table-timestamp-column)                        | The timestamp when the event was created.                                                                         |+| [RESOURCE_ATTRIBUTES](#label-event-table-resource-attributes-column)    | Attributes that identify the Iceberg automated refresh event, such as database, schema, table, and catalog names. |+| [RECORD_TYPE](#label-event-table-record-type-column)                    | The event type `EVENT`.                                                                                           |+| [RECORD](#label-event-table-record-column)                              | Detailed information about the status of the operation associated with the event, including name and severity.    |+| [RECORD_ATTRIBUTES](#label-event-table-record-attributes-event-iceberg) | Attributes associated with the event.                                                                             |+| [VALUE](#label-event-table-value-column)                                | Additional information specific to the event.                                                                     |  </div>@@ -203,5 +203,5 @@ ## RECORD column -Provides core information about the event, include the log level for a log event, or the name for trace event (span or span event record).+Provides core information about the event, including the log level for a log event, or the name for a trace event (span or span event record).  Attributes, if any, for the record are recorded in the [RECORD_ATTRIBUTES column](#label-event-table-record-attributes-column).@@ -534,8 +534,8 @@ | Attribute              | Type    | Description                                                                                                                            | | ---------------------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------- |-| `code.filepath`        | int     | The file containing code that generated the message.                                                                                   |+| `code.filepath`        | string  | The file containing code that generated the message.                                                                                   | | `code.function`        | string  | The name of the function that generated the message.                                                                                   | | `code.lineno`          | int     | The line number in code that generated the message.                                                                                    |-| `code.namespace`       | int     | The namespace of code that generated the messages.                                                                                     |+| `code.namespace`       | string  | The namespace of code that generated the message.                                                                                      | | `exception.message`    | string  | The error message from an [unhandled exception](/developer-guide/logging-tracing/unhandled-exception-messages).                        | | `exception.type`       | string  | The name of the class for an [unhandled exception](/developer-guide/logging-tracing/unhandled-exception-messages).                     |@@ -684,5 +684,5 @@       <td> -The row represents a span event. The may be multiple span event records attached to a particular span. Your handler code may create+The row represents a span event. There may be multiple span event records attached to a particular span. Your handler code may create events to fit your needs. The number of span events is limited to 128. @@ -765,5 +765,5 @@       <td>`snow.executable.id`</td>       <td>int</td>-      <td>The internal/system-generated identifier of the executable (procedure, function, SnowService, etc.) generating the event.</td>+      <td>The internal/system-generated identifier of the executable (procedure, function, SnowService, and so on) generating the event.</td>       <td>`12345`</td>     </tr>@@ -773,20 +773,4 @@       <td>The name of the executable generating the event. For example, this might be the name of the procedure, function, or Streamlit app.</td>       <td>`MY_UDF`</td>-    </tr>-    <tr>-      <td>`snow.executable.runtime.version`</td>-      <td>string</td>-      <td>--The executable language's runtime version. This will be a value specific to the language, as described below:--- Java: `11` or `17`-- JavaScript: No value-- Python: From `3.10` to `3.12`-- Scala: `2.12`-- SQL: No value--</td>-      <td>`procedure`</td>     </tr>     <tr>@@ -810,4 +794,20 @@     </tr>     <tr>+      <td>`snow.executable.runtime.version`</td>+      <td>string</td>+      <td>++The executable language's runtime version. This will be a value specific to the language, as described below:++- Java: `11` or `17`+- JavaScript: No value+- Python: From `3.10` to `3.12`+- Scala: `2.12`+- SQL: No value++</td>+      <td>`3.11`</td>+    </tr>+    <tr>       <td>`snow.owner.id`</td>       <td>int</td>@@ -859,5 +859,5 @@ | `db.user`                        | string | For a function or procedure, the name of the user executing the function or procedure. For a Streamlit app, the name of the user who was viewing the app for a given event. | `MY_USER_NAME`                         | | `snow.query.id`                  | string | The ID of the query.                                                                                                                                                        | `01a6aeb7-0604-c466-0000-097127d13812` |-| `snow.release.version`           | string | The Snowflake release running when event was generated          ... (truncated) 

差分が長いため、途中まで表示しています。

--- ahttps://docs.snowflake.com/en/user-guide/collaboration/listings/pricing-plans-offers/providers-create-manage-offers+++ bhttps://docs.snowflake.com/en/user-guide/collaboration/listings/pricing-plans-offers/providers-create-manage-offers@@ -40,5 +40,5 @@ ## Working with offers -The **Offers** tab shows a list of both standard and private offers that are available for a listing. The table includes the following information about each offer:+The **Offers** tab shows a list of both standard and private offers that are available for a listing.  The following details are available for Standard offers:@@ -60,5 +60,5 @@ - Expiration date - Target consumer-- Pricing plan Terms+- Pricing plan terms - Last updated date @@ -109,5 +109,6 @@    1. Select **Standard offer**.    2. Select the **Purchase type**:-      - Select **Self-serve** to allow consumers to see the price and purchase the listing directly+      - Select **Self-serve** to allow consumers to see the price and purchase the listing directly.+       - Select **Sales-led** to require consumers to contact you to purchase the listing. @@ -212,6 +213,6 @@       4. Select **Next**. -   2. On the **Billings and payments** page, select an existing pricing plan` and enter the following information.-      1. Review the negotiated price details in the **Plan components** table.+      5. On the **Billing and payments** page, select an existing pricing plan and enter the following information.+      6. Review the negotiated price details in the **Plan components** table.           Optional: Hover on a row in the **Plan components** table and select the **Edit** icon to modify the component details.@@ -220,6 +221,6 @@          - For flat-fee plans, you can edit the access fee price or apply a discount percentage. -      2. Specify the contract type:-         - **Limited-time**: This grants access for a fixed period of time, such as 30 days. Consumers can be charged upfront or in installments+      7. Specify the contract type:+         - **Limited-time**: This grants access for a fixed period of time, such as 30 days. Consumers can be charged upfront or in installments.          - **Recurring (Subscription)**: This grants continuous access. Consumers are billed at the chosen frequency for the contract duration, and the subscription auto-renews until the consumer [cancels](#label-pricing-plans-offers-consumer-cancel-purchase) the purchase. @@ -253,10 +254,10 @@       </blockquote> -   3. On the **Access and terms** page, specify the access start date and the terms of service for the offer.+   2. On the **Access and terms** page, specify the access start date and the terms of service for the offer.        The access start date is the date when the consumer can start using the product. You can set this to **When offer accepted** to allow the consumer to start using the product immediately after accepting the offer, or you can configure a specific start date. -   4. Select **Next**.-   5. On the **Summary** page, review the offer details, and then select **Done**.+   3. Select **Next**.+   4. On the **Summary** page, review the offer details, and then select **Done**.  Upon completion, the offer appears on the **Private offers** tab. The initial status will show **Active**, indicating that the offer is ready to be accepted by the consumer. The consumer can either accept or reject the offer, and the status will be updated accordingly.@@ -353,12 +354,13 @@       4. Select **Next**. -   2. On the **Billings and payments** page, select **Apple one-time pricing** and enter the following information.-      1. Specify the total contract value.-      2. Specify the contract type:-         - **Limited-time**: This grants access for a fixed period of time, such as 30 days. Consumers can be charged upfront or in installments+      5. On the **Billing and payments** page, select **Apply one-time pricing** and enter the following information.+      6. Specify the total contract value.+      7. Specify the contract type:+         - **Limited-time**: This grants access for a fixed period of time, such as 30 days. Consumers can be charged upfront or in installments.+          - **Recurring (Subscription)**: This grants continuous access. Consumers are billed at the chosen frequency for the contract duration, and the subscription auto-renews until the consumer [cancels](#label-pricing-plans-offers-consumer-cancel-purchase) the purchase. -      3. Enter a contract duration to indicate the length of time that the offer is valid for.-      4. Specify payment options for the offer:+      8. Enter a contract duration to indicate the length of time that the offer is valid for.+      9. Specify payment options for the offer:          - **Require full payment upfront**: The consumer pays the total contract value (TCV) at the start of the contract.          - **Accept installments**: Allow the consumer to pay in equal monthly installments or specify custom installment amounts.@@ -366,17 +368,17 @@            If you select the **Accept installments** option, you can specify the number of installments and the installment amount. -      5. Specify the first invoice date.--         The first invoice date is the date when the consumer will be billed for the first time.--      6. Select whether to require a credit card to be on file.-      7. Select **Next**.--   3. On the **Access and terms** page, specify the access start date and the terms of service for the offer.+      10. Specify the first invoice date.++      The first invoice date is the date when the consumer will be billed for the first time.++      11. Select whether to require a credit card to be on file.+      12. Select **Next**.++   2. On the **Access and terms** page, specify the access start date and the terms of service for the offer.        The access start date is the date when the consumer can start using the product. You can set this to **When offer accepted** to allow the consumer to start using the product immediately after accepting the offer, or you can configure a specific start date. -   4. Select **Next**.-   5. On the **Summary** page, review the offer details, and then select **Done**.+   3. Select **Next**.+   4. On the **Summary** page, review the offer details, and then select **Done**.  **SQL:**@@ -481,5 +483,5 @@ ## Edit a private offer -The steps below describe how to edit a private offers. Only private offers that have the following status can be edited:+The steps below describe how to edit a private offer. Only private offers that have the following status can be edited:  - DRAFT@@ -566,4 +568,4 @@ 4. Select a paid listing in the list. 5. Click the **Private Offers** tab.-6. Click the %vertical-ellipsis% button for private offer you want to withdraw and then select **Withdraw**.+6. Click the %vertical-ellipsis% button for the private offer you want to withdraw and then select **Withdraw**. 7. Click **Withdraw offer**. 

--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-cli+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-cli@@ -207,9 +207,17 @@     </tr>     <tr>-      <td>Claude Opus 4.8 (Preview)</td>+      <td>Claude Opus 5</td>+      <td>`claude-opus-5`</td>+    </tr>+    <tr>+      <td>Claude Sonnet 5</td>+      <td>`claude-sonnet-5`</td>+    </tr>+    <tr>+      <td>Claude Opus 4.8</td>       <td>`claude-opus-4-8`</td>     </tr>     <tr>-      <td>Claude Opus 4.7 (Preview)</td>+      <td>Claude Opus 4.7</td>       <td>`claude-opus-4-7`</td>     </tr>@@ -235,5 +243,5 @@     </tr>     <tr>-      <td>OpenAI GPT 5.5</td>+      <td>OpenAI GPT 5.5 (Preview)</td>       <td>`openai-gpt-5.5`</td>     </tr>@@ -290,14 +298,32 @@   <tbody>     <tr>-      <td>`claude-opus-4-8` (Preview)</td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td>%cm%</td>-      <td></td>-      <td></td>-      <td></td>-    </tr>-    <tr>-      <td>`claude-opus-4-7` (Preview)</td>+      <td>`claude-opus-5`</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+    </tr>+    <tr>+      <td>`claude-sonnet-5`</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+    </tr>+    <tr>+      <td>`claude-opus-4-8`</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+    </tr>+    <tr>+      <td>`claude-opus-4-7`</td>       <td>%cm%</td>       <td>%cm%</td>@@ -353,5 +379,5 @@     </tr>     <tr>-      <td>`openai-gpt-5.5`</td>+      <td>`openai-gpt-5.5` (Preview)</td>       <td>%cm%</td>       <td></td>@@ -394,5 +420,5 @@ following settings based on your needs: -- **AWS_US**: Recommended for the best experience with **Claude Opus 4.x** models.+- **AWS_US**: Recommended for the best experience with **Claude Opus** models. - **AWS_EU**: Access Claude models from the EU. - **AWS_APJ**: Access Claude models from APJ (may be limited to Claude Sonnet 4.0). 

--- ahttps://docs.snowflake.com/en/migrations/sma-docs/issue-analysis/issue-codes-by-source/python/README+++ bhttps://docs.snowflake.com/en/migrations/sma-docs/issue-analysis/issue-codes-by-source/python/README@@ -64,5 +64,5 @@ ## SPRKPY1002 -Message**:** < element > is not supported,Spark element is not supported.+Message**:** < element > is not supported. Spark element is not supported.  Category**:** Conversion error.@@ -75,5 +75,5 @@  - Even though the option or the element on the message is not supported, this does not mean that a solution cannot be found. It only means that the tool itself cannot find the solution.-- If you have encountered an unsupported element from a pyspark.ml library, consider some alternative approaches. There are additional guides available to walkthrough issues related to ml such as this one from Snowflake.+- If you have encountered an unsupported element from a pyspark.ml library, consider some alternative approaches. There are additional guides available to walk through issues related to ML such as this one from [Snowflake](https://docs.snowflake.com/en/developer-guide/snowpark/python/snowpark-python-ml). - Check if the source code has the correct syntax. (You can use the issues.csv file to determine where the conversion error(s) are occurring.) If the syntax is correct, report that you encountered a conversion error on a particular element using the Report an Issue option in the SMA. Include the line of code that was causing the error in the description when you file this issue. - For more support, you can email us at [sma-support@snowflake.com](mailto:sma-support@snowflake.com) or post an issue [in the SMA](/migrations/sma-docs/user-guide/project-overview/configuration-and-settings).@@ -171,5 +171,5 @@ **Input** -In this example there are two context to create a connections to an Spark Cluster+In this example there are two contexts to create connections to a Spark Cluster  ```python@@ -182,5 +182,5 @@ **Output** -Because there are no clusters on Snowflake the Context is not required, note that the variables my_sc1 and my_sc2 that contains Spark properties may be not required or it will to be adapted to fix the code.+Because there are no clusters on Snowflake the Context is not required, note that the variables my_sc1 and my_sc2 that contain Spark properties might not be required or will need to be adapted to fix the code.  ```python@@ -258,5 +258,5 @@ **Input** -In this example an example to create a connection to an Hive store.+In this example, there is an example showing how to create a connection to a Hive store.  ```python@@ -269,5 +269,5 @@ **Output** -In Snowflake there are not Hive stores, so the Hive Context is not required, You can still use parquet files on Snowflake please check this [tutorial](https://docs.snowflake.com/en/user-guide/tutorials/script-data-load-transform-parquet) to learn how.+In Snowflake there are no Hive stores, so the Hive Context is not required. You can still use parquet files on Snowflake please check this [tutorial](https://docs.snowflake.com/en/user-guide/tutorials/script-data-load-transform-parquet) to learn how.  ```python@@ -278,9 +278,9 @@ ``` -the sc variable refers to a [Snow Park Session Object](https://docs.snowflake.com/en/developer-guide/snowpark/reference/python/1.23.0/snowpark/api/snowflake.snowpark.Session)--**Recommended fix**--For the output code in the example you should add the [Snow Park Session Object](https://docs.snowflake.com/en/developer-guide/snowpark/reference/python/1.23.0/snowpark/api/snowflake.snowpark.Session) similar to this code:+the sc variable refers to a [Snowpark Session Object](https://docs.snowflake.com/en/developer-guide/snowpark/reference/python/1.23.0/snowpark/api/snowflake.snowpark.Session)++**Recommended fix**++For the output code in the example you should add the [Snowpark Session Object](https://docs.snowflake.com/en/developer-guide/snowpark/reference/python/1.23.0/snowpark/api/snowflake.snowpark.Session) similar to this code:  ```python@@ -315,5 +315,5 @@ **Input** -It's important understand that Pyspark uses two different approxQuantile functions, here we use the [DataFrame approxQuantile](https://spark.apache.org/docs/latest/api/python/reference/pyspark.sql/api/pyspark.sql.DataFrame.approxQuantile.html) version+It's important to understand that Pyspark uses two different approxQuantile functions, here we use the [DataFrame approxQuantile](https://spark.apache.org/docs/latest/api/python/reference/pyspark.sql/api/pyspark.sql.DataFrame.approxQuantile.html) version  ```python@@ -406,5 +406,5 @@ **Output** -SMA returns the EWI SPRKPY1010 over the line where approxQuantile is used, so you can use to identify where to fix. Note that also marks the [setCheckpointDir](https://spark.apache.org/docs/latest/api/python/reference/api/pyspark.SparkContext.setCheckpointDir.html) as unsupported, but a checpointed directory is not required for the fix.+SMA returns the EWI SPRKPY1010 over the line where checkpoint is used, so you can use it to identify where to fix. Note that also marks the [setCheckpointDir](https://spark.apache.org/docs/latest/api/python/reference/api/pyspark.SparkContext.setCheckpointDir.html) as unsupported, but a checkpointed directory is not required for the fix.  ```python@@ -484,5 +484,5 @@ **Input** -It's important understand that Pyspark uses two different approxQuantile functions, here we use the [DataFrameStatFunctions approxQuantile](https://spark.apache.org/docs/latest/api/python/reference/pyspark.sql/api/pyspark.sql.DataFrameStatFunctions.approxQuantile.html#pyspark.sql.DataFrameStatFunctions.approxQuantile) version.+It's important to understand that Pyspark uses two different approxQuantile functions, here we use the [DataFrameStatFunctions approxQuantile](https://spark.apache.org/docs/latest/api/python/reference/pyspark.sql/api/pyspark.sql.DataFrameStatFunctions.approxQuantile.html#pyspark.sql.DataFrameStatFunctions.approxQuantile) version.  ```python@@ -553,5 +553,5 @@ **Input** -For this example the dataframe df is writed to a Spark table "table".+For this example the dataframe df is written to a Spark table "table".  ```python@@ -570,5 +570,5 @@ **Recommended fix** -Use df.write.SaveAsTable() instead.+Use df.write.save_as_table() instead.  ```python@@ -1118,10 +1118,4 @@  - For more support, you can email us at [sma-support@snowflake.com](mailto:sma-support@snowflake.com) or post an issue [in the SMA](/migrations/sma-docs/user-guide/project-overview/configuration-and-settings).-------description: >--The `mode` parameter in the methods of CSV, JSON and PARQUET is transformed to-`overwrite`  ---@@ -3127,5 +3121,4 @@ ## Output Code from snowflake.snowpark import Session-from snowflake.snowpark import Session  def example1():@@ -3268,5 +3261,5 @@ **Output** -Since the tool can not determine the value of the variable in runtime, shows the EWI `SPRKPY1054` indicating that the value "" is not supported.+Since the tool can't determine the value of the variable in runtime, shows the EWI `SPRKPY1054` indicating that the value "" is not supported.  ```python@@ -3777,5 +3770,5 @@ ```python #EWI: SPRKPY1062 => pyspark.sql.group.GroupedData.pivot without parameter 'values' is not supported. See documentation for more info.-df.groupBy("date").pivot("category", [v[0] for v in df.select("category").distinct().limit(10000).collect()]]).sum("amount")+df.groupBy("date").pivot("category", [v[0] for v in df.select("category").distinct().limit(10000).collect()]).sum("amount") ``` @@ -3867,5 +3860,5 @@  ```python-#EWI: SPRKPY1062 => pyspark.sql.pandas.functions.pandas_udf has a workaround, see documentation for more info+#EWI: SPRKPY1063 => pyspark.sql.pandas.functions.pandas_udf has a workaround, see documentation for more info @pandas_udf(schema, PandasUDFType.GROUPED_MAP) @@ -4211,5 +4204,5... (truncated) 

差分が長いため、途中まで表示しています。

--- ahttps://docs.snowflake.com/en/developer-guide/native-apps/update-app-upgrade+++ bhttps://docs.snowflake.com/en/developer-guide/native-apps/update-app-upgrade@@ -91,9 +91,9 @@    ``` -This command sets the upgrade date and time to April 6, 2025 at 11:00am.+This command sets the upgrade date and time to April 6, 2025 at 11:00 am.  ### Change the upgrade date and time for a custom release directive -1. To change the upgrade date and time for a default release directive:+1. To change the upgrade date and time for a custom release directive:    ```sql    ALTER APPLICATION PACKAGE hello_snowflake_package@@ -105,5 +105,5 @@    ``` -This command sets the upgrade date and time to April 6, 2025 at 11:00am.+This command sets the upgrade date and time to April 6, 2025 at 11:00 am.  ## Start an upgrade@@ -144,5 +144,5 @@  The consumer performs a manual upgrade by running the [](/sql-reference/sql/alter-application).-This command initiate the upgrade of an installed version or patch of an app using the release directive+This command initiates the upgrade of an installed version or patch of an app using the release directive specified in the application package. @@ -167,5 +167,5 @@ If a provider publishes a %native-app% using [Cross-Cloud Auto-Fulfillment](/collaboration/provider-listings-auto-fulfillment),-automated upgrades may take a while to upgrade depending on multiple factors, including:+automated upgrades may take some time depending on multiple factors, including:  - The value of the refresh schedule.@@ -200,12 +200,12 @@ <div className="colwidths-auto"> -|   | Stage                          | Description                                                                                                                                                                                                                                                       |-| - | ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |-| 1 | App is disabled?               | If the app is disabled, no upgrade is possible.                                                                                                                                                                                                                   |-| 2 | Set release directive to v2.0  | The provider sets the release directive to v2.0.                                                                                                                                                                                                                  |-| 3 | Eligible to upgrade            | Snowflake performs checks to verify that the app is eligible to upgrade. These checks include verifying that the app is not disabled, that application package is available, that the version and patch is valid for upgrade, the consumer account is valid, etc. |-| 4 | Obtain upgrade slot?           | Depending on the number of apps being upgraded, the number of consumer accounts, etc. they may have to wait to begin the upgrade process.                                                                                                                         |-| 5 | Setup script run successfully? | When the upgrade begins, Snowflake runs setup script. If any uncaught errors occur, the setup script execution stops. Snowflake queues the app for upgrade again based on the number of retries configured.                                                       |-| 6 | Is version updated?            | Snowflake checks to see if the upgrade is for a version or patch. If the upgrade is for a version, Snowflake performs additional checks and waits until all jobs from the older version of the app have completed.                                                |+|   | Stage                          | Description                                                                                                                                                                                                                                                                  |+| - | ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |+| 1 | App is disabled?               | If the app is disabled, no upgrade is possible.                                                                                                                                                                                                                              |+| 2 | Set release directive to v2.0  | The provider sets the release directive to v2.0.                                                                                                                                                                                                                             |+| 3 | Eligible to upgrade            | Snowflake performs checks to verify that the app is eligible to upgrade. These checks include verifying that the app is not disabled, that the application package is available, that the version and patch are valid for upgrade, the consumer account is valid, and so on. |+| 4 | Obtain upgrade slot?           | Depending on the number of apps being upgraded, the number of consumer accounts, and so on, they may have to wait to begin the upgrade process.                                                                                                                              |+| 5 | Setup script run successfully? | When the upgrade begins, Snowflake runs the setup script. If any uncaught errors occur, the setup script execution stops. Snowflake queues the app for upgrade again based on the number of retries configured.                                                              |+| 6 | Is version updated?            | Snowflake checks to see if the upgrade is for a version or patch. If the upgrade is for a version, Snowflake performs additional checks and waits until all jobs from the older version of the app have completed.                                                           |  </div>@@ -227,12 +227,12 @@ <div className="colwidths-auto"> -| State        | Description                                                                                                                                                                                                                 |-| ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |-| DISABLED     | The app is disabled and not eligible for upgrade.                                                                                                                                                                           |-| QUEUED       | The app is in the queue to be upgraded based on the number of apps and consumer accounts.                                                                                                                                   |-| UPGRADING    | The app is in the process of being upgraded.                                                                                                                                                                                |-| COMPLETED    | The app has upgraded successfully.                                                                                                                                                                              ... (truncated) 

差分が長いため、途中まで表示しています。

--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/dataverse/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/dataverse/about@@ -25,4 +25,53 @@  - Integrate data from Microsoft Power Platform and Dynamics 365 applications with Snowflake for holistic business insights++<a id="label-dataverse-connector-managed-columns"></a>++## Connector-managed columns++In addition to the columns replicated from the Dataverse table, every destination table has+the following connector-managed columns:++<div className="colwidths-given">++  <colgroup>+    <col style={{width: "30.0%"}} />+    <col style={{width: "20.0%"}} />+    <col style={{width: "50.0%"}} />+  </colgroup>+  <thead>+    <tr>+      <th>Column</th>+      <th>Type</th>+      <th>Purpose</th>+    </tr>+  </thead>+  <tbody>+    <tr>+      <td>`_SNOWFLAKE_ID`</td>+      <td>`VARCHAR`</td>+      <td>The identifier of the record in Dataverse, taken from the primary key of the source table.</td>+    </tr>+    <tr>+      <td>`_SNOWFLAKE_UPDATED_AT`</td>+      <td>`VARCHAR`</td>+      <td>The time at which the connector last replicated the row, in ISO 8601 format, for example `2026-08-11T15:04:05.123Z`.</td>+    </tr>+    <tr>+      <td>`_SNOWFLAKE_DELETED`</td>+      <td>`BOOLEAN`</td>+      <td>Whether the record was deleted at the source.</td>+    </tr>+  </tbody>++</div>++Deletes are replicated as soft deletes: when a record is deleted in Dataverse, the connector+keeps the row in the destination table and sets `_SNOWFLAKE_DELETED` to `TRUE`. To query only+the records that currently exist in Dataverse, filter on `_SNOWFLAKE_DELETED = FALSE`.++If you enable the `Include Formatted Values` parameter, each destination table also has a+`_DATAVERSE_FORMATTED_VALUES` column of type `OBJECT`. For more information, see+[](/user-guide/data-integration/openflow/connectors/dataverse/setup#label-include-formatted-values).  ## Rate limiting restrictions 

--- ahttps://docs.snowflake.com/en/user-guide/personal-databases+++ bhttps://docs.snowflake.com/en/user-guide/personal-databases@@ -22,5 +22,5 @@ - **Organize personal projects:** Users can organize their own projects in an isolated environment, reducing clutter and potential naming   conflicts in shared databases.-- **Easy administrator governance:** All file-related developments are fully governed by RBAC.+- **Governance:** All Personal Database objects are fully governed by RBAC.  <a id="label-personal-databases-pdb-object-types"></a>@@ -55,5 +55,5 @@   already possesses. This mirrors the execution environment of a standard Snowflake workspace file. -Personal databases also support personal secrets. [Secret objects](/sql-reference/sql/create-secret) are owned exclusively by the user. This ensures, by default, that the secret+Personal Databases also support personal secrets. [Secret objects](/sql-reference/sql/create-secret) are owned exclusively by the user. This ensures, by default, that the secret remains private, is accessible only to the user, and is not shared unintentionally. @@ -71,27 +71,27 @@  - CREATE and OWNERSHIP privileges can't be granted to account roles on PDB objects.-- Privileges on APPLICATION SERVICE objects in a personal database can't be granted to account roles. To share an Application Service with other roles, deploy it to a standard database instead. For details, see [Deploy to a standard database when sharing with other roles](/developer-guide/snowflake-app-runtime/access-control).+- Privileges on APPLICATION SERVICE objects in a Personal Database can't be granted to account roles. To share an Application Service with other roles, deploy it to a standard database instead. For details, see [Deploy to a standard database when sharing with other roles](/developer-guide/snowflake-app-runtime/access-control).  <a id="label-personal-databases-feature-policies"></a> -## Use feature policies with personal databases+## Use feature policies with Personal Databases  Account administrators can use feature policies to control which object types users are allowed-to create in their personal databases. This lets organizations enforce governance rules across-all personal databases in the account.+to create in their Personal Databases. This lets organizations enforce governance rules across+all Personal Databases in the account. -A feature policy can block the creation of any [object type supported in personal databases](#label-personal-databases-pdb-object-types).+A feature policy can block the creation of any [object type supported in Personal Databases](#label-personal-databases-pdb-object-types).  Account-level object types such as WAREHOUSES, COMPUTE POOLS, and DATABASES have no effect-when a feature policy is bound to personal databases. Those types only apply when a feature+when a feature policy is bound to Personal Databases. Those types only apply when a feature policy is bound to native apps. -Feature policies only prevent the creation of new objects. Existing objects are not affected-and will continue to exist. To enforce a policy on objects that already exist, remove them+Feature policies only prevent the creation of new objects. Existing objects are not affected.+To enforce a policy on objects that already exist, remove them manually before or after applying the policy. -### Applying a feature policy to personal databases+### Applying a feature policy to Personal Databases -To create and apply a feature policy to all personal databases in the account, use the+To create and apply a feature policy to all Personal Databases in the account, use the [CREATE FEATURE POLICY](/sql-reference/sql/create-feature-policy) and [ALTER ACCOUNT](/sql-reference/sql/alter-account) commands:@@ -108,7 +108,7 @@ ``` -After applying this policy, users can no longer create application services in their personal databases.+After applying this policy, users can no longer create application services in their Personal Databases. -To remove the policy from all personal databases:+To remove the policy from all Personal Databases:  ```sql@@ -137,8 +137,8 @@  Roles with the MANAGE GRANTS privilege have visibility into all objects within the account, including personal objects owned by individual-users. For example, roles like ACCOUNTADMIN can view all databases, including personal databases, by default. These roles can also access-details about schemas and their objects within personal databases.+users. For example, roles like ACCOUNTADMIN can view all databases, including Personal Databases, by default. These roles can also access+details about schemas and their objects within Personal Databases. -- To view details for all personal databases within an account, query the [DATABASES Account Usage view](/sql-reference/account-usage/databases):+- To view details for all Personal Databases within an account, query the [DATABASES Account Usage view](/sql-reference/account-usage/databases):   ```sql   SELECT * FROM SNOWFLAKE.ACCOUNT_USAGE.DATABASES@@ -146,17 +146,17 @@   ``` -- To view the workspaces that exist in a specific personal database, use the following code:+- To view the workspaces that exist in a specific Personal Database, use the following code:   ```sql   SHOW WORKSPACES IN DATABASE "USER$CMEYER";   ``` -- To view a specific user's personal database, use the following code:+- To view a specific user's Personal Database, use the following code:   ```sql   SHOW DATABASES LIKE 'USER$BOBR';   ``` -  For personal databases, the value in the `kind` column is `PERSONAL DATABASE`.+  For Personal Databases, the value in the `kind` column is `PERSONAL DATABASE`. -- To view objects in a specific personal database, use the following code:+- To view objects in a specific Personal Database, use the following code:   ```sqlsyntax   SHOW OBJECTS IN DATABASE "USER$<username>";@@ -167,5 +167,5 @@ ### Drop a workspace -- To drop a workspace in a personal database, use the following code:+- To drop a workspace in a Personal Database, use the following code:   ```sql   DROP WORKSPACE "USER$JSMITH_DROP_WS_TEST".PUBLIC."drop_this_ws";@@ -176,5 +176,5 @@ ## Cost considerations -- Users cannot store data in tables in their PDBs.+- Users can't store data in tables in their PDBs. - Storage costs reflect only the size of the workspace files and associated metadata. @@ -183,5 +183,5 @@ ## Limitations -Administrators cannot perform the following tasks:+Administrators can't perform the following tasks:  - View filenames or file contents that belong to other users. 

--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-coding-agent+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-coding-agent@@ -7,12 +7,12 @@ - [](/user-guide/snowflake-cortex/cortex-agents-code-execution-tool) -A Coding Agent is a managed agent that brings Snowflake CoCo's coding capabilities into your own applications through the Cortex Agents REST API. You add the `code_toolset_all` tool type to a Cortex Agent, and Snowflake provisions and manages a sandbox backed by the same runtime that powers CoCo — bash, file read/write/edit, grep, glob, web search, SQL execution, and skills — executes the tools, and streams results back to your application, so you don't build or host an agent loop yourself. Any query that requires code generation, SQL execution, data transformation, or pipeline automation is handled inside the sandboxed runtime.+A Coding Agent is a managed agent that brings Snowflake CoCo's coding capabilities into your own applications through the Cortex Agents REST API. You add the `code_toolset_all` tool type to a Cortex Agent, and Snowflake provisions and manages a sandbox backed by the same runtime that powers CoCo (bash, file read/write/edit, grep, glob, web search, SQL execution, and skills), executes the tools, and streams results back to your application, so you don't build or host an agent loop yourself. Any query that requires code generation, SQL execution, data transformation, or pipeline automation is handled inside the sandboxed runtime.  Use `code_toolset_all` when you want an autonomous coding agent with the full suite of development tools. It differs from two related surfaces: -- **`code_execution` tool** — a single Python sandbox tool you add alongside other agent tools (Cortex Analyst, Cortex Search). Use it when your agent's primary function is not code generation. See [Cortex Agent code execution tool](/user-guide/snowflake-cortex/cortex-agents-code-execution-tool).-- **Cortex Code CLI** — the `cortex code` command-line client that runs locally on your machine. A Coding Agent exposes the same toolset as a hosted agent you call over the API instead.--`code_toolset_all` and `code_execution` are **mutually exclusive** — a single request can declare at most one of them. Specifying both returns an error.+- **`code_execution` tool**: a single Python sandbox tool you add alongside other agent tools (Cortex Analyst, Cortex Search). Use it when your agent's primary function is not code generation. See [Cortex Agent code execution tool](/user-guide/snowflake-cortex/cortex-agents-code-execution-tool).+- **Cortex Code CLI**: the `cortex code` command-line client that runs locally on your machine. A Coding Agent exposes the same toolset as a hosted agent you call over the API instead.++`code_toolset_all` and `code_execution` are **mutually exclusive**: a single request can declare at most one of them. Specifying both returns an error.  ## Included tools@@ -49,5 +49,5 @@ ``` -No `tool_resources` entry is required for basic usage — the sandbox is provisioned automatically when this tool type is present. The remaining sections describe optional configuration.+No `tool_resources` entry is required for basic usage: the sandbox is provisioned automatically when this tool type is present. The remaining sections describe optional configuration.  ## Example request@@ -99,5 +99,5 @@ ``` -Skills are declared in the top-level `skills` array (not under `tool_resources`), matching how skills are attached to a persistent agent. Sandbox behavior — permission policy, workspace mounts, and disabled skills — is configured under `tool_resources.code_toolset_all`.+Skills are declared in the top-level `skills` array (not under `tool_resources`), matching how skills are attached to a persistent agent. Sandbox behavior (permission policy, workspace mounts, and disabled skills) is configured under `tool_resources.code_toolset_all`.  ## Sandbox permission policy@@ -160,5 +160,5 @@ | Field        | Description                                                                                    | | ------------ | ---------------------------------------------------------------------------------------------- |-| `name`       | Fully-qualified Snowflake workspace name (e.g., `USER$.PUBLIC.DEFAULT$`). Required.            |+| `name`       | Fully qualified Snowflake workspace name (for example, `USER$.PUBLIC.DEFAULT$`). Required.     | | `type`       | Mount type. Use `workspace` for Snowflake workspaces. Defaults to `workspace` if omitted.      | | `mount_path` | Container filesystem path where the workspace is mounted. Defaults to `/workspace` if omitted. |@@ -185,5 +185,5 @@ The workspace must exist and have a live version before it can be mounted. Workspaces are mounted read-write at version `live` by default. Skills defined in the mounted workspace (under `.snowflake/cortex/skills/`) are automatically attached to the agent session. -The `mount_path` must be a **top-level** absolute path (e.g., `/workspace`, `/project`, `/data`). Nested paths like `/workspace/mydata` are not supported — the sandbox runtime creates a symlink at the specified path but does not create intermediate parent directories. Each workspace requires a unique top-level mount path.+The `mount_path` must be a **top-level** absolute path (for example, `/workspace`, `/project`, `/data`). Nested paths like `/workspace/mydata` are not supported: the sandbox runtime creates a symlink at the specified path but does not create intermediate parent directories. Each workspace requires a unique top-level mount path.  The `name` must be a Snowflake **workspace** object (created with `CREATE WORKSPACE`), not a regular internal stage. Regular stages cannot be mounted as workspaces.@@ -193,9 +193,9 @@ The sandbox exposes skills to the agent from three sources: -- **Bundled skills** — Snowflake-provided skills (such as charting and dashboard skills) are included in every `code_toolset_all` sandbox by default. Use `disabled_skills` to remove ones you don't want.-- **Workspace skills** — skills under `.snowflake/cortex/skills/` in a mounted workspace are attached automatically (see [Attaching a workspace](#attaching-a-workspace)).-- **Stage-based skills** — skills stored in a Snowflake named stage or Git repository, attached through the agent's `skills` list.--Stage-based skills use the same mechanism documented in [Agent skills](/user-guide/snowflake-cortex/cortex-agents-skills): store each skill folder (with its `SKILL.md` and any scripts) in a named stage, then reference it in the top-level `skills` array. When the request also includes `code_toolset_all`, Snowflake mounts each referenced stage skill read-only into the sandbox and the agent can invoke it like any bundled skill — including running the skill's Python scripts, since the sandbox provides the code execution environment those skills require.+- **Bundled skills**: Snowflake-provided skills (such as charting and dashboard skills) are included in every `code_toolset_all` sandbox by default. Use `disabled_skills` to remove ones you don't want.+- **Workspace skills**: skills under `.snowflake/cortex/skills/` in a mounted workspace are attached automatically (see [Attaching a workspace](#attaching-a-workspace)).+- **Stage-based skills**: skills stored in a Snowflake named stage or Git repository, attached through the agent's `skills` list.++Stage-based skills use the same mechanism documented in [Agent skills](/user-guide/snowflake-cortex/cortex-agents-skills): store each skill folder (with its `SKILL.md` and any scripts) in a named stage, then reference it in the top-level `skills` array. When the request also includes `code_toolset_all`, Snowflake mounts each referenced stage skill read-only into the sandbox and the agent can invoke it like any bundled skill, including running the skill's Python scripts, since the sandbox provides the co... (truncated) 

差分が長いため、途中まで表示しています。

--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-python-api/snowflake-python-managing-tasks+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-python-api/snowflake-python-managing-tasks@@ -124,5 +124,5 @@ ## Performing task operations -You can perform common task operations—such as executing, suspending, and resuming tasks—with a `TaskResource` object.+You can perform common task operations (such as executing, suspending, and resuming tasks) with a `TaskResource` object.  Code in the following example executes, suspends, resumes, and drops the `my_task` task:@@ -156,4 +156,5 @@  ```python+from datetime import timedelta from snowflake.core.task import StoredProcedureCall from snowflake.core.task.dagv1 import DAG, DAGTask, DAGOperation@@ -212,27 +213,24 @@   return "task3" -try:-  with DAG(-    "my_dag",-    schedule=Cron("10 * * * *", "America/Los_Angeles"),-    stage_location="@mystage",-    packages=["snowflake-snowpark-python"],-    use_func_return_value=True,-  ) as dag:-    task1 = DAGTask(-      "task1",-      task_handler,-      warehouse=test_warehouse,-    )-    task1_branch = DAGTaskBranch("task1_branch", task_branch_handler, warehouse=test_warehouse)-    task2 = DAGTask("task2", task_handler, warehouse=test_warehouse)-    task3 = DAGTask("task3", task_handler, warehouse=test_warehouse, condition="1=1")-    task1 >> task1_branch-    task1_branch >> [task2, task3]-  schema = root.databases["my_db"].schemas["my_schema"]-  op = DAGOperation(schema)-  op.deploy(dag, mode=CreateMode.or_replace)-finally:-  session.close()+with DAG(+  "my_dag",+  schedule=Cron("10 * * * *", "America/Los_Angeles"),+  stage_location="@mystage",+  packages=["snowflake-snowpark-python"],+  use_func_return_value=True,+) as dag:+  task1 = DAGTask(+    "task1",+    task_handler,+    warehouse="test_warehouse",+  )+  task1_branch = DAGTaskBranch("task1_branch", task_branch_handler, warehouse="test_warehouse")+  task2 = DAGTask("task2", task_handler, warehouse="test_warehouse")+  task3 = DAGTask("task3", task_handler, warehouse="test_warehouse", condition="1=1")+  task1 >> task1_branch+  task1_branch >> [task2, task3]+schema = root.databases["my_db"].schemas["my_schema"]+op = DAGOperation(schema)+op.deploy(dag, mode=CreateMode.or_replace) ```  

--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/native-apps/bundle-app+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/native-apps/bundle-app@@ -20,23 +20,23 @@    entities:      codegen_nativeapp_pkg:-    type: application package-    manifest: root_files/_manifest.yml-    artifacts:-      - src: root_files/README.md-        dest: README.md-      - src: root_files/_manifest.yml-        dest: manifest.yml-      - src: root_files/setup_scripts/*-        dest: setup_scripts/-      - src: python/user_gen/echo.py-        dest: user_gen/echo.py-      - src: python/cli_gen/*-        dest: cli_gen/-        processors:-          - snowpark+       type: application package+       manifest: root_files/_manifest.yml+       artifacts:+         - src: root_files/README.md+           dest: README.md+         - src: root_files/_manifest.yml+           dest: manifest.yml+         - src: root_files/setup_scripts/*+           dest: setup_scripts/+         - src: python/user_gen/echo.py+           dest: user_gen/echo.py+         - src: python/cli_gen/*+           dest: cli_gen/+           processors:+             - snowpark      codegen_nativeapp:-    type: application-    from:-      target: codegen_nativeapp_pkg+       type: application+       from:+         target: codegen_nativeapp_pkg    ``` @@ -46,5 +46,5 @@    ``` -3. Verify the contents of the output or deploy directory match the rules you specified in the snowflake.yml. file. If you invoked Snowpark annotation processing in your Python files, you can see the generated code in the amended setup script in the directory.+3. Verify the contents of the output/deploy directory match the rules you specified in the snowflake.yml file. If you invoked Snowpark annotation processing in your Python files, you can see the generated code in the amended setup script in the directory.  For more information, see the [snow app bundle](/developer-guide/snowflake-cli/command-reference/native-apps-commands/bundle-app) command.@@ -114,5 +114,5 @@ @udf(name="echo_fn") def echo_fn(data) -> str:-  return 'echo_fn: ' + str+  return 'echo_fn: ' + data ``` @@ -150,5 +150,5 @@  - You can't use any `Session` objects in these files, as %sf-cli% executes these Python files in a sandbox environment with no connection to Snowflake. As a result, any reference of a Snowpark `Session` results in an error.-- You can use only the `@udf`, `@sproc`, `@udaf` and `@udtf` Snowpark Python decorators.+- You can use only the `@udf`, `@sproc`, `@udaf`, and `@udtf` Snowpark Python decorators. - You can't use these decorators as regular functions to register your code as a Snowflake object. Only code explicitly annotated with the supported decorators is recognized. Therefore, the Python function must be a named function. Lambda functions are not supported. - %sf-cli% always generates CREATE OR REPLACE statements, as recommended by Snowflake, for creating functions and procedures in your setup scripts. 

--- ahttps://docs.snowflake.com/en/migrations/sma-docs/use-cases/migration-lab/pipeline-conversion+++ bhttps://docs.snowflake.com/en/migrations/sma-docs/use-cases/migration-lab/pipeline-conversion@@ -27,5 +27,5 @@ Let’s start with the pipeline script file, and get to the notebook in the next section. -## Resolve Issues+## Resolve issues  Let’s open our source and our output code in a code editor. You can use any code editor of your choice, but as has been mentioned multiple times, Snowflake would recommend using **VS Code with the Snowflake Extension**. Not only does the Snowflake Extension help navigate through the issues from SnowConvert, but can also run **Snowpark Checkpoints** for Python, which would help with testing and root cause analysis (though just barely out of scope for this lab).@@ -47,5 +47,5 @@ ![Error code](/static/images/migrations/sma-assets/error-code.png) -Since I have not filtered the results, the listing of this error code in the **issues.csv** also comes up in the search and the **AssessmentReport.json** that is used to build the **AssessmentReport.docx** summary assessment report. This is the main report that users will navigate through to understand a large workload, but we did not look at it in this lab. ([More info on the this report can be found in the SMA documentation](https://docs.snowconvert.com/sma/user-guide/assessment/output-reports/curated-reports).) Let’s choose where this EWI shows up in the **pipeline_dimcustomer.py** file as shown above.+Since I have not filtered the results, the listing of this error code in the **issues.csv** also comes up in the search and the **AssessmentReport.json** that is used to build the **AssessmentReport.docx** summary assessment report. This is the main report that users will navigate through to understand a large workload, but we did not look at it in this lab. ([More info on this report can be found in the SMA documentation](https://docs.snowconvert.com/sma/user-guide/assessment/output-reports/curated-reports).) Let’s choose where this EWI shows up in the **pipeline_dimcustomer.py** file as shown above.  You can see that this line of code was present at the bottom of the source code.@@ -61,5 +61,5 @@ ``` -Looks like this parsing error was because of… “some rogue code that doesn’t make any sense!”. This line of code is at the bottom of the pipeline file. This is not unusual to have extra characters or other elements in a code file as part of an extraction from a source. Note have the SMA detected that this was not valid Python code, and it generated the parsing error.+Looks like this parsing error was because of… “some rogue code that doesn’t make any sense!”. This line of code is at the bottom of the pipeline file. This is not unusual to have extra characters or other elements in a code file as part of an extraction from a source. Note how the SMA detected that this was not valid Python code, and it generated the parsing error.  You can also see how the SMA inserts both the error code and the description into the output code as a comment where the error occurred. This is how all error messages will appear in the output.@@ -86,5 +86,5 @@ This is the write call to the spark jdbc driver to write the output dataframe into SQL Server. Since this is part of the “resolve all inputs/outputs” step that we are going to deal with after we address our issues, we’ll leave this for later. Note, however, that this error must be resolved. The previous one was just a warning and may still work with no change being made. -## Resolving the Session Calls+## Resolving the session calls  The session calls are converted by the SMA, but you should pay special attention to them to make sure they are functional. In our pipeline script, this is the before and after code:@@ -116,9 +116,9 @@ ``` -Might as well convert it to a single line. The SMA couldn’t be sure we didn’t need that driver (although that seems logical), so it did not remove it. But now that we have our session call is complete.+Might as well convert it to a single line. The SMA couldn’t be sure we didn’t need that driver (although that seems logical), so it did not remove it. But now our session call is complete.  (Note that the SMA also adds a “query tag” to the session. This is to help troubleshoot issues with this session or query later on, but this is completely optional to leave or remove.) -### Notes on the Session Calls+### Notes on the session calls  Believe it or not that is all that we need to change in the code for the session call, but that’s not all we need to do to create the session. This refers back to the original question that a lot of this depends on where you want to run these files. These original spark session calls used a configuration that was setup elsewhere. If you look at the original Spark session call it’s looking for a config file that is being read into a pandas dataframe location at the start of this script file (this is actually true for our notebook file as well).@@ -173,7 +173,7 @@ Now it's time for the most critical component of this migration, resolving any input/output references. -## Resolving the Inputs and Outputs--So let’s resolve our inputs and outputs now. Note that this is going to diverge based on whether you’re running the files locally or Snowflake. for the python script, Let’s make sure what we gain/lose by running directly inside of Snowsight: **you cannot run the whole operation in Snowsight** (at least not currently). The local csv file is not accessible from Snowsight. You will have to load the .csv file into a stage manually. This will likely not be an ideal solution, but we can test the conversion by doing this.+## Resolving the inputs and outputs++So let’s resolve our inputs and outputs now. Note that this is going to diverge based on whether you’re running the files locally or in Snowflake. For the python script, let’s make sure what we gain/lose by running directly inside of Snowsight: **you cannot run the whole operation in Snowsight** (at least not currently). The local csv file is not accessible from Snowsight. You will have to load the .csv file into a stage manually. This will likely not be an ideal solution, but we can test the conversion by doing this.  So we’ll first prep this file to be run/orchestrated locally, and then to be run in Snowflake.@@ -183,5 +183,5 @@ - access a local file - load the result into SQL Server (but now Snowflake)-- moves the file to make way for the next one+- moving the file to make way for the next one  Simple enough. So we need to replace each component of the code that does those things. Let’s start with accessing the local file.@@ -191,5 +191,5 @@ We have options to do this, but we will create an internal stage and move the file into the stage with the script. We would then need to move the file in the local file system, and also move it in the stage. This can all be done with Snowpark. Let’s break it down: -- accessing a local file: Create an internal stage (it one doesn’t exist already) -> Load the file into the stage -> Read the file into a dataframe+- accessing a local file: Create an internal stage (if one doesn’t exist already) -> Load the file into the stage -> Read the file into a dataframe - loading the result into SQL Server: Load the transformed data into a table in Snowflake - moves the file to make way for the next one: Move the local file -> Move the file in the stage.@@ -197,5 +197,5 @@ Let’s look at code that can do each of these things. -### Access a Locally Accessible File+### Access a locally accessible file  This source code in Spark looks like this:@@ -215,5 +215,5 @@ We can replace that with this with code that does the steps above: -1. Create an internal stage (if one does not exist already). We will create a stage called 'LOCAL_LOAD_STAGE' and go through a few steps to make sure that the stage is r+1. Create an internal stage (i... (truncated) 

差分が長いため、途中まで表示しています。

--- ahttps://docs.snowflake.com/en/migrations/virtualization/aim-virtualization-overview+++ bhttps://docs.snowflake.com/en/migrations/virtualization/aim-virtualization-overview@@ -1,3 +1,3 @@-# **Snowflake AIM for Virtualization of Teradata**+# Snowflake AIM for Virtualization of Teradata  **Generally Available**@@ -7,9 +7,9 @@ --- -## **1\. Product Overview**+## 1. Product Overview  This is an overview of Snowflake AIM for the Virtualization of Teradata, along with key requirements to run the software. -Snowflake AIM's virtualization capabilities enables existing Teradata-based applications to maintain native functionality on Snowflake, minimizing the need for any SQL modifications or code rewrites. By translating SQL in real-time, Snowflake AIM allows existing applications to run natively on Snowflake with identical results, interoperability, and minimal switching costs.+Snowflake AIM's virtualization capabilities enable existing Teradata-based applications to maintain native functionality on Snowflake, minimizing the need for any SQL modifications or code rewrites. By translating SQL in real time, Snowflake AIM allows existing applications to run natively on Snowflake with identical results, interoperability, and minimal switching costs.  ![Snowflake AIM for Virtualization overview diagram.](/static/images/migrations/sc-assets/aim-virtualization-overview.png)@@ -17,22 +17,22 @@ --- -## **2\. Core Architecture**+## 2. Core Architecture -Snowflake AIM for the Virtualization of Teradata is a gateway situated between the enterprise's existing applications (on-premises or in-cloud) and the Snowflake AI Data Cloud. Snowflake AIM for Virtualization, can be deployed on premises or in a customer's cloud subscription. Snowflake AIM is available as a RPM for the customer to deploy and manage on a Red Hat-compatible Linux VM.+Snowflake AIM for the Virtualization of Teradata is a gateway situated between the enterprise's existing applications (on-premises or in-cloud) and the Snowflake AI Data Cloud. Snowflake AIM for Virtualization can be deployed on premises or in a customer's cloud subscription. Snowflake AIM is available as an RPM for the customer to deploy and manage on a Red Hat-compatible Linux VM.  ![Reference architecture diagram for Snowflake AIM for Virtualization of Teradata.](/static/images/migrations/sc-assets/aim-virtualization-architecture.png) -### **2.1\. System Requirements**+### 2.1. System Requirements  * 32 - 64 core VM (the product scales both horizontally and vertically)-* 2 VM for production workloads, behind a standard load balancer designed for failover+* 2 VMs for production workloads, behind a standard load balancer designed for failover * Red Hat Linux 8.x or 9.x compatible * 500GB of SSD data disk * Inbound port 1025 for existing client tools-* Inbound port 22 for operators of the virtual machine to install, test, run.+* Inbound port 22 for operators of the virtual machine to install, test, and run the software. -### **2.2\. Deployment**+### 2.2. Deployment -* **Architecture:** Snowflake AIM for Virtualization is a stateless database virtualization engine, deployed within the customer's environment \- on-premises or in-cloud.+* **Architecture:** Snowflake AIM for Virtualization is a stateless database virtualization engine, deployed within the customer's environment: on-premises or in-cloud. * **Scalability:** Snowflake AIM for Virtualization scales vertically with CPU resources and horizontally across multiple VMs using a standard load balancer. * **Self-Contained:** Snowflake AIM for Virtualization has no external dependencies; all auxiliary metadata is stored directly within Snowflake.@@ -40,5 +40,5 @@ --- -## **3\. XTRA Engine**+## 3. XTRA Engine  Central to Snowflake AIM for Virtualization is the **XTRA (Extensible Relational Algebra)** engine. Snowflake AIM for Virtualization performs a deep semantic analysis of every SQL request.@@ -51,7 +51,7 @@ --- -## **4\. Metadata Management**+## 4. Metadata Management -For features where no direct mapping exists between Teradata and Snowflake (e.g., SET Tables, Global Temporary Tables), Snowflake AIM for Virtualization utilizes a specialized **Metadata Store** which stores Teradata-specific properties. These are consulted at run time for translation and emulation of SQL and the conversion of results.+For features where no direct mapping exists between Teradata and Snowflake (for example, SET Tables, Global Temporary Tables), Snowflake AIM for Virtualization utilizes a specialized **Metadata Store** which stores Teradata-specific properties. These are consulted at run time for translation and emulation of SQL and the conversion of results.  * **Metadata Store:** A collection of objects stored within a dedicated Snowflake schema.@@ -61,5 +61,5 @@ --- -## **5\. Supported Application Types**+## 5. Supported Application Types  * All commonly used SQL and protocols associated with Teradata 14.0 and higher are supported.@@ -69,5 +69,5 @@ --- -## **6\. Supported Data Types and Formats**+## 6. Supported Data Types and Formats  * Snowflake AIM for Virtualization supports all data types and formats commonly used in Teradata SQL, including data types not natively available in Snowflake.@@ -78,5 +78,5 @@ --- -## **7\. Supported Syntax**+## 7. Supported Syntax  While there are no technical limits to virtualization, Snowflake AIM for Virtualization supports primarily commonly used SQL and APIs. In practice, Snowflake AIM for Virtualization provides an average of at least **99.5% syntax coverage** for typical Teradata workloads.@@ -88,5 +88,5 @@ --- -## **8\. Implementation Workflow: Repoint, Test, Transition**+## 8. Implementation Workflow: Repoint, Test, Transition  The transition to Snowflake follows a non-disruptive, phased approach which allows IT leaders to:@@ -96,11 +96,11 @@ * **Repoint:** Update application connection strings (JDBC/ODBC) to the Snowflake AIM for Virtualization endpoint. * **Verify:** Execute dual-run testing to confirm parity between Teradata and Snowflake results.-* **Transition:** Cut over production traffic (e.g., by changing a central DNS record) and decommission the legacy Teradata system.+* **Transition:** Cut over production traffic (for example, by changing a central DNS record) and decommission the legacy Teradata system.  --- -## **9\. Pricing & Cost Considerations**+## 9. Pricing & Cost Considerations -Use of the Snowflake AIM for Virtualization software is subject to the price terms in your Order Form. AIM for Virtualization connects to the Snowflake Service. Queries routed to and run on the Snowflake Service will incur costs as described in the Snowflake Service Consumption table, found at https://www.snowflake.com/legal-files/CreditConsumptionTable.pdf.+Use of the Snowflake AIM for Virtualization software is subject to the price terms in your Order Form. AIM for Virtualization connects to the Snowflake Service. Queries routed to and run on the Snowflake Service will incur costs as described in the [Snowflake Service Consumption table](https://www.snowflake.com/legal-files/CreditConsumptionTable.pdf).  --- 

--- ahttps://docs.snowflake.com/en/sql-reference/sql/alter-warehouse+++ bhttps://docs.snowflake.com/en/sql-reference/sql/alter-warehouse@@ -9,5 +9,5 @@ <dd> -[](/sql-reference/sql/create-warehouse) , [](/sql-reference/sql/desc-warehouse) , [](/sql-reference/sql/drop-warehouse) , [](/sql-reference/sql/show-warehouses)+[](/sql-reference/sql/create-warehouse), [](/sql-reference/sql/desc-warehouse), [](/sql-reference/sql/drop-warehouse), [](/sql-reference/sql/show-warehouses)  </dd>@@ -179,20 +179,20 @@ the number of credits consumed while the warehouse is running. -For more information see [](#label-resizing-a-warehouse).--<dl className="field-list">-<dt>Valid values<span className="colon">:</span></dt>-<dd>--- `XSMALL` , `'X-SMALL'`+For more information, see [](#label-resizing-a-warehouse).++<dl className="field-list">+<dt>Valid values<span className="colon">:</span></dt>+<dd>++- `XSMALL`, `'X-SMALL'` - `SMALL` - `MEDIUM` - `LARGE`-- `XLARGE` , `'X-LARGE'`-- `XXLARGE` , `X2LARGE` , `'2X-LARGE'`-- `XXXLARGE` , `X3LARGE` , `'3X-LARGE'`-- `X4LARGE` , `'4X-LARGE'`-- `X5LARGE` , `'5X-LARGE'`-- `X6LARGE` , `'6X-LARGE'`+- `XLARGE`, `'X-LARGE'`+- `XXLARGE`, `X2LARGE`, `'2X-LARGE'`+- `XXXLARGE`, `X3LARGE`, `'3X-LARGE'`+- `X4LARGE`, `'4X-LARGE'`+- `X5LARGE`, `'5X-LARGE'`+- `X6LARGE`, `'6X-LARGE'`  </dd>@@ -635,5 +635,5 @@ <dd> -Object parameter that specifies the concurrency level for SQL statements (i.e. queries and DML) executed by a warehouse cluster. When+Object parameter that specifies the concurrency level for SQL statements (that is, queries and DML) executed by a warehouse cluster. When the level is reached: @@ -658,5 +658,5 @@ <dd> -Object parameter that specifies the time, in seconds, a SQL statement (query, DDL, DML, etc.) can be queued on a warehouse before it is+Object parameter that specifies the time, in seconds, a SQL statement (query, DDL, DML, and so on) can be queued on a warehouse before it is canceled by the system. @@ -673,5 +673,5 @@ <dd> -Object parameter that specifies the time, in seconds, after which a running SQL statement (query, DDL, DML, etc.) is canceled by the system.+Object parameter that specifies the time, in seconds, after which a running SQL statement (query, DDL, DML, and so on) is canceled by the system.  For a detailed description of this parameter, see [](#label-statement-timeout-in-seconds).@@ -925,5 +925,5 @@  -- Resuming a Snowpark-optimized virtual warehouse may take longer than standard warehouses.+- Resuming a Snowpark-optimized virtual warehouse may take longer than for standard warehouses. - Snowpark-optimized warehouses don't support [Query Acceleration](/user-guide/query-acceleration-service). - Specifying the `IF EXISTS` clause requires the role in use or a role in the active role hierarchy to have the appropriate 

--- ahttps://docs.snowflake.com/en/connectors/google/gard/gard-connector-managing+++ bhttps://docs.snowflake.com/en/connectors/google/gard/gard-connector-managing@@ -135,21 +135,21 @@ The connector upgrades are managed automatically by the provider of the application. -## Scaling the Connector--You should start your work with the Connector using a `X-Small` as it will most likely give you a sufficient performance.-However, if you are experiencing any Connector slowdowns, you may want to try gradually increasing the warehouse size and evaluating-whether you see any performance boosts at each step. Whether the Connector gains anything from scaling the warehouse depends on+## Scaling the connector++You should start your work with the connector using an `X-Small` as it will most likely give you sufficient performance.+However, if you are experiencing any connector slowdowns, you may want to try gradually increasing the warehouse size and evaluating+whether you see any performance boosts at each step. Whether the connector gains anything from scaling the warehouse depends on a few factors, such as the number of properties or the amount of data each of them has. -For insights on how to resize the warehouse see Resizing a warehouse in [](/user-guide/warehouses-tasks).+For insights on how to resize the warehouse, see Resizing a warehouse in [](/user-guide/warehouses-tasks).  If you are constantly experiencing ingestion errors related to insufficient memory and are already using a `LARGE` or `X-LARGE` warehouse, then you can try to resolve this issue by decreasing the `MAX_CONCURRENCY_LEVEL` parameter on a warehouse from 8 (default) to 4. -## Changing the warehouse for the Connector+## Changing the warehouse for the connector  It is possible to change the warehouse that the %gard% uses for its internal tasks without reinstalling the connector.-First, make sure that the Connector is paused. It can be done either via UI or using the `PAUSE_CONNECTOR` procedure.-Then, you need to grant the Connector access to the new warehouse:+First, make sure that the connector is paused. It can be done either via the UI or using the `PAUSE_CONNECTOR` procedure.+Then, you need to grant the connector access to the new warehouse:  ```sqlsyntax@@ -160,14 +160,14 @@  ```sqlsyntax-CALL UPDATE_WAREHOUSE('<new_warehouse_name');+CALL UPDATE_WAREHOUSE('<new_warehouse_name>'); ```  <a id="label-re-authentication-of-the-connector"></a> -## Re-authentication of the Connector+## Re-authentication of the connector  In order to change the secret, external access integration or the security integration used by the connector without re-installation, you need to execute the `UPDATE_CONNECTION` procedure defined in the `PUBLIC` schema.-Ensure, that all of the new objects are defined as described in [](/connectors/google/gard/gard-connector-configuring-sql) and that the connector has all of the required grants.+Ensure that all of the new objects are defined as described in [](/connectors/google/gard/gard-connector-configuring-sql) and that the connector has all of the required grants.  ```sqlsyntax@@ -177,6 +177,6 @@ ## Automatically disabling inaccessible Google Analytics properties -The Connector has a mechanism to automatically disable inaccessible Google Analytics properties in order to prevent unnecessary-costs caused by attempting ingestions for data which does not exist indefinitely and alarm you that data is not being ingested anymore.+The connector has a mechanism to automatically disable inaccessible Google Analytics properties in order to prevent unnecessary+costs caused by attempting ingestions indefinitely for data that does not exist, and to notify you that data is not being ingested anymore. The property is considered inaccessible and might be automatically disabled if data ingestions have been failing for the last 7 days. @@ -186,8 +186,8 @@ set up the **sink database failover** to a replica account. For details, see [](/user-guide/database-failover-config). -Moreover, after an outage you need to manually install the %gard% on your replica account, because the connector itself can not be replicated.+Moreover, after an outage you need to manually install the %gard% on your replica account, because the connector itself can't be replicated. After the installation it will synchronize itself with the replicated sink database. -In order to prevent data corruption you can not have two connector instances, one on a primary account and one on a replica account+In order to prevent data corruption, you can't have two connector instances, one on a primary account and one on a replica account ingesting data to the sink database at the same time. @@ -214,6 +214,6 @@ - `DISABLE_AUTO_RELOADS` - Disables auto reloading data. For more details about auto reload see [](/connectors/google/gard/gard-connector-data-ingestion-model).   Setting this value to `TRUE` can reduce credit consumption, but late data won't be ingested into Snowflake. This property-  cannot be set to `true` for the `FRESH_DAILY` export type. The default value is `FALSE`.-- `ENABLED_EXPORT_TYPES` - A list of export types, which connector will try to ingest data for. Possible values are: `DAILY`, `FRESH_DAILY`, `INTRADAY`, `USERS` and `PSEUDONYMOUS_USERS`.+  cannot be set to `TRUE` for the `FRESH_DAILY` export type. The default value is `FALSE`.+- `ENABLED_EXPORT_TYPES` - A list of export types that the connector will try to ingest data for. Possible values are: `DAILY`, `FRESH_DAILY`, `INTRADAY`, `USERS` and `PSEUDONYMOUS_USERS`.  </blockquote> 

--- ahttps://docs.snowflake.com/en/developer-guide/native-apps/consumer-guide-about+++ bhttps://docs.snowflake.com/en/developer-guide/native-apps/consumer-guide-about@@ -11,9 +11,9 @@ - [](/developer-guide/native-apps/consumer-guide-responsibility) -## Definition — from a consumer's perspective+## Definition: from a consumer's perspective  A Snowflake Native App is a data application published by a third party that is installed and runs entirely inside your Snowflake account. Unlike a web application you log into, or a connected tool-that extracts your data to process it elsewhere, a Native App lives where your data already lives —+that extracts your data to process it elsewhere, a Native App lives where your data already lives: inside your Snowflake environment, under your governance, accessible through the same interface and controls you already use.@@ -28,5 +28,5 @@  **Access is controlled by the same Snowflake roles and policies you already use.** You grant the app-access to the data it needs using standard Snowflake Role-Based Access Control (RBAC) — the same+access to the data it needs using standard Snowflake Role-Based Access Control (RBAC), the same mechanisms your team already uses. Your existing masking policies, row-access policies, and governance controls continue to apply inside the app's scope.@@ -36,5 +36,5 @@ upgrades. Uninstalling is fully under your control. -## Native App vs. Connected App vs. SaaS — which model fits your needs?+## Native App versus Connected App versus SaaS: which model fits your needs?  **A Native App brings the app to your data, not your data to the app.**@@ -48,5 +48,5 @@ | Data egress      | You control it (explicit grants) | App vendor controls (connection creds) | Vendor controls (replication) | -**Connected apps** — such as a BI charting tool connecting via ODBC — run outside your Snowflake+**Connected apps**, such as a BI charting tool connecting via ODBC, run outside your Snowflake security perimeter. They retrieve your data to process it elsewhere and return results. Your data leaves your account, carrying compliance and governance implications that must be managed separately.@@ -57,8 +57,8 @@ **Three patterns show where Native Apps have a clear advantage:** -**Pattern 1 — Data ingestion (example: Salesforce connector)**+**Pattern 1: Data ingestion (example: Salesforce connector)**  A connector that pulls data from Salesforce into your Snowflake account needs to run close to the-data destination — your account. The app uses an External Access Integration (EAI) that you+data destination: your account. The app uses an External Access Integration (EAI) that you explicitly authorize to make the outbound call to Salesforce. The data flows in; it does not flow out. With a traditional connected connector, your Snowflake credentials and Salesforce credentials@@ -66,5 +66,5 @@ your control. -**Pattern 2 — Pure computation (example: knowledge graph builder)**+**Pattern 2: Pure computation (example: knowledge graph builder)**  An app that builds a knowledge graph from your relational data runs inside your account as a@@ -73,10 +73,10 @@ the vendor's system for processing. -**Pattern 3 — Data collaboration (example: identity resolution)**+**Pattern 3: Data collaboration (example: identity resolution)**  An identity resolution app brings the provider's proprietary identity graph and joins it with your customer data inside your account. Neither party's raw data crosses the boundary: the provider's identity graph is protected from you (provider IP protection); your customer data never leaves-Snowflake (consumer data protection). Only the derived results — better-matched customer records —+Snowflake (consumer data protection). Only the derived results (better-matched customer records) are visible. This pattern cannot be done safely with a connected app, which would require sending your customer data to the vendor's infrastructure where the identity graph also lives.@@ -86,5 +86,5 @@ and there is no separate data silo to manage or reconcile (unlike a SaaS app). -## The consumer lifecycle — a guide to this guide+## The consumer lifecycle  Working with a Native App follows five stages. Each stage maps to a section of this guide.@@ -92,13 +92,13 @@ ![](/static/images/native-apps/na-consumer-lifecycle.png) -**Stage 1 — Evaluation**+**Stage 1: Evaluation**  Before committing to procurement, many organizations run a Proof-of-Concept (PoC) or Proof-of-Value (PoV) with the provider to establish business value. This phase typically involves lighter-weight security and procurement review. Even at this stage, be deliberate about what access-you grant — only what the PoC genuinely requires. See [](/developer-guide/native-apps/consumer-guide-evaluate)+you grant, only what the PoC genuinely requires. See [](/developer-guide/native-apps/consumer-guide-evaluate) for evaluation guidance and [](/developer-guide/native-apps/consumer-guide-access) for access decisions. -**Stage 2 — Procurement**+**Stage 2: Procurement**  Once business value is established, the app goes through a full procurement process covering@@ -108,5 +108,5 @@ [](/developer-guide/native-apps/consumer-guide-responsibility) for the formal shared-responsibility framework. -**Stage 3 — Installation and initial configuration**+**Stage 3: Installation and initial configuration**  An account admin or their delegate installs the app. At this stage the app presents its privilege@@ -116,13 +116,13 @@ [](/developer-guide/native-apps/consumer-guide-access) for access configuration. -**Stage 4 — Active use**+**Stage 4: Active use**  The app delivers business value. Upgrades happen automatically via patches (high compatibility) or new versions (two-version compatibility window). During active use, the app may occasionally request-additional privileges or new App Spec approvals — these deserve the same scrutiny as at installation.+additional privileges or new App Spec approvals. These deserve the same scrutiny as at installation. See [](/developer-guide/native-apps/consumer-guide-upgrades) for upgrades and [](/developer-guide/native-apps/consumer-guide-monitor) for monitoring. -**Stage 5 — Uninstallation**+**Stage 5: Uninstallation**  If the app is no longer needed, transfer ownership of any objects the app created outside its own 

--- ahttps://docs.snowflake.com/en/developer-guide/native-apps/consumer-guide-access+++ bhttps://docs.snowflake.com/en/developer-guide/native-apps/consumer-guide-access@@ -24,12 +24,12 @@  Access is structured into three distinct categories, described below. Understanding the categories-helps you make informed decisions at installation time and throughout the app's lifecycle — because+helps you make informed decisions at installation time and throughout the app's lifecycle, because apps may request additional access not just at installation, but during upgrades and during active use. -## Category 1 — Automatically grantable privileges+## Category 1: Automatically grantable privileges  Six privileges are available for the app to request. These allow the app to create operational-resources in your account. They do not, by themselves, grant the app access to your data — that+resources in your account. They do not, by themselves, grant the app access to your data. That happens only through Category 3. @@ -56,5 +56,5 @@  If the app requests new Category 1 privileges during an upgrade, the provider must disclose this to-you in advance. These additional requests do not appear silently — you will be notified before the+you in advance. These additional requests do not appear silently. You will be notified before the upgrade proceeds. @@ -62,5 +62,5 @@ Category 3 grants. These are operational resource grants only. -## Category 2 — Application Specifications (App Specs)+## Category 2: Application Specifications (App Specs)  Some apps need to do things that carry higher risk than creating operational resources: making@@ -76,5 +76,5 @@  You can approve none, some, or all of an app's App Specs. Each is an independent decision. If you-are not comfortable with a particular App Spec, you can decline it — the app will not have access+are not comfortable with a particular App Spec, you can decline it. The app will not have access to that capability. Some app functionality may be limited or unavailable if certain App Specs are not approved, but the app will not receive the capability without your approval.@@ -98,5 +98,5 @@  **External Access Integration (EAI):** the app will make outbound network calls to a specific named-external endpoint. The endpoint is defined in the integration — you are approving access to that+external endpoint. The endpoint is defined in the integration. You're approving access to that specific destination, not open-ended internet access. Verify that the endpoint is a legitimate destination for this type of app (for example, a known ERP or CRM API endpoint for a connector app).@@ -115,8 +115,8 @@ [](/developer-guide/native-apps/ui-consumer-app-spec). -## Category 3 — Explicitly granted privileges+## Category 3: Explicitly granted privileges  Category 3 is how the app gets access to your data. Nothing in Categories 1 or 2 touches your-data. Category 3 may be app-requested but is entirely consumer-controlled — you choose what to+data. Category 3 may be app-requested but is entirely consumer-controlled. You choose what to grant, when, and to what scope. Everything is revocable at any time. @@ -131,10 +131,10 @@ References are an object-level mechanism where the app pre-declares a named reference "slot" (for example, "I need a table matching this shape" or "I need a table with an ID column") and you bind a-specific object to that slot. References work at the level of individual named objects only — there+specific object to that slot. References work at the level of individual named objects only. There is no database-level reference, and references do not cover objects created in the future (for example, new views added to a database after the reference is established).  **Direct object grants:**-You grant the app access to specific named objects — individual views, tables, schemas, or stored+You grant the app access to specific named objects: individual views, tables, schemas, or stored procedures. This is the most explicit and auditable approach. Grant only what the app needs. @@ -148,5 +148,5 @@   data. -**Database role grants (database scope — use deliberately):**+**Database role grants (database scope, use deliberately):** Grant a database role to the app. Database role grants typically apply at the database level and can cover future objects created in that database scope after the grant is made. Use this level of@@ -156,10 +156,10 @@ You may grant additional privileges to an app at any point after installation. For example, a data quality assurance app working against one database could be reconfigured later to cover additional-databases at your discretion. Regardless, you control access to your database objects — at+databases at your discretion. Regardless, you control access to your database objects, at installation and throughout the app's lifecycle.  For full instructions, see [](/developer-guide/native-apps/ui-consumer-granting-privs). -## Feature policies — limiting what the app can create+## Feature policies: limiting what the app can create  Feature policies give you a governance lever that is orthogonal to the three access categories: you@@ -181,11 +181,11 @@  Restricted Callers Rights (RCR) enables a different mode: the app runs with the rights of the-caller — the Snowflake user currently executing a request. The app can only access what that user+caller, the Snowflake user currently executing a request. The app can only access what that user can access, further bounded by the restrictions defined in the RCR grant. For example, an app may be allowed access to all that a user can access but only in a specific database. An account admin can choose to allow caller's rights by imposing no restrictions, but use such elevated privileges-carefully — especially if highly privileged users intend to use the app.+carefully, especially if highly privileged users intend to use the app. -This model is appropriate for apps where per-user data access is the intended design — for example,+This model is appropriate for apps where per-user data access is the intended design, for example, a notebook-style app where different users should see different data based on their own Snowflake roles. It is not appropriate for apps that should run under a consistent, predictable access 

--- ahttps://docs.snowflake.com/en/user-guide/data-exchange-marketplace-privileges+++ bhttps://docs.snowflake.com/en/user-guide/data-exchange-marketplace-privileges@@ -69,7 +69,7 @@ | [](#label-modify-on-data-exchange-listing)         | LISTING          | Role with the OWNERSHIP privilege on the listing. | Grants the ability to modify listing properties.                                                          | | [](#label-usage-on-data-exchange-listing)          | LISTING          | Role with the OWNERSHIP privilege on the listing. | Grants the ability to view a listing.                                                                     |-| [](#label-ownership-on-data-exchange-listing)      | LISTING          | Role with the OWNERSHIP privilege on the listing. | Transfer the OWNERSHIP privilege on the listing.                                                          |+| [](#label-ownership-on-data-exchange-listing)      | LISTING          | Role with the OWNERSHIP privilege on the listing. | Grants the ability to transfer the OWNERSHIP privilege on the listing.                                    | | [](#label-modify-on-provider-profile)              | PROVIDER PROFILE | Role with the OWNERSHIP privilege on the profile. | Grants the ability to modify properties for a provider profile.                                           |-| [](#label-ownership-on-provider-profile)           | PROVIDER PROFILE | Role with the OWNERSHIP privilege on the profile. | Transfer the OWNERSHIP privilege on the profile.                                                          |+| [](#label-ownership-on-provider-profile)           | PROVIDER PROFILE | Role with the OWNERSHIP privilege on the profile. | Grants the ability to transfer the OWNERSHIP privilege on the profile.                                    |  ### Account-level privileges@@ -80,5 +80,5 @@ - [](#label-create-data-exchange-listing-on-account) - [](#label-create-share-on-account)-- [](#label-import-share-privilege)+- [](#label-import-share-on-account)  <a id="label-create-data-exchange-listing-on-account"></a>@@ -90,5 +90,5 @@  - Create listings.-- Modify listings properties.+- Modify listing properties. - View listings. - View incoming listing requests.@@ -195,9 +195,9 @@ 4. Locate the listing that you want to modify and select the row to open the listing details. 5. In the listing details page, select **Settings**.-6. In the **Privileges** section, select the pencil icon next to the **Modify Listing** privilege.-7. Select **Add Role** and add required roles.-8. Save your changes.--To grant the MODIFY privilege on a listing in a data exchange:+6. In the **Privileges** section, select the pencil icon next to the **Usage** privilege.+7. Select **Add Role** and add required roles.+8. Save your changes.++To grant the MODIFY privilege on a listing in a Data Exchange:  1. Sign in to %sf-web-interface-link%.@@ -206,5 +206,5 @@ 4. Locate the listing that you want to modify and select the row to open the listing details. 5. In the listing details page, select **Settings**.-6. In the **Privileges** section, select the pencil icon next to the **Modify Listing** privilege.+6. In the **Privileges** section, select the pencil icon next to the **Usage** privilege. 7. Select **Add Role** and add required roles. 8. Save your changes.@@ -224,9 +224,9 @@ 4. Locate the listing that you want to modify and select the row to open the listing details. 5. In the listing details page, select **Settings**.-6. In the **Privileges** section, select the pencil icon next to the **Modify Listing** privilege.-7. Select **Add Role** and add required roles.-8. Save your changes.--To grant the USAGE privilege on a listing in a data exchange:+6. In the **Privileges** section, select the pencil icon next to the **Ownership** privilege.+7. Select **Add Role** and add required roles.+8. Save your changes.++To grant the USAGE privilege on a listing in a Data Exchange:  1. Sign in to %sf-web-interface-link%.@@ -235,5 +235,5 @@ 4. Locate the listing that you want to modify and select the row to open the listing details. 5. In the listing details page, select **Settings**.-6. In the **Privileges** section, select the pencil icon next to the **Modify Listing** privilege.+6. In the **Privileges** section, select the pencil icon next to the **Ownership** privilege. 7. Select **Add Role** and add required roles. 8. Save your changes.@@ -260,5 +260,5 @@ 8. Save your changes. -To grant the OWNERSHIP privilege on a listing in a data exchange:+To grant the OWNERSHIP privilege on a listing in a Data Exchange:  1. Sign in to %sf-web-interface-link%. 

--- ahttps://docs.snowflake.com/en/developer-guide/native-apps/tutorials/getting-started-tutorial+++ bhttps://docs.snowflake.com/en/developer-guide/native-apps/tutorials/getting-started-tutorial@@ -10,5 +10,5 @@ The %naf% allows providers to build, sell, and distribute a %native-app% within the Snowflake Data Cloud. Providers can create apps that leverage core Snowflake functionality to share data-and application logic with consumers. The logic of %native-app% can include features such as stored procedures,+and application logic with consumers. The logic of a %native-app% can include features such as stored procedures and user-defined functions (UDFs). Providers can share their applications with consumers through listings in the Snowflake Marketplace or through private listings.@@ -17,5 +17,5 @@ with other Snowflake accounts. -The tutorial uses both %sf-cli% and the %sf-web-interface% web interface.+The tutorial uses both %sf-cli% and %sf-web-interface%.  ### What you learn in this tutorial@@ -138,5 +138,5 @@ ## Create a Snowflake CLI connection for the tutorial -To run the %sf-cli% commands in this tutorial, you must setup a %sf-cli% connection for the tutorial.+To run the %sf-cli% commands in this tutorial, you must set up a %sf-cli% connection for the tutorial.  To create a connection:@@ -258,5 +258,5 @@ This line is a placeholder because the setup script cannot be empty. -This tutorial refers a particular structure and filename for the setup+This tutorial refers to a particular structure and filename for the setup script. However, when building your own app you can choose your own name and directory structure for this file.@@ -375,5 +375,5 @@ Note that the name of the stage is specified as a schema-qualified name. This schema is created inside the application package. This named stage is used to store the files required by the-%naf%. This stage must include any files you want available to the setup script of your app setup+%naf%. This stage must include any files you want available to the app's setup script or at runtime. @@ -395,5 +395,5 @@  In this section you learned that an application package is a container for the resources used by an-app. You also learned the how to set the fields in the project definition file.+app. You also learned how to set the fields in the project definition file.  ## Add application logic and install your first app@@ -474,5 +474,5 @@ This command performs the following tasks: -1. Create an application package name `hello_snowflake_package` with schema `stage_content` and+1. Create an application package named `hello_snowflake_package` with schema `stage_content` and    stage `hello_snowflake_stage`. 2. Upload all required files to the named stage.@@ -641,5 +641,5 @@     This uploads all the edited files to the stage, runs the `scripts/shared_content.sql` script,-   and upgrade the app using those files on the stage.+   and upgrades the app using those files on the stage.  2. To verify that the view works correctly, run the following command:@@ -731,5 +731,5 @@    ``` -   Similar to the previous example, these statement create a Python UDF in a schema and grants+   Similar to the previous example, these statements create a Python UDF in a schema and grant    privileges on the function to the application role. However, this example contains an    IMPORTS clause that refers to an external Python file that you create and include in@@ -848,5 +848,5 @@    ``` -   This statement creates a STREAMLIT object in the core schema.+   This statement creates a STREAMLIT object in the code_schema schema.  2. Add the following statement at the end of the `setup_script.sql` file to allow the APP_PUBLIC role to@@ -976,6 +976,5 @@ ``` -12. Grant the ACCOUNTADMIN role with the privilege to attach a listing for the HELLO_SNOWFLAKE_PACKAGE application package:-    following command:+12. Grant the ACCOUNTADMIN role the privilege to attach a listing for the HELLO_SNOWFLAKE_PACKAGE application package by running the following command:  ```sql@@ -1004,5 +1003,5 @@ In this section, you publish your app by creating a private listing that uses the application package as the data content. After creating the listing,-you login to another account to install the listing.+you log in to another account to install the listing.  ### Set the release channel@@ -1029,5 +1028,5 @@    This command displays the versions and patches defined for the application package. -2. To attach the previously created version to the `default` release channel , run the following command:+2. To attach the previously created version to the `default` release channel, run the following command:     ```snowcli@@ -1122,6 +1121,5 @@ ## Learn more -Congratulations! Not only have you finished this tutorial, but you have worked through-development and publishing life cycle of an app using the %naf%.+Congratulations! Not only have you finished this tutorial, but you have worked through the development and publishing life cycle of an app using the %naf%.  Along the way, you:@@ -1145,5 +1143,5 @@ - Added logic to your app using stored procedures and UDFs written in Python.   - Refer to [](/developer-guide/native-apps/adding-application-logic) for information-    on using stored procedures, UDFs, and external function in the %naf%.+    on using stored procedures, UDFs, and external functions in the %naf%.   - Refer to [](/developer-guide/snowpark/index), [](/developer-guide/extensibility)     and [](/sql-reference/external-functions) for general information on each type of@@ -1163,5 +1161,5 @@   separate Snowflake account.   - Refer to [Sharing an App with Consumers](https://other-docs.snowflake.com/en/native-apps/provider-publishing-app-package)-    for information on publish a listing containing an application package.+    for information on publishing a listing containing an application package.   - Refer to [Installing an App from a Listing](https://other-docs.snowflake.com/en/native-apps/consumer-installing)     for information on how consumers install an app from a listing. 

--- ahttps://docs.snowflake.com/en/migrations/aim-for-datawarehouses/code-conversion/function-references/general+++ bhttps://docs.snowflake.com/en/migrations/aim-for-datawarehouses/code-conversion/function-references/general@@ -17,5 +17,5 @@ `INPUT_PART` VARCHAR -The format of the operation. E.g.: `DAY`, `HOUR TO SECOND,` `YEAR TO MONTH`.+The format of the operation. For example: `DAY`, `HOUR TO SECOND`, `YEAR TO MONTH`.  `INPUT_VALUE` VARCHAR@@ -25,5 +25,5 @@ `INPUT_MULT` INTEGER -The time to multiply the interval of time.+The factor by which to multiply the interval.  ### Returns@@ -104,5 +104,5 @@ `INPUT_PART` VARCHAR -The related type of the second parameter. E.g. `DAY`, `DAY TO HOUR`, `HOUR`, `MINUTE`.+The related type of the second parameter. For example, `DAY`, `DAY TO HOUR`, `HOUR`, `MINUTE`.  `INPUT_VALUE` VARCHAR@@ -187,5 +187,5 @@ `INPUT_PART` VARCHAR -The related type of the second parameter. E.g. `DAY`, `DAY TO HOUR`, `HOUR`, `MINUTE`, `MINUTE TO SECOND`.+The related type of the second parameter. For example, `DAY`, `DAY TO HOUR`, `HOUR`, `MINUTE`, `MINUTE TO SECOND`.  `INPUT_VALUE` VARCHAR@@ -195,5 +195,5 @@ ### Returns -Returns+Returns a varchar representing the converted time interval.  ### Usage example@@ -351,5 +351,5 @@ `D2` TIME -The input time to converts into a separate interval.+The input time to convert into a separate interval.  ### Returns@@ -419,5 +419,5 @@ ```sql :force:-DATEADD_UDF(INTERVAL_VALUE STRING,D TIMESTAMP)+DATEDIFF_UDF(INTERVAL_VALUE STRING, D TIMESTAMP) ``` @@ -468,5 +468,5 @@ `INPUT_PART` VARCHAR -The related type of the second parameter. E.g. `YEAR TO MONTH`, `YEAR`, `MONTH`.+The related type of the second parameter. For example, `YEAR TO MONTH`, `YEAR`, `MONTH`.  `INPUT_VALUE` VARCHAR@@ -476,5 +476,5 @@ ### Returns -Returns a varchar with the input value transform to an interval.+Returns a varchar with the input value transformed to an interval.  ### Usage example@@ -633,5 +633,5 @@ `INPUT_PART1` VARCHAR -The time type of the _`INPUT_VALUE1`_. E.g.: `HOUR`.+The time type of the _`INPUT_VALUE1`_. For example: `HOUR`.  `INPUT_VALUE2` VARCHAR@@ -641,5 +641,5 @@ `INPUT_PART2` VARCHAR -The time type of the _`INPUT_VALUE2`_. E.g.: `HOUR`.+The time type of the _`INPUT_VALUE2`_. For example: `HOUR`.  `OP` CHAR@@ -720,5 +720,5 @@ ```sql :force:-TRUNC_UDF(INPUT TIMESTAMP_LTZ)+TRUNC_UDF(DATE_TO_TRUNC TIMESTAMP_LTZ) ``` @@ -794,9 +794,9 @@ ### Definition -This user-defined store procedure (UDP) is used to log messages using the Snowflake [SYSTEM$LOG](/developer-guide/logging-tracing/logging-snowflake-scripting) functions.--```sql-:force:-DATEADD_UDF(D TIMESTAMP, INTERVAL_VALUE STRING)+This user-defined stored procedure (UDP) is used to log messages using the Snowflake [SYSTEM$LOG](/developer-guide/logging-tracing/logging-snowflake-scripting) functions.++```sql+:force:+LOG_INFO_UDP(MESSAGE VARCHAR) ```  

--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-ml/inference/real-time-inference-rest-api+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-ml/inference/real-time-inference-rest-api@@ -34,5 +34,5 @@  - Version 1.8.0 or later of the snowflake-ml-python Python package.-- A model logged into [Snowflake Model Registry](/developer-guide/snowflake-ml/model-registry/overview).+- A model logged in [Snowflake Model Registry](/developer-guide/snowflake-ml/model-registry/overview). - An understanding of [compute pools](/developer-guide/snowpark-container-services/working-with-compute-pool) and   related privileges on SPCS.@@ -56,5 +56,5 @@ The following limitations apply to online model serving in Snowpark Container Services. -- Table functions aren't supported. Your model must have a table function to be deployed to Snowflake.+- Table functions aren't supported. Your model must NOT have a table function to be deployed to Snowflake. - Models developed using Snowpark ML modeling classes   can't be deployed to environments that have a GPU. As a workaround, you can extract the native model and deploy that. For more information,@@ -137,5 +137,5 @@ <a id="label-real-time-inference-invoking-deployed-model"></a> -## Invoking deployed model+## Invoking a deployed model  <a id="label-real-time-inference-http-endpoints"></a>@@ -159,5 +159,5 @@ predict-proba in the URL. -To simplify things, in Python, list_services() API can be called on ModelVersion object:+To simplify things, in Python, the list_services() API can be called on a ModelVersion object:  ```python@@ -166,5 +166,5 @@ ``` -It outputs both public endpoint (`inference_endpoint`) and internal endpoint (`internal_endpoint`).+It outputs both the public endpoint (`inference_endpoint`) and the internal endpoint (`internal_endpoint`).  <a id="label-real-time-inference-authentication"></a>@@ -173,9 +173,8 @@  Snowflake supports multiple authentication protocols.-Simplest of all is to use [Programmatic Access Tokens (PAT)](/user-guide/programmatic-access-tokens)-where token can be passed simply to the request header as <code className="samp">Authorization: Snowflake Token="<em>your_pat_token</em>"</code>--All authorization failures such as an incorrect token or lack of network route to the service result in a 404 error. As of today, there is-no way to distinguish authentication errors from invalid URLs.+The simplest of all is to use [Programmatic Access Tokens (PAT)](/user-guide/programmatic-access-tokens)+where the token can be passed simply to the request header as <code className="samp">Authorization: Snowflake Token="<em>your_pat_token</em>"</code>++All authorization failures such as an incorrect token or lack of network route to the service result in a 404 error. There is no way to distinguish authentication errors from invalid URLs.  <a id="label-real-time-inference-authorization"></a>@@ -190,8 +189,8 @@ ## Request body (or protocol or data format) -Snowflake supports two types of data formats for REST requests. They are inspired by Pandas dataframe particularly because they are well-known in the industry and verifiable by customers using simple Python scripts with a Pandas Dataframe.--**Method-to-URL Mapping:** When constructing your request URL, note that underscores (`_`) in your model's method names are+Snowflake supports two types of data formats for REST requests. They are inspired by the Pandas DataFrame, particularly because DataFrames are well+known in the industry and verifiable by customers using simple Python scripts with a Pandas DataFrame.++**Method-to-URL mapping:** When constructing your request URL, note that underscores (`_`) in your model's method names are automatically replaced by dashes (`-`). For example, if your model method is `predict_proba`, the endpoint URL path becomes `/predict-proba`.@@ -229,5 +228,5 @@ - `data`: A list of rows, where each row is a list of values aligned with the columns. -Example `cURL` Request:+Example `cURL` request:  ```bash@@ -256,5 +255,5 @@ The request body wraps this list under the `dataframe_records` key: -Example `cURL` Request:+Example `cURL` request:  ```bash@@ -522,5 +521,5 @@ <a id="label-real-time-inference-next-steps"></a> -## Next Steps+## Next steps  Explore these detailed guides to optimize and manage your inference services: 

--- ahttps://docs.snowflake.com/en/user-guide/cortex-code-agent-sdk/cortex-code-agent-sdk+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code-agent-sdk/cortex-code-agent-sdk@@ -468,16 +468,32 @@     </tr>     <tr>+      <td>Claude Opus 5</td>+      <td>`claude-opus-5`</td>+    </tr>+    <tr>+      <td>Claude Opus 4.8</td>+      <td>`claude-opus-4-8`</td>+    </tr>+    <tr>+      <td>Claude Opus 4.7</td>+      <td>`claude-opus-4-7`</td>+    </tr>+    <tr>       <td>Claude Opus 4.6</td>       <td>`claude-opus-4-6`</td>     </tr>     <tr>+      <td>Claude Opus 4.5</td>+      <td>`claude-opus-4-5`</td>+    </tr>+    <tr>+      <td>Claude Sonnet 5</td>+      <td>`claude-sonnet-5`</td>+    </tr>+    <tr>       <td>Claude Sonnet 4.6</td>       <td>`claude-sonnet-4-6`</td>     </tr>     <tr>-      <td>Claude Opus 4.5</td>-      <td>`claude-opus-4-5`</td>-    </tr>-    <tr>       <td>Claude Sonnet 4.5</td>       <td>`claude-sonnet-4-5`</td>@@ -486,4 +502,12 @@       <td>Claude Sonnet 4.0</td>       <td>`claude-4-sonnet`</td>+    </tr>+    <tr>+      <td>OpenAI GPT 5.5 (Preview)</td>+      <td>`openai-gpt-5.5`</td>+    </tr>+    <tr>+      <td>OpenAI GPT 5.4</td>+      <td>`openai-gpt-5.4`</td>     </tr>     <tr> 

--- ahttps://docs.snowflake.com/en/migrations/aim-for-datawarehouses/code-conversion/function-references/oracle+++ bhttps://docs.snowflake.com/en/migrations/aim-for-datawarehouses/code-conversion/function-references/oracle@@ -87,5 +87,5 @@ ### Definition -This user-defined function (UDF) transforms from Gregorian date to Julian date (The number of days since January 1, 4712 BC.).+This user-defined function (UDF) transforms from Gregorian date to Julian date (the number of days since January 1, 4712 BC).  ```sql@@ -164,5 +164,5 @@ ### Usage example -To review the lines in the file, there are two ways: Downloading the file from the Snowflake CLI or briefly review the information with `SELECT * FROM UTL_FILE.FOPEN_TABLES_LINES;` but only if the file has not been closed.+To review the lines in the file, there are two ways: Downloading the file from the Snowflake CLI or briefly reviewing the information with `SELECT * FROM UTL_FILE.FOPEN_TABLES_LINES;` but only if the file has not been closed.  Input:@@ -233,5 +233,5 @@ ### Usage example -The `UTL_FILE.FOPEN_UDF` allows to open a .csv file. To access the file it is required to create a `stage` for the file and use the Snowflake CLI to upload it.+The `UTL_FILE.FOPEN_UDF` allows you to open a .csv file. To access the file it is required to create a `stage` for the file and use the Snowflake CLI to upload it.  Input:@@ -364,5 +364,5 @@ The timestamp number that is going to be added with the second float parameter. -`SECOND_PARAM` DATE+`SECOND_PARAM` TIMESTAMP  The float number to be added with the timestamp in the first parameter.@@ -537,5 +537,5 @@ `FIRST_PARAM` DATE -The date over the subtraction is done.+The date on which the subtraction is performed.  `SECOND_PARAM` TIMESTAMP@@ -884,5 +884,5 @@ ### Definition -This user-defined function (UDF) is+This user-defined function (UDF) is used to support the Oracle `REGEXP_LIKE` functionality with a match parameter for case sensitivity.  ```sql@@ -903,9 +903,9 @@ MATCHPARAM STRING -The match parameter that will determine whether the case-sensitive or not.--### Returns--Returns+The match parameter that will determine whether the match is case-sensitive or not.++### Returns++Returns a boolean expression. True if the pattern matches the string; otherwise, false.  ### Usage example@@ -1115,5 +1115,5 @@ ### Definition -This user-defined function (UDF) is used to pen a cursor without bindings.+This user-defined function (UDF) is used to open a cursor without bindings.  ```sql@@ -1410,5 +1410,5 @@ `DATESTR` STRING -The date as a `string` to be formatted. The format should be '`YYYY-MM-DD"T"HH24:MI:SS.FF'` e.g. `'2024-01-25T23:25:11.120'`.+The date as a `string` to be formatted. The format should be `'YYYY-MM-DD"T"HH24:MI:SS.FF'` e.g. `'2024-01-25T23:25:11.120'`.  Please review the following information about formatting [here](https://docs.snowflake.com/en/sql-reference/date-time-input-output#timestamp-formats).@@ -1562,5 +1562,5 @@ ### Definition -This user-defined function (UDF) transforms from date to oracle RR datetime format date+This user-defined function (UDF) transforms from date to Oracle RR datetime format  ```sql@@ -1602,5 +1602,5 @@ ```sql :force:-PUBLIC.CONVERT_DATE_WITH_RR_FORMAT_UDF(TO_DATE('17-NOV-30','DD-MON-YY')) as A from DUAL;+PUBLIC.DATE_TO_RR_FORMAT_UDF(TO_DATE('17-NOV-30','DD-MON-YY')) as A from DUAL; ``` @@ -2094,5 +2094,5 @@ ### Usage example -The `UTL_FILE.FOPEN_UDF` allows to open a .csv file. To access the file it is required to create a `stage` for the file and use the Snowflake CLI to upload it.+The `UTL_FILE.FOPEN_UDF` allows you to open a .csv file. To access the file it is required to create a `stage` for the file and use the Snowflake CLI to upload it.  Input: 

--- ahttps://docs.snowflake.com/en/sql-reference/sql/show-application-services+++ bhttps://docs.snowflake.com/en/sql-reference/sql/show-application-services@@ -133,12 +133,4 @@     </tr>     <tr>-      <td>`execute_as_role`</td>-      <td>-        For a service in a personal database, the role that owner's rights-        queries run as, set with `EXECUTE_AS_ROLE`. Empty for a service in a-        standard database.-      </td>-    </tr>-    <tr>       <td>`created_by`</td>       <td>Name of the user who created the service.</td>@@ -191,4 +183,28 @@       </td>     </tr>+    <tr>+      <td>`execute_as_role`</td>+      <td>+        For a service in a personal database, the role that owner's rights+        queries run as, set with `EXECUTE_AS_ROLE`. Empty for a service in a+        standard database.+      </td>+    </tr>+    <tr>+      <td>`min_instances`</td>+      <td>+        Minimum instance count. `1` when not set.+      </td>+    </tr>+    <tr>+      <td>`max_instances`</td>+      <td>+        Maximum instance count. Matches `MIN_INSTANCES` when not set.+      </td>+    </tr>+    <tr>+      <td>`current_instances`</td>+      <td>Current number of running instances.</td>+    </tr>   </tbody>  

--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/manifest-reference+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/manifest-reference@@ -107,5 +107,5 @@ This field includes a single `databases` field and an optional `required_databases` field: -- `shared_content.databases` (List, required): A list of named database instances and the underlying objects to share.+- `shared_content.databases` (list, required): A list of named database instances and the underlying objects to share.  <a id="label-dsna-manifest-databases"></a>@@ -144,10 +144,10 @@ Each named schema supports the following name value pairs: -- `tables` (list, <a class="footnote-reference brackets" href="#citation-OneOfRequired" role="doc-noteref"><span class="fn-bracket">[</span>OneOfRequired<span class="fn-bracket">]</span></a>): A list of named tables, which can include [dynamic tables](/user-guide/dynamic-tables/overview) and [Apache Iceberg tables](/user-guide/tables-iceberg).-- `views` (list, <a class="footnote-reference brackets" href="#citation-OneOfRequired" role="doc-noteref"><span class="fn-bracket">[</span>OneOfRequired<span class="fn-bracket">]</span></a>): A list of named views.-- `semantic_views` (list, <a class="footnote-reference brackets" href="#citation-OneOfRequired" role="doc-noteref"><span class="fn-bracket">[</span>OneOfRequired<span class="fn-bracket">]</span></a>): A list of named semantic views.-- `functions` (list, <a class="footnote-reference brackets" href="#citation-OneOfRequired" role="doc-noteref"><span class="fn-bracket">[</span>OneOfRequired<span class="fn-bracket">]</span></a>): A list of named user-defined functions (UDFs).-- `procedures` (list, <a class="footnote-reference brackets" href="#citation-OneOfRequired" role="doc-noteref"><span class="fn-bracket">[</span>OneOfRequired<span class="fn-bracket">]</span></a>): A list of named stored procedures.-- `cortex_agents` (list, <a class="footnote-reference brackets" href="#citation-OneOfRequired" role="doc-noteref"><span class="fn-bracket">[</span>OneOfRequired<span class="fn-bracket">]</span></a>): A list of named [Cortex Agents](/user-guide/snowflake-cortex/cortex-agents).+- `tables` (list, <a class="footnote-reference brackets" href="#citation-oneofrequired" role="doc-noteref"><span class="fn-bracket">[</span>OneOfRequired<span class="fn-bracket">]</span></a>): A list of named tables, which can include [dynamic tables](/user-guide/dynamic-tables/overview) and [Apache Iceberg tables](/user-guide/tables-iceberg).+- `views` (list, <a class="footnote-reference brackets" href="#citation-oneofrequired" role="doc-noteref"><span class="fn-bracket">[</span>OneOfRequired<span class="fn-bracket">]</span></a>): A list of named views.+- `semantic_views` (list, <a class="footnote-reference brackets" href="#citation-oneofrequired" role="doc-noteref"><span class="fn-bracket">[</span>OneOfRequired<span class="fn-bracket">]</span></a>): A list of named semantic views.+- `functions` (list, <a class="footnote-reference brackets" href="#citation-oneofrequired" role="doc-noteref"><span class="fn-bracket">[</span>OneOfRequired<span class="fn-bracket">]</span></a>): A list of named user-defined functions (UDFs).+- `procedures` (list, <a class="footnote-reference brackets" href="#citation-oneofrequired" role="doc-noteref"><span class="fn-bracket">[</span>OneOfRequired<span class="fn-bracket">]</span></a>): A list of named stored procedures.+- `cortex_agents` (list, <a class="footnote-reference brackets" href="#citation-oneofrequired" role="doc-noteref"><span class="fn-bracket">[</span>OneOfRequired<span class="fn-bracket">]</span></a>): A list of named [Cortex Agents](/user-guide/snowflake-cortex/cortex-agents). - `roles` (list, optional): A list of app roles that the objects in the schema can use, for example, `[SALES, MARKETING]`. When this field is empty (`[]`) or omitted, then only app owners and roles with [granted IMPORTED PRIVILEGES](#label-dsna-share-access-to-all-data) receive access. The included roles must be defined in the [top-level roles field](#label-dsna-manifest-roles-top). @@ -164,5 +164,5 @@ #### `tables.{named table}` field -Each named standard table, [dynamic table](/user-guide/dynamic-tables/overview), and [Apache Iceberg table](/user-guide/tables-iceberg) (List, required <a class="footnote-reference brackets" href="#citation-OneOfRequired" role="doc-noteref"><span class="fn-bracket">[</span>OneOfRequired<span class="fn-bracket">]</span></a> ) supports the following name value pair:+Each named standard table, [dynamic table](/user-guide/dynamic-tables/overview), and [Apache Iceberg table](/user-guide/tables-iceberg) (list, required <a class="footnote-reference brackets" href="#citation-oneofrequired" role="doc-noteref"><span class="fn-bracket">[</span>OneOfRequired<span class="fn-bracket">]</span></a> ) supports the following name value pair:  - `roles` (list, optional): A list of app roles that can access the table; for example, `[SALES]`. When this field is empty (`[]`) or omitted, then only app owners and roles with [granted IMPORTED PRIVILEGES](#label-dsna-share-access-to-all-data) receive access. The included roles must be defined in the [top-level roles field](#label-dsna-manifest-roles-top) and included in the [\{named schema\}.roles](#label-dsna-manifest-schemas) field.@@ -176,5 +176,5 @@ #### `views.{named view}` field -Each named view (List, required <a class="footnote-reference brackets" href="#citation-OneOfRequired" role="doc-noteref"><span class="fn-bracket">[</span>OneOfRequired<span class="fn-bracket">]</span></a> ): supports the following name value pair:+Each named view (list, required <a class="footnote-reference brackets" href="#citation-oneofrequired" role="doc-noteref"><span class="fn-bracket">[</span>OneOfRequired<span class="fn-bracket">]</span></a>) supports the following name value pair:  - `roles` (list, optional): A list of app roles that can access the view; for example, `[MARKETING]`. When this field is empty (`[]`) or omitted, then only app owners and roles with [granted IMPORTED PRIVILEGES](#label-dsna-share-access-to-all-data) receive access. The included roles must be defined in the [top-level roles field](#label-dsna-manifest-roles-top) and included in the [\{named schema\}.roles](#label-dsna-manifest-schemas) field.@@ -186,5 +186,5 @@ #### `semantic_views.{named semantic view}` field -Each named semantic view (List, required <a class="footnote-reference brackets" href="#citation-OneOfRequired" role="doc-noteref"><span class="fn-bracket">[</span>OneOfRequired<span class="fn-bracket">]</span></a> ): supports the following name value pair:+Each named semantic view (list, required <a class="footnote-reference brackets" href="#citation-oneofrequired" role="doc-noteref"><span class="fn-bracket">[</span>OneOfRequired<span class="fn-bracket">]</span></a>) supports the following name value pair:  - `roles` (list, optional): A list of app roles that can access the semantic view; for example, `[SALES]`. Note that, when sharing a semantic view, its referenced tables or views must be shared as well. When this field is empty (`[]`) or omitted, then only app owners and roles with [granted IMPORTED PRIVILEGES](#label-dsna-share-access-to-all-data) receive access. The included roles must be defined in the [top-level roles field](#label-dsna-manifest-roles-top) and included in the [\{named schema\}.roles](#label-dsna-manifest-schemas) field.@@ -194,5 +194,5 @@ #### `functions.{named function}` field -Each named function (List, required <a class="footnote-reference brackets" href="#citation-OneOfRequired" role="doc-noteref"><span class="fn-bracket">[</span>OneOfRequired<span class="fn-bracket">]</span></a> ): supports the following name value pair:+Each named function (list, required <a class="footnote-reference brackets" href="#citation-oneofrequired" role="doc-noteref"><span class="fn-bracket">... (truncated) 

差分が長いため、途中まで表示しています。

--- ahttps://docs.snowflake.com/en/migrations/snowconvert-docs/general/release-notes/release-notes/README+++ bhttps://docs.snowflake.com/en/migrations/snowconvert-docs/general/release-notes/release-notes/README@@ -4008,5 +4008,5 @@ ### IBM DB2 Stored Procedures & User-Defined Functions Support -SnowConvert AI now supports the conversion of DB2 stored procedures to Snowflake equivalents, enabling seamless migration of procedural code. This feature includes support for variable operations, and control flow statements. Also, DB2 user-defined functions will be converted to Snowflake Scripting UDFs when possible.+SnowConvert AI now supports the conversion of DB2 stored procedures to Snowflake equivalents, enabling seamless migration of procedural code. This feature includes support for variable operations and control flow statements. Also, DB2 user-defined functions will be converted to Snowflake Scripting UDFs when possible.  ### New Features 🚀@@ -4549,5 +4549,5 @@ ### Fixes - Fixed issue with retrieving access codes from SnowConvert due to certificate handling problems.-- Added Data Validation manual execution instruction and scripts.+- Added Data Validation manual execution instructions and scripts.  ## Version 1.15.1 (Aug 6, 2025)@@ -4635,24 +4635,24 @@  * **General support**:-  * Transformation for ```SELECT INTO``` variables inside stored procedures.-  * Transformation for ```CASE``` statements without ELSE clauses.-  * Transformation of ```RETURN``` statement in Redshift.-  * Support of ```RAISE``` for logging, warnings, and exceptions.+  * Transformation for `SELECT INTO` variables inside stored procedures.+  * Transformation for `CASE` statements without ELSE clauses.+  * Transformation of `RETURN` statement in Redshift.+  * Support of `RAISE` for logging, warnings, and exceptions. * **Variable Binding**:   * Support for binding variables in stored procedures.   * Handling positional arguments for binding variables.-  * Variable bindings in the ```OPEN cursor``` statement.+  * Variable bindings in the `OPEN cursor` statement. * **Transaction Support**:-  * Initial support for ```COMMIT```, ```ROLLBACK```, and ```TRUNCATE``` statements.+  * Initial support for `COMMIT`, `ROLLBACK`, and `TRUNCATE` statements. * **Cursor Operations**:-  * Support for the ```FETCH``` statement.-  * Transformation for ```refcursor variable declaration```.+  * Support for the `FETCH` statement.+  * Transformation for `refcursor variable declaration`. * **DML Operations**:-  * Transformations for ```INSERT```, ```UPDATE```, ```MERGE```, ```SELECT INTO``` statements.-* ```**Control Flow Statements**```:+  * Transformations for `INSERT`, `UPDATE`, `MERGE`, `SELECT INTO` statements.+* **Control Flow Statements**:   * Support for basic control flows statements.   * Transformations of Labels Stats against loops. * **DDL Operations**:-  * Support for ```CREATE TABLE AS``` statement.+  * Support for `CREATE TABLE AS` statement.  ### Breaking Changes ⛓️‍💥@@ -4708,5 +4708,5 @@ * **Free** access for anyone with a corporate email. * **Redshift** conversion is now supported under preview.-* Remove assessment step. Assessment and conversion are now completed in only one step.+* Removed assessment step. Assessment and conversion are now completed in only one step. * Introduction of the new Code Completeness Score and Code Unit Methodology. * Improved messages like Functional Difference Messages (FDMs), Performance Reviews (PRFs) and EWIs (error, warnings, and issues).@@ -4743,5 +4743,5 @@   * TERA mode without COLLATE. * Support parsing of  GENERATED TIMECOLUMN column option.-* Support parsing of TD\_NORMALIZE\_MEET function.\+* Support parsing of TD\_NORMALIZE\_MEET function.  #### Fixed 

--- ahttps://docs.snowflake.com/en/migrations/sma-docs/use-cases/sma-checkpoints-walkthrough/snowpark-checkpoints-execution-guide/validation+++ bhttps://docs.snowflake.com/en/migrations/sma-docs/use-cases/sma-checkpoints-walkthrough/snowpark-checkpoints-execution-guide/validation@@ -1,11 +1,2 @@-<dl className="field-list">-<dt>description<span className="colon">:</span></dt>-<dd>--This page outlines the step-by-step process for the validation procedure.--</dd>-</dl>- # Snowpark Migration Accelerator: Validation @@ -20,25 +11,25 @@ 3. Generate checkpoints using the `checkpoints.json` file. -To generate checkpoints you can do one of the following actions:+   To generate checkpoints you can do one of the following actions: -- Generate them by accepting the suggested message:+   - Generate them by accepting the suggested message: -![Load found checkpoints message](/static/images/migrations/sma-assets/image(575).png)+   ![Load found checkpoints message](/static/images/migrations/sma-assets/image(575).png) -- Execute "Snowflake: Load All Checkpoints command"+   - Execute the "Snowflake: Load All Checkpoints" command -![Load All Checkpoints Command](/static/images/migrations/sma-assets/image(576).png)+   ![Load All Checkpoints Command](/static/images/migrations/sma-assets/image(576).png) -Once all checkpoints are loaded, your files should appear as follows:+   Once all checkpoints are loaded, your files should appear as follows: -![File with checkpoints](/static/images/migrations/sma-assets/image(583).png)+   ![File with checkpoints](/static/images/migrations/sma-assets/image(583).png) -1. Run the Python file to execute the checkpoints validation process.+4. Run the Python file to execute the checkpoints validation process. -When running a python file that contains validation checkpoints, the validation results are going to be shown in the copied "snowpark-checkpoints-output" folder as "checkpoints_validation_results.json":+When running a Python file that contains validation checkpoints, the validation results will be shown in the copied "snowpark-checkpoints-output" folder as "checkpoints_validation_results.json":  ![Results](/static/images/migrations/sma-assets/image(584).png) -The "checkpoints_validation_results.json" contains the unified results of the collection process+The "checkpoints_validation_results.json" contains the unified results of the validation process.  ```json 

--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents@@ -9,5 +9,5 @@ Agents bring your structured and unstructured data together in a single governed workflow. They generate SQL over structured data using %cortex-analyst% semantic views and use Cortex Search to retrieve insights from unstructured sources, then reason over the combined results. You can extend what an agent can do with several types of tools: -- A built-in code execution tool (Private Preview) that, when enabled, runs Python in a secure, isolated sandbox to process data and perform calculations.+- A built-in [code execution tool](/user-guide/snowflake-cortex/cortex-agents-code-execution-tool) that, when enabled, runs Python in a secure, isolated sandbox to process data and perform calculations. - A Data to Chart tool that generates visualizations from data. - Custom tools built from stored procedures and user-defined functions (UDFs) to call backend systems or implement your own business logic.@@ -21,5 +21,5 @@  1. **Plan**: The agent parses the request and decides how to answer it. It can disambiguate a vague question (for example, "Tell me about Acme Supplies" might refer to products, location, or sales personnel), split a complex request into subtasks (for example, "What are the differences between contract terms for Acme Supplies and Acme Stationery?"), and choose which tool to use for each part.-2. **Use tools**: The agent calls the tools it selected, such as %cortex-analyst% for structured data, Cortex Search for unstructured data, or the code execution tool to process results.+2. **Use tools**: The agent calls the tools it selected, such as %cortex-analyst% for structured data, Cortex Search for unstructured data, or the [code execution tool](/user-guide/snowflake-cortex/cortex-agents-code-execution-tool) to process results. 3. **Reflect and respond**: The agent evaluates the results from each tool to decide what to do next, whether that's asking a clarifying question, calling another tool, or generating a final response. This loop lets the agent handle complex, multi-step questions. @@ -45,11 +45,11 @@ Cortex Agents is built around the following concepts: -| Concept           | Description                                                                                                                                                              |-| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |-| **Agent**         | A schema-level object that bundles the agent's model, tools, orchestration settings, and instructions. Create it once and reuse it across interactions and applications. |-| **Tools**         | How the agent acts on your data and systems: %cortex-analyst%, Cortex Search, code execution, custom tools, and more. See [Tools](#label-cortex-agents-tools).           |-| **Orchestration** | The LLM-driven plan, use tools, reflect loop the agent runs to answer a request. You shape it with natural-language planning and response instructions.                  |-| **Thread**        | Persisted conversation context across turns, so your client application doesn't manage state. Create a thread object and reference its ID in agent interactions.         |-| **Run**           | A single request to an agent through the `agent:run` API. The agent emits events throughout the run that surface its reasoning, tool calls, and reflections.             |+| Concept           | Description                                                                                                                                                                                                                      |+| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |+| **Agent**         | A schema-level object that bundles the agent's model, tools, orchestration settings, and instructions. Create it once and reuse it across interactions and applications.                                                         |+| **Tools**         | How the agent acts on your data and systems: %cortex-analyst%, Cortex Search, [code execution](/user-guide/snowflake-cortex/cortex-agents-code-execution-tool), custom tools, and more. See [Tools](#label-cortex-agents-tools). |+| **Orchestration** | The LLM-driven plan, use tools, reflect loop the agent runs to answer a request. You shape it with natural-language planning and response instructions.                                                                          |+| **Thread**        | Persisted conversation context across turns, so your client application doesn't manage state. Create a thread object and reference its ID in agent interactions.                                                                 |+| **Run**           | A single request to an agent through the `agent:run` API. The agent emits events throughout the run that surface its reasoning, tool calls, and reflections.                                                                     |  <a id="label-cortex-agents-models"></a>@@ -64,6 +64,6 @@ | Provider  | Model                      | Status         | Cross Cloud (any region) | AWS US | AWS US Gov | AWS EU | AWS APJ | AWS AU | Azure US | Azure EU | Google Cloud US | | --------- | -------------------------- | -------------- | ------------------------ | ------ | ---------- | ------ | ------- | ------ | -------- | -------- | --------------- |-| Anthropic | `claude-opus-5`            | Public preview | %cm%                     | %cm%   |            | %cm%   | %cm%    | %cm%   |          |          |                 |-| Anthropic | `claude-opus-4-8`          | Public preview | %cm%                     | %cm%   |            | %cm%   | %cm%    | %cm%   |          |          |                 |+| Anthropic | `claude-opus-5`            | GA             | %cm%                     | %cm%   |            | %cm%   | %cm%    | %cm%   |          |          |                 |+| Anthropic | `claude-opus-4-8`          | GA             | %cm%                     | %cm%   |            | %cm%   | %cm%    | %cm%   |          |          |                 | | Anthropic | `claude-opus-4-7`          | GA             | %cm%                     | %cm%   |            | %cm%   | %cm%    | %cm%   |          |          |                 | | Anthropic | `claude-opus-4-6`          | GA             | %cm%                     | %cm%   |            | %cm%   | %cm%    | %cm%   |          |          |                 |@@ -135,6 +135,6 @@     </tr>     <tr>-      <td>Code execution (Private Preview)</td>-      <td>Runs Python in a secure, isolated sandbox to process data and perform calculations. See [](/user-guide/snowflake-cortex/cortex-agents-code-execution-tool).</td>+      <td>[Code execution](/user-guide/snowflake-cortex/cortex-agents-code-execution-tool)</td>+      <td>Runs Python in a secure, isolated sandbox to process data and perform calculations.</td>     </tr>     <tr>@@ -168,5 +168,5 @@ ## Access control and authentication -Calling an agent requires the SNOWFLAKE.CORTEX_USER or SNOWFLAKE.CORTEX_AGENT_USER database role, privileges on the agent object, and privileges on the objects used by the agent's tools. Cortex Agents determines session permissions from the querying user's default role. Requests to the Cortex Agents API must include an authorization token.+Calling an agent requires the SNOWFLAKE.CORTEX_USER or SNOWFLAKE.CORTEX_AGENT_USER database role, privileges on the agent object, and privileges on the objects used by the agent's tools. If the user's role is missing privileges on a tool, ... (truncated) 

差分が長いため、途中まで表示しています。

--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/connecting/configure-connections+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/connecting/configure-connections@@ -45,5 +45,5 @@ ``` -For MacOS and Linux systems, %sf-cli% requires the `config.toml` file to limit its file permissions to read and write for the file owner only. To set the file required file permissions execute the following commands:+For macOS and Linux systems, %sf-cli% requires the `config.toml` file to limit its file permissions to read and write for the file owner only. To set the required file permissions, execute the following commands:  ```snowcli@@ -113,5 +113,5 @@ ``` -If the command finishes with an error, such as if the `--private_key_file` option references a non-existing file, the connection is not saved in the `config.toml` configuration file.+If the command finishes with an error, such as if the `--private-key-file` option references a non-existing file, the connection is not saved in the `config.toml` configuration file.  By default, the `snow connection add` command prompts for optional parameters if they are not specified on the command line. If you want to add connections without specifying some optional parameter, like `account`, and skip the interactive prompts, you can use the `--no-interactive` option, as shown:@@ -178,5 +178,5 @@  ```snowcli-snow connection test -c myconnection2 --enable-diag --diag-log-path $(HOME)/report+snow connection test -c myconnection2 --enable-diag --diag-log-path $HOME/report ``` @@ -454,8 +454,8 @@ ### Use a private key file for authentication -To use private key file for authentication, your connection configuration requires you to set the `authenticator`-parameter to `SNOWFLAKE_JWT` and provide path to file with your private key similar to the following:--- Specify the `--private_key-file` option in the `snow connection add` command, as shown:+To use a private key file for authentication, your connection configuration requires you to set the `authenticator`+parameter to `SNOWFLAKE_JWT` and provide the path to the file with your private key similar to the following:++- Specify the `--private-key-file` option in the `snow connection add` command, as shown:   ```snowcli   snow connection add \@@ -492,5 +492,5 @@ ### Use OAuth authentication -To use connect using OAuth, you can do either of the following:+To connect using OAuth, you can do either of the following:  - Specify the `--token-file-path` option in the `snow connection add` command, as shown:@@ -556,5 +556,5 @@  -   If you want use the passcode in the password for authentication, after executing the first `snow` command, you can no longer provide the passcode as long as the token in valid. You must do the following:+   If you want to use the passcode in the password for authentication, after executing the first `snow` command, you can no longer provide the passcode as long as the token is valid. You must do the following:     - Remove the passcode from the password.@@ -587,5 +587,5 @@ You can use your browser to authenticate your %sf-cli% connection with any SAML 2.0 compliant identity provider (IdP), such as Okta or Active Directory Federation Services. -The `externalbrowser` authenticator is only supported in terminal windows that have web browser access. For example, a terminal window on a remote machine accessed through a SSH (Secure Shell) session might require additional setup to open a web browser.+The `externalbrowser` authenticator is only supported in terminal windows that have web browser access. For example, a terminal window on a remote machine accessed through an SSH (Secure Shell) session might require additional setup to open a web browser.  If you don't have access to a web browser, but your IdP is Okta, you can use native Okta by setting the authenticator to `https://<okta_account_name>.okta.com`.@@ -612,5 +612,5 @@ Programmatic Access Token (PAT) is a Snowflake-specific authentication method. The feature must be enabled for the account before usage (see the [](#label-pat-prerequisites) for more information). Authentication with PAT doesn't involve any human interaction. -To use PAT with the connection, set `authenticator` to `PROGRAMMATIC_ACCESS_TOKEN` and `token_file_path` to point the file with token, as shown:+To use PAT with the connection, set `authenticator` to `PROGRAMMATIC_ACCESS_TOKEN` and `token_file_path` to point to the file with the token, as shown:  ```toml@@ -665,6 +665,6 @@      snow connection add \       --connection-name my_wif_conn \-      --account <account>-      --authenticatior WORKLOAD_IDENTITY \+      --account <account> \+      --authenticator WORKLOAD_IDENTITY \       --workload-identity-provider <provider type>      ```@@ -683,5 +683,5 @@ </blockquote> -When using OIDC as a provider, you need to retrieve the token from your environment and provide it to cli. You can provide retrieved token via+When using OIDC as a provider, you need to retrieve the token from your environment and provide it to the CLI. You can provide the retrieved token via  - `--token` parameter 

--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-warehouse+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-warehouse@@ -14,5 +14,5 @@ <dd> -[](/sql-reference/sql/alter-warehouse) , [](/sql-reference/sql/desc-warehouse) , [](/sql-reference/sql/drop-warehouse) , [](/sql-reference/sql/show-warehouses)+[](/sql-reference/sql/alter-warehouse), [](/sql-reference/sql/desc-warehouse), [](/sql-reference/sql/drop-warehouse), [](/sql-reference/sql/show-warehouses)  </dd>@@ -195,9 +195,9 @@     <tr>       <td>`XXLARGE`</td>-      <td>`X2LARGE` , `'2X-LARGE'`</td>+      <td>`X2LARGE`, `'2X-LARGE'`</td>     </tr>     <tr>       <td>`XXXLARGE`</td>-      <td>`X3LARGE` , `'3X-LARGE'`</td>+      <td>`X3LARGE`, `'3X-LARGE'`</td>     </tr>     <tr>@@ -272,5 +272,5 @@ </dl> -`RESOURCE_CONSTRAINT = { STANDARD_GEN_1 | STANDARD_GEN_2 | MEMORY_1X| MEMORY_1X_x86 | MEMORY_16X | MEMORY_16X_x86 | MEMORY_64X | MEMORY_64X_x86 }`+`RESOURCE_CONSTRAINT = { STANDARD_GEN_1 | STANDARD_GEN_2 | MEMORY_1X | MEMORY_1X_x86 | MEMORY_16X | MEMORY_16X_x86 | MEMORY_64X | MEMORY_64X_x86 }`  <blockquote>@@ -479,5 +479,5 @@  - `STANDARD`: Minimizes queuing by starting clusters.-- `ECONOMY`: Conserves credits by favoring keeping running clusters fully-loaded.+- `ECONOMY`: Conserves credits by favoring keeping running clusters fully loaded.  For a more detailed description, see [](#label-mcw-scaling-policies).@@ -504,8 +504,8 @@ Any integer `0` or greater, or `NULL`: -- The background process that suspends a warehouse runs approximately every 30 seconds and therefore, the setting for+- The background process that suspends a warehouse runs approximately every 30 seconds and, therefore, the setting for   this property isn't intended for enabling precise control over warehouse suspension. - Setting a value less than 30, or a value that isn't a multiple of 30, is allowed but might not result in the expected-  behavior due to the 30 second poll interval for warehouse suspension.+  behavior due to the 30-second poll interval for warehouse suspension. - Setting a `0` or `NULL` value means the warehouse never suspends. @@ -692,5 +692,5 @@ <dd> -Object parameter that specifies the concurrency level for SQL statements (i.e. queries and DML) executed by a warehouse cluster.+Object parameter that specifies the concurrency level for SQL statements (that is, queries and DML) executed by a warehouse cluster.  For a detailed description of this parameter, see [](#label-max-concurrency-level).@@ -700,5 +700,5 @@ <dd> -Object parameter that specifies the time, in seconds, a SQL statement (query, DDL, DML, etc.) can be queued on a warehouse before it is+Object parameter that specifies the time, in seconds, a SQL statement (query, DDL, DML, and so on) can be queued on a warehouse before it is canceled by the system. @@ -709,5 +709,5 @@ <dd> -Object parameter that specifies the time, in seconds, after which a running SQL statement (query, DDL, DML, etc.) is canceled by the system.+Object parameter that specifies the time, in seconds, after which a running SQL statement (query, DDL, DML, and so on) is canceled by the system.  For a detailed description of this parameter, see [](#label-statement-timeout-in-seconds).@@ -814,5 +814,5 @@ - Existing policies or tags can't be altered by a CREATE OR ALTER WAREHOUSE statement and remain unchanged. -## Billing and Pricing+## Billing and pricing  For information on Snowpark-optimized warehouse credit consumption, see@@ -874,5 +874,5 @@   WAREHOUSE_TYPE = 'SNOWPARK-OPTIMIZED'   WAREHOUSE_SIZE = 'X-LARGE'-  RESOURCE_CONSTRAINT = 'MEMORY_16X_X86'+  RESOURCE_CONSTRAINT = 'MEMORY_16X_x86'   AUTO_RESUME = TRUE   COMMENT = 'Snowpark warehouse for ingestion';@@ -881,5 +881,5 @@   WAREHOUSE_TYPE = 'SNOWPARK-OPTIMIZED'   WAREHOUSE_SIZE = 'X-LARGE'-  RESOURCE_CONSTRAINT = 'MEMORY_16X_X86'+  RESOURCE_CONSTRAINT = 'MEMORY_16X_x86'   AUTO_RESUME = FALSE   COMMENT = 'Snowpark warehouse for ingestion (disabled for auto-resume)'; 

--- ahttps://docs.snowflake.com/en/developer-guide/native-apps/connector-sdk/getting_started+++ bhttps://docs.snowflake.com/en/developer-guide/native-apps/connector-sdk/getting_started@@ -31,10 +31,10 @@  This directory contains the actual %snsdkforconn% source code and tests.-Because of the nature of the native app inside Snowflake source code is not only Java code,-but also bundled SQL code with database objects definitions.+Because of the nature of the native app inside Snowflake, source code is not only Java code,+but also bundled SQL code with database object definitions. -The Java code is inside `src/main` directory as for any regular Java library. The same for the unit tests located inside `src/test`.+The Java code is inside the `src/main` directory as for any regular Java library. Unit tests are located inside `src/test`. Additionally, inside `src/` directory you can find `intTest` and `appTest` directories.-Those are respectively integration and application tests. Both of those test types require connection to a Snowflake account.+Those are respectively integration and application tests. Both of those test types require a connection to a Snowflake account. The former ones test the SDK components using standalone database objects, while the latter deploy an actual application and run tests using it. @@ -44,5 +44,5 @@ - `connectors-native-sdk-test` -This directory contains helper library designed to enable easier unit testing of the Connector based on the %snsdkforconn%.+This directory contains a helper library designed to enable easier unit testing of the Connector based on the %snsdkforconn%. It provides mock implementations for some of the database objects, specially designed test builders that allow overwriting parts of the code not available for customization and some custom assertions based on the [AssertJ library](https://assertj.github.io/doc/).@@ -52,5 +52,5 @@ Currently, installation and usage of the %snsdkforconn% requires the developer to perform some manual actions. -The %snsdkforconn% library is available via Maven Central+The %snsdkforconn% library is available via Maven Central.  ```text@@ -119,8 +119,8 @@  The %snsdkforconn% is designed to be used with the %naf%. This means that deployment and installation is happening the same way-as it does for any other native app. This mean that first the Application Package needs to be created and all the files need to be uploaded into stage,+as it does for any other native app. This means that first the Application Package needs to be created and all the files need to be uploaded into a stage, recommendation is to create stage inside the Application Package. If the above example script was used then all the required files from the %snsdkforconn% should be already present in the target build directory of the Connector.-This means that its up to the developer to make sure that the custom code of the Connector and any Streamlit files are also there.+This means that it's up to the developer to make sure that the custom code of the Connector and any Streamlit files are also there. For more information check [](/developer-guide/native-apps/creating-app-package). @@ -133,15 +133,15 @@ The %snsdkforconn% provides objects and procedures that handle common use cases for each Connector application. This includes things like configuration, lifecycle, ingestion definition, and so on. To review the full list of features, see the SDK reference.-Some parts of the predefined features can be customized, for more information on that check Stored procedures and handlers customization.+Some parts of the predefined features can be customized. For more information, check Stored procedures and handlers customization.  ## Testing -As mentioned before Connectors Native SDK contains different types of tests.-This includes unit tests, integration tests and so called application tests.+As mentioned before, Connectors Native SDK contains different types of tests.+This includes unit tests, integration tests and so-called application tests. The unit tests use features provided in the aforementioned `connectors-native-sdk-test`. As for integration and application tests they require connection to Snowflake. Connection details can be defined using the `.env/snowflake_credentials` file.-Application tests directory also contains an empty connector application in resource.-That application is deployed during the test suite execution+The application tests directory also contains an empty connector application in resources.+That application is deployed during the test suite execution.  Additional resources: 

--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-search/tutorials/cortex-search-tutorial-2-chat+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-search/tutorials/cortex-search-tutorial-2-chat@@ -27,12 +27,10 @@  You will use a sample dataset hosted on Kaggle for this tutorial.-The Books dataset is a collection of book name, title and descriptions. You can download the dataset from the following link:--The complete dataset can be found on+The Books dataset is a collection of book names, titles, and descriptions. The complete dataset can be found on [Kaggle](https://www.kaggle.com/datasets/elvinrustam/books-dataset/data).  In a non-tutorial setting, you would bring your own data, possibly already in a Snowflake table. -### Creating the database, schema, stage and warehouse+### Creating the database, schema, and warehouse  Run the following SQL code to set up the necessary database, schema, and warehouse:@@ -72,15 +70,15 @@ 4. Select your schema `public`. 5. Select **Stages** and select `books_data_stage`.-6. On the top right, Select the **+ Files** button.+6. On the top right, select the **+ Files** button. 7. Drag and drop files into the UI or select **Browse** to choose a file from the dialog window.-8. Select **Upload** to upload your file, `BooksDatasetClean.csv`+8. Select **Upload** to upload your file, `BooksDatasetClean.csv`. 9. Select the three dots on the right of the file and select **Load into table**. 10. Name the table `BOOKS_DATASET_RAW` and select **Next**.-    <img src="/static/images/cortex-search/basic_chatbot_tutorial_add_data.png" alt="" style={{width: "600"}} />+    <img src="/static/images/cortex-search/basic_chatbot_tutorial_add_data.png" alt="" style={{width: "600px"}} />  11. In the left panel of the load data dialog, choose **First line contains header** from the **Header** menu. 12. Then select **Load**. -## Step 3: Build the Chunks Table+## Step 3: Build the chunks table  Retrieval accuracy with Cortex Search tends to be higher when documents are shorter.@@ -133,5 +131,5 @@ ## Step 5: Create a Streamlit app -You can query the service with Python SDK (using the `snowflake` Python package). This tutorial+You can query the service with the Python SDK (using the `snowflake` Python package). This tutorial demonstrates using the Python SDK in a %sis% application. @@ -301,5 +299,5 @@     prompt = f"""         [INST]-        Based on the chat history below and the question, generate a query that extend the question+        Based on the chat history below and the question, generate a query that extends the question         with the chat history provided. The query should be in natural language.         Answer with only the query. Do not add any explanation.@@ -355,7 +353,7 @@              If the user asks a generic question which cannot be answered with the given context or chat_history,-            just say "I don't know the answer to that question.--            Don't saying things like "according to the provided context".+            just say "I don't know the answer to that question."++            Don't say things like "according to the provided context".              <chat_history>@@ -427,6 +425,4 @@ ## Step 7: Clean up -### Clean up (optional)- Execute the following [](/sql-reference/sql/drop) commands to return your system to its state before you began the tutorial:  

--- ahttps://docs.snowflake.com/en/user-guide/kafka-connector-ts+++ bhttps://docs.snowflake.com/en/user-guide/kafka-connector-ts@@ -160,5 +160,5 @@ </dl> -5. Create a temporary table with two variant columns for testing purposes. The table is only used to validate staged data file. No data is loaded into the table. The table is dropped automatically when the current user session ends:+5. Create a temporary table with one variant column for testing purposes. The table is only used to validate staged data files. No data is loaded into the table. The table is dropped automatically when the current user session ends:     ```sql@@ -300,6 +300,6 @@ ### Failure in Streaming Channel Offset Migration Response Error Code: 5023 -When upgrading to the v2.1.0 (or higher) connector version, there was a change introduced in Snowpipe Streaming Channel name format. As a result, the logic detecting information about previously committed offsets-will not find any information about previously committed ones.+When upgrading to the v2.1.0 (or higher) connector version, a change was introduced in the Snowpipe Streaming Channel name format. As a result, the logic detecting information about previously committed offsets+will not find any information about them. This will manifest as the following exception: @@ -325,5 +325,5 @@ ### Configuring connector to support multiple topics -We have encountered an issue with a single kafka connector instance supporting a large number of topics, each having multiple partitions. The connector's configuration, even though seemed to be valid, resulted in endless re-balance cycle without possibility to ingest any data into the Snowflake.+We have encountered an issue with a single Kafka connector instance supporting a large number of topics, each having multiple partitions. The connector's configuration, even though it seemed to be valid, resulted in an endless re-balance cycle without the possibility of ingesting any data into Snowflake. The issue was specific to Snowpipe Streaming ingestion mode (`snowflake.ingestion.method=SNOWPIPE_STREAMING`), but guidelines are also applicable to Snowpipe ingestion mode (`snowflake.ingestion.method=SNOWPIPE`). The issue manifests itself in the log file by repeatedly logging this log message:@@ -338,5 +338,5 @@ <dd> -Configure partition assignment strategy to tasks as `org.apache.kafka.clients.consumer.CooperativeStickyAssignor` - this will cause even distribution of ingested channels to available tasks, reducing the risk of re-balancing. Note that `CooperativeStickyAssignor` requires Kafka Connect version 3.0.1 or later because of [this known issue](https://issues.apache.org/jira/browse/KAFKA-12487).+Configure partition assignment strategy to tasks as `org.apache.kafka.clients.consumer.CooperativeStickyAssignor`. This causes even distribution of ingested channels to available tasks, reducing the risk of re-balancing. Note that `CooperativeStickyAssignor` requires Kafka Connect version 3.0.1 or later because of [this known issue](https://issues.apache.org/jira/browse/KAFKA-12487).  </dd>@@ -344,5 +344,5 @@ <dd> -The number of instantiated tasks per connector shouldn't exceed number of available CPUs - the underlying driver implements throttling mechanism based on the available CPUs. Increasing number of concurrent requests will increase memory pressure on your system, but also will result in longer insert processing times, directly leading to missing connector's heartbeats.+The number of instantiated tasks per connector shouldn't exceed the number of available CPUs; the underlying driver implements a throttling mechanism based on the available CPUs. Increasing the number of concurrent requests will increase memory pressure on your system and will result in longer insert processing times, directly leading to missing connector's heartbeats.  </dd>@@ -355,5 +355,5 @@ <dd> -Defines how often the monitor thread (there is one associated with each task) will send heartbeat to Kafka. Default is `3000` ms, but in case of higher system load - you can experiment with increasing it to `5000` ms.+Defines how often the monitor thread (there is one associated with each task) will send a heartbeat to Kafka. Default is `3000` ms, but if system load is higher, you can experiment with increasing it to `5000` ms.  </dd>@@ -367,5 +367,5 @@ <dd> -Defines the maximum interval between call to `poll()` from underlying Kafka. The time spent between the polls basically maps to the connector processing batch of data (including upload to Snowflake and committing). In scenarios when you have multiple tasks processing data, underlying Snowflake Connection may start throttling requests, resulting in longer processing times. Depending on your scenario, you can increase this value to even 20 minutes (`1200000` ms) - especially when you start the connector with a large initial record count to be ingested.+Defines the maximum interval between calls to `poll()` from the underlying Kafka. The time spent between the polls basically maps to the connector processing batch of data (including upload to Snowflake and committing). In scenarios when you have multiple tasks processing data, underlying Snowflake Connection may start throttling requests, resulting in longer processing times. Depending on your scenario, you can increase this value to even 20 minutes (`1200000` ms), especially when you start the connector with a large initial record count to be ingested.  </dd>@@ -373,5 +373,5 @@ <dd> -When re-balance happens, in a scenario with large number of channels per task, there is a lot of underlying logic per channel to figure out where to resume processing. This code is executed sequentially, so the more channels per task, the longer initial setup will last. Configure this property to value large enough, to give each channel to complete its initialization. Value of 3 minutes (`180000` ms) is a good starting point.+When re-balance happens, in a scenario with a large number of channels per task, there is a lot of underlying logic per channel to figure out where to resume processing. This code is executed sequentially, so the more channels per task, the longer initial setup will last. Configure this property to a value large enough to give each channel time to complete its initialization. A value of 3 minutes (`180000` ms) is a good starting point.  </dd>@@ -380,5 +380,5 @@ It is also important to be aware of available heap memory for the connector. This is especially important in scenarios, where there are multiple connectors running simultaneously or you have one connector ingesting data from multiple topics. Each topic’s partition maps to a single channel and as such, requires memory. -Make sure you adjust your Kafka connect process memory settings via Xmx setting. One way of doing that is to define the+Make sure you adjust your Kafka Connect process memory settings via the Xmx setting. One way of doing that is to define the `KAFKA_OPTS` environment variable and set it accordingly (that is, `KAFKA_OPTS=-Xmx4G`). @@ -388,9 +388,9 @@ If your configuration doesn't have the `snowflake.topic2table.map` entry or there is a 1:1 mapping between the topic and the table, this issue doesn’t apply. -The Kafka connector is generating files with records to be uploaded to a stage. These files are formatted according to the following pattern:-`snowflake_kafka_connector_<connector-name>_stage_<table-name>/<connector-name>/<table-name>/<partition-id>/<low-watermark>_<high-watermark>_<timestamp>.json.gz`. The issue is located in the `<partition-id>`: if multiple topics load data into a single table, duplicates are likely on the `partition-id` value. This is not a problem in a normal connector operation. However, if the connector restarts or rebalances, the cleaner process might inaccurately associate files loaded to stage (but not yet ingested) with the wrong partition and decide to delete th... (truncated) 

差分が長いため、途中まで表示しています。

--- ahttps://docs.snowflake.com/en/developer-guide/native-apps/ui-consumer-granting-privs+++ bhttps://docs.snowflake.com/en/developer-guide/native-apps/ui-consumer-granting-privs@@ -99,5 +99,5 @@     The account level permissions requested by the app appear under-   **Account level privileges**+   **Account level privileges**.  6. In the **Account level privileges** pane, select the **Edit** icon and then move the slider for each privilege that you want to grant.@@ -211,5 +211,5 @@ communicate this requirement to the consumer, for example, in the README file of the app. -To grant the IMPORT privilege on the SNOWFLAKE database, run the following command:+To grant the IMPORTED PRIVILEGES privilege on the SNOWFLAKE database, run the following command:  ```sql@@ -352,5 +352,5 @@ ### Security and cost considerations -When allowing an app to accesses an external or Iceberg table, consumers+When allowing an app to access an external or Iceberg table, consumers should be aware of the following: @@ -364,7 +364,7 @@  Providers can configure the app to display a dialog to all consumers to allow an app to access-an external or Iceberg tables.--To allow an app to access to an external or Iceberg table:+an external or Iceberg table.++To allow an app to access an external or Iceberg table:  1. Sign in to %sf-web-interface-link%.@@ -379,13 +379,12 @@  To enable access to external and Iceberg tables by using SQL use the-SET_APPLICATION_RESTRICTED_FEATURE_ACCESS system function as shown in the following+SYSTEM$SET_APPLICATION_RESTRICTED_FEATURE_ACCESS system function as shown in the following example:  ```sql-SELECT SYSTEM$SET_APPLICATION_RESTRICTED_FEATURE_ACCESS(hello_snowflake_app, 'external_data', '{"allowed_cloud_providers" : "all"}');-```--This command allows the `hello_snowflake_app` app to access the external or Iceberg tables in the-that the app uses.+SELECT SYSTEM$SET_APPLICATION_RESTRICTED_FEATURE_ACCESS('hello_snowflake_app', 'external_data', '{"allowed_cloud_providers" : "all"}');+```++This command allows the `hello_snowflake_app` app to access the external or Iceberg tables in the share that the app uses.  To determine if external and Iceberg tables have been enabled for an app, use the@@ -397,3 +396,3 @@  This system function returns a JSON object that indicates if external and Iceberg tables are allowed-the for the `hello_snowflake_app`.+for the `hello_snowflake_app`. 

--- ahttps://docs.snowflake.com/en/user-guide/snowflake-postgres/postgres-data-mirroring-query+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-postgres/postgres-data-mirroring-query@@ -84,5 +84,5 @@ ## Query changes with the `$changes` table -Each mirrored table has a companion `$changes` table (e.g. `orders_db.public.orders$changes`). It is a rolling **7-day change feed**: every insert, update, and delete that happens on the+Each mirrored table has a companion `$changes` table (for example, `orders_db.public.orders$changes`). It is a rolling **7-day change feed**: every insert, update, and delete that happens on the source PostgreSQL table shows up here as a queryable row, with a `_change_type` column (`I` for insert, `D` for delete; updates appear as a delete/insert pair). @@ -91,5 +91,5 @@ ### Snapshotting -When a table is **added to a mirror for the first time** — whether by creating the mirror, adding a table explicitly, or creating a new table inside a schema that is already mirrored — the mirror needs a full baseline copy of any existing rows before the change feed can start. During this period the table shows as `SNAPSHOTTING` in `list_mirrored_tables`. No changes are lost; the feed starts automatically once the copy completes.+When a table is **added to a mirror for the first time,** whether by creating the mirror, adding a table explicitly, or creating a new table inside a schema that is already mirrored, the mirror needs a full baseline copy of any existing rows before the change feed can start. During this period the table shows as `SNAPSHOTTING` in `list_mirrored_tables`. No changes are lost; the feed starts automatically once the copy completes.  This is the only situation that triggers a full data copy. No DDL on an already-mirrored table causes a re-snapshot.@@ -107,5 +107,5 @@ In other words: **after a column change, `$changes` only contains rows that were written after the DDL**. Any rows from before the column change are gone from the feed. The new `$changes` table's `_data_version` carries forward from the previous table's last value rather than resetting to 1, so consumers that use `_data_version` to detect a fresh start should treat any increase as a signal to reset state. -The underlying data files from before the DDL are not immediately deleted — they continue to exist for up to 7 days before being cleaned up — but they are no longer exposed through `$changes`.+The underlying data files from before the DDL are not immediately deleted; they continue to exist for up to 7 days before being cleaned up, but they are no longer exposed through `$changes`.  If you have a pipeline or query that reads `$changes` and depends on seeing the full 7-day history, be aware that a column DDL will truncate that window back to zero at the moment it is applied.@@ -113,14 +113,14 @@ ## Check row version with `_data_version` -Every row in `$changes` carries a `_data_version` integer. Unlike the column DDL case above, these operations do not replace `$changes` with a new empty table — the feed keeps running and all existing rows remain visible. However, they still mark a new generation in the system: the `_data_version` value increments at the boundary, signalling that rows before and after that point should not be treated as part of the same continuous sequence. Consumers should treat a version bump as a cue to reset their bookmarks or deduplication state.+Every row in `$changes` carries a `_data_version` integer. Unlike the column DDL case above, these operations do not replace `$changes` with a new empty table; the feed keeps running and all existing rows remain visible. However, they still mark a new generation in the system: the `_data_version` value increments at the boundary, signaling that rows before and after that point should not be treated as part of the same continuous sequence. Consumers should treat a version bump as a cue to reset their bookmarks or deduplication state. -| PostgreSQL DDL                                      | What happens                                                                                                                                                                           |-| --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |-| `TRUNCATE`                                          | All existing rows on the source were wiped. `_data_version` bumps to mark the clean-slate boundary.                                                                                    |-| `ALTER TABLE ... ADD PRIMARY KEY`                   | The table gains the ability to accept updates and deletes (it was insert-only before). `_data_version` bumps to separate the two eras.                                                 |-| `ALTER TABLE ... DROP CONSTRAINT ... (primary key)` | The table reverts to insert-only mode. Same version bump.                                                                                                                              |-| `ALTER TABLE ... RENAME TO`                         | The table — and its `$changes` companion — is renamed on Snowflake. `_data_version` bumps to keep change batches from before and after the rename from being confused with each other. |-| `ALTER TABLE ... SET SCHEMA`                        | Same as a rename but the table moves to a different schema.                                                                                                                            |-| `ALTER SCHEMA ... RENAME TO`                        | All tables in the renamed schema are renamed on Snowflake simultaneously, each with a `_data_version` bump.                                                                            |+| PostgreSQL DDL                                      | What happens                                                                                                                                                                        |+| --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |+| `TRUNCATE`                                          | All existing rows on the source were wiped. `_data_version` bumps to mark the clean-slate boundary.                                                                                 |+| `ALTER TABLE ... ADD PRIMARY KEY`                   | The table gains the ability to accept updates and deletes (it was insert-only before). `_data_version` bumps to separate the two eras.                                              |+| `ALTER TABLE ... DROP CONSTRAINT ... (primary key)` | The table reverts to insert-only mode. Same version bump.                                                                                                                           |+| `ALTER TABLE ... RENAME TO`                         | The table and its `$changes` companion are renamed on Snowflake. `_data_version` bumps to keep change batches from before and after the rename from being confused with each other. |+| `ALTER TABLE ... SET SCHEMA`                        | Same as a rename but the table moves to a different schema.                                                                                                                         |+| `ALTER SCHEMA ... RENAME TO`                        | All tables in the renamed schema are renamed on Snowflake simultaneously, each with a `_data_version` bump.                                                                         |  ## Use Cortex Search on mirrored tables 

--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/oracle/setup-connector+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/oracle/setup-connector@@ -68,9 +68,9 @@   connectors on Small only when each source is genuinely light. - Moderate workload (approximately 1,000 to 5,000 events per second, hundreds-  of actively changing tables): a Medium runtime, typically running 5 to 8+  of actively changing tables): a Medium runtime can typically host 5 to 8   connectors. - Heavy workload (approximately 5,000 to 15,000 events per second, hundreds to-  low thousands of actively changing tables): a Large runtime, typically-  running 15 or more connectors. If you want a smaller blast radius, split+  low thousands of actively changing tables): a Large runtime can typically host+  15 or more connectors. If you want a smaller blast radius, split   across two Medium runtimes instead. @@ -291,5 +291,5 @@   BYOC deployments must have previously configured   [runtime roles](#label-deployment-byoc-setup-runtime-role) to use SNOWFLAKE_MANAGED.-- **BYOC:** Alternatively BYOC can use KEY_PAIR as the value for authentication strategy.+- **BYOC**: Alternatively, BYOC can use KEY_PAIR as the value for the authentication strategy.  </td>@@ -303,5 +303,5 @@  - **SNOWFLAKE_MANAGED** Authentication Strategy: Must be blank.-- **KEY_PAIR**: Snowflake account name formatted as [organization-name]-[account-name] where data is persisted.+- **KEY_PAIR**: Snowflake account name formatted as [organization-name]-[account-name].  </td>@@ -389,5 +389,5 @@  - **SNOWFLAKE_MANAGED** Authentication Strategy: Must be blank.-- **KEY_PAIR**: Provide the user name used to connect to the Snowflake instance.+- **KEY_PAIR**: Provide the username used to connect to the Snowflake instance.  </td>@@ -460,5 +460,5 @@  Comma-separated list of fully-qualified table paths.-Tables must be specified using fully qualified database, schema and table name format: DATABASE_NAME.SCHEMA_NAME.TABLE_NAME.+Tables must be specified using fully-qualified database, schema, and table name format: DATABASE_NAME.SCHEMA_NAME.TABLE_NAME.  For example: `MYPDB.SALES.CUSTOMERS, MYPDB.SALES.ORDERS`@@ -543,5 +543,5 @@ Snowflake recommends using this option if database objects aren't expected to have mixed case names. -<p><span className="emph">Option 2: case-sensitive.</span></p>+<p><span className="emph">Option 2: Case-sensitive.</span></p>  - **Transformation**: Case is preserved.@@ -603,5 +603,5 @@ JDBC URL of the database connection to the DB. The URL must specify the target container (PDB or CDB) that contains the data to be replicated.-For example `jdbc:oracle:thin@<host>:<port>/YOUR_DB_NAME` where YOUR_DB_NAME is the name of your PDB or CDB.+For example `jdbc:oracle:thin:@<host>:<port>/YOUR_DB_NAME` where YOUR_DB_NAME is the name of your PDB or CDB.  When SSL is enabled, use the TCPS protocol, for example@@ -654,5 +654,5 @@     <tr>       <td>Oracle Database Processor Multiplier</td>-      <td>Core Processor Licensing Factor as described in [Oracle Processor Core Factor Table](https://www.oracle.com/contracts/docs/processor-core-factor-table-070634.pdf)</td>+      <td>Core Processor Licensing Factor as described in [Oracle Processor Core Factor Table](https://www.oracle.com/contracts/docs/processor-core-factor-table-070634.pdf).</td>       <td>Required for Embedded License only</td>     </tr>@@ -664,5 +664,5 @@     <tr>       <td>XStream Billing Acknowledgement</td>-      <td>A confirmation of the licensing agreement</td>+      <td>A confirmation of the licensing agreement.</td>       <td>Required for Embedded License only</td>     </tr>@@ -676,5 +676,5 @@       <td> -JDBC URL of the database connection for XStream, must use OCI driver.+JDBC URL of the database connection for XStream, which must use the OCI driver. For example `jdbc:oracle:oci:@<host>:<port>/SID`.  

--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/aisql-regional-availability+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/aisql-regional-availability@@ -211,10 +211,10 @@     <tr>       <td>`claude-opus-5`</td>-      <td>\*</td>-      <td>\*</td>-      <td></td>-      <td></td>-      <td></td>-      <td>\*</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td>%cm%</td>       <td></td>       <td></td>@@ -226,10 +226,10 @@     <tr>       <td>`claude-opus-4-8`</td>-      <td>\*</td>-      <td>\*</td>-      <td></td>-      <td></td>-      <td></td>-      <td>\*</td>+      <td>%cm%</td>+      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>+      <td>%cm%</td>       <td></td>       <td></td> 

--- ahttps://docs.snowflake.com/en/developer-guide/native-apps/consumer-guide-evaluate+++ bhttps://docs.snowflake.com/en/developer-guide/native-apps/consumer-guide-evaluate@@ -13,8 +13,8 @@ Three stakeholder groups typically review a %native-app% before procurement approval: the business team establishing value, the finance team assessing cost and risk, and the security and legal teams-conducting compliance and risk review. Not every reviewer needs every section — use the headings+conducting compliance and risk review. Not every reviewer needs every section. Use the headings below to navigate to the relevant parts. -## Business evaluation — does it meet the business objective?+## Business evaluation: does it meet the business objective?  The business review focuses on one question: does this app deliver the outcome we need?@@ -22,5 +22,5 @@  **Define the business objective before evaluating the app.** A clear statement of expected outcome-— for example, "reduce time to identify high-value customers by 30%" — makes it easier to assess+(for example, "reduce time to identify high-value customers by 30%") makes it easier to assess whether the app's capabilities are a genuine fit. @@ -43,5 +43,5 @@ version and patch submitted by the provider. This process is largely automated; manual review occurs in exceptional cases. This means the app you install has been scanned not just when it was-first published, but each time the provider released a new version or patch.+first published, but each time the provider releases a new version or patch.  These reviews establish a baseline. They are not a substitute for consumer due diligence.@@ -51,5 +51,5 @@ Provider is the seller of record; not Snowflake. -Consumer is responsible for security, privacy, compliance and all other necessary reviews of the+Consumer is responsible for security, privacy, compliance, and all other necessary reviews of the provider's app. Any security scanning or other vetting done by Snowflake is not a substitute for a consumer's due diligence.@@ -68,12 +68,12 @@  `CREATE WAREHOUSE`, `CREATE TASK`, `CREATE MANAGED TASK`, `CREATE DATABASE`, `CREATE COMPUTE POOL`,-`BIND SERVICE ENDPOINT` — these allow the app to create operational resources. They do not, by+`BIND SERVICE ENDPOINT`. These allow the app to create operational resources. They do not, by themselves, grant the app access to your data. See [](/developer-guide/native-apps/consumer-guide-access#category-1-automatically-grantable-privileges) for the full list. -**App Spec requests (higher risk — require explicit approval):**+**App Spec requests (higher risk, requiring explicit approval):** -App Specs are requests for capabilities that go beyond creating operational resources — for example,+App Specs are requests for capabilities that go beyond creating operational resources, for example, making outbound network calls, using OAuth to connect to external services, sharing data back, or connecting to another app. The provider should disclose expected App Specs during procurement so you@@ -88,5 +88,5 @@ monitoring queries in [](/developer-guide/native-apps/consumer-guide-monitor). -## Involving your security team — a structured handoff+## Involving your security team: a structured handoff  To support a thorough security review, provide your security team with the following before@@ -100,5 +100,5 @@   and listing details if applicable - The provider's documentation of what data access the app will need (Category 3 grants)-- The formal shared-responsibility framework — see+- The formal shared-responsibility framework: see   [](/developer-guide/native-apps/consumer-guide-responsibility) @@ -112,5 +112,5 @@ For trial apps: when the trial period expires, Snowflake automatically suspends the app unless you convert to a full paid listing. Data written inside the app is retained while the app is suspended,-as long as you do not drop the app. Convert before expiry — once suspended, resumption is not+as long as you do not drop the app. Convert before expiry. Once suspended, resumption is not guaranteed if the provider has changed the version or if there are unresolved state issues. @@ -122,5 +122,5 @@ creates warehouses (Category 1 privilege), those warehouses consume credits in your account. For apps with containers, the compute pool also consumes credits. Monitor this using-`APPLICATION_DAILY_USAGE_HISTORY` — see+`APPLICATION_DAILY_USAGE_HISTORY`. See [](/developer-guide/native-apps/consumer-guide-monitor#monitoring-app-activity-and-usage).  

--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/limitations+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/limitations@@ -25,5 +25,5 @@ <a id="label-dsna-supported-object-types"></a> -## Supported Object Types+## Supported object types  Declarative sharing supports these object types:@@ -47,5 +47,5 @@ <a id="label-dsna-shared-objects"></a> -## Shared Objects+## Shared objects  <dl>@@ -60,5 +60,5 @@ <dd> -Requires `CHANGE_TRACKING = TRUE` to be enabled on the provider's source object.+The provider's source object must have `CHANGE_TRACKING = TRUE` enabled.  </dd>@@ -120,5 +120,5 @@ <a id="label-dsna-notebook-limitations"></a> -## Notebook Limitations+## Notebook limitations  Sharing individual notebooks with `application_content.notebooks` shares@@ -143,5 +143,5 @@ <dd> -Notebooks cannot access external endpoints or consumer data when running in customer accounts.+Notebooks can't access external endpoints or consumer data when running in consumer accounts.  </dd>@@ -149,5 +149,5 @@ <dd> -Geospatial and other 3rd party libraries aren't guaranteed to work out-of-the-box in notebooks.+Geospatial and other third-party libraries aren't guaranteed to work out-of-the-box in notebooks.  </dd>@@ -155,5 +155,5 @@ <dd> -Declarative Sharing apps have limited support for external libraries (Snowflake Anaconda channel and Python files in code stage.)+Declarative Sharing apps have limited support for external libraries (Snowflake Anaconda channel and Python files in code stage).  </dd>@@ -161,5 +161,5 @@ <dd> -Notebooks that are part of native applications cannot be executed non-interactively by+Notebooks that are part of Native Apps cannot be executed non-interactively by worksheets or SQL commands. @@ -169,5 +169,5 @@ <a id="label-dsna-security-and-access-control"></a> -## Security and Access Control+## Security and access control  <dl>@@ -206,5 +206,5 @@ <a id="label-dsna-migration-compatibility"></a> -## Migration & Compatibility+## Migration and compatibility  <dl>@@ -219,5 +219,5 @@ <a id="label-dsna-naming-and-configuration-constraints"></a> -## Naming and Configuration Constraints+## Naming and configuration constraints  <dl>@@ -266,5 +266,5 @@  <dl>-<dt>Execution Environment</dt>+<dt>Execution environment</dt> <dd>  

--- ahttps://docs.snowflake.com/en/sql-reference/account-usage/iceberg_storage_optimization_history+++ bhttps://docs.snowflake.com/en/sql-reference/account-usage/iceberg_storage_optimization_history@@ -12,5 +12,5 @@ - [](/user-guide/tables-iceberg) -Use this Account Usage view to query Iceberg storage optimization jobs, which includes *data compaction*, within the last 365 days (1 year)+Use this Account Usage view to query Iceberg storage optimization jobs, which include *data compaction*, within the last 365 days (1 year) for %iceberg-tm% tables in your account. You can query jobs for the following Iceberg tables: @@ -18,5 +18,5 @@ - Open Catalog-managed tables -- Snowflake starts billing for data compaction of data files for Snowflake-managed Iceberg tables on October 20th, 2025.+- Snowflake starts billing for data compaction of data files for Snowflake-managed Iceberg tables on October 20, 2025. - For Iceberg tables that use Snowflake storage (`EXTERNAL_VOLUME = SNOWFLAKE_MANAGED`), data compaction is bundled   for tables that are written only by Snowflake. While a table is written only by Snowflake, this view reports `0`@@ -123,14 +123,15 @@ The following example shows how to filter for tables whose number of credits billed is more than a specified amount: -```sql-  SELECT-      table_name,-      start_time,-      credits_used-    FROM SNOWFLAKE.ACCOUNT_USAGE.ICEBERG_STORAGE_OPTIMIZATION_HISTORY-    WHERE credits_used > 0.0005-    ORDER BY-      credits_used DESC;+sql+SELECT+table_name,+start_time,+credits_used+FROM SNOWFLAKE.ACCOUNT_USAGE.ICEBERG_STORAGE_OPTIMIZATION_HISTORY+WHERE credits_used > 0.0005+ORDER BY+credits_used DESC; +``` The query returns the following results: ``` 

--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-ml/overview+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-ml/overview@@ -9,5 +9,5 @@ ![Snowflake ML Overview Diagram](/static/images/snowflake-ml/snowflake-ml_v6-NEWEST-full-CortexCode.png) -Scaling end-to-end ML workflows in Snowflake is seamless. You can automate the following all from simple prompts in CoCo with native context awareness across your data, models, notebooks, features on a unified platform:+Scaling end-to-end ML workflows in Snowflake is seamless. You can automate the following all from simple prompts in CoCo with native context awareness across your data, models, notebooks, and features on a unified platform:  - Prepare data@@ -20,35 +20,35 @@ - Use ML Lineage to track the source data to features, datasets, and models throughout your ML pipeline -Snowflake ML is also flexible and modular. You can deploy the models that you've developed in Snowflake outside of Snowflake and externally-trained models can easily be brought into Snowflake for inference.+Snowflake ML is also flexible and modular. You can deploy the models that you've developed in Snowflake outside of Snowflake, and externally trained models can easily be brought into Snowflake for inference. -### Agentic ML+## Agentic ML  Snowflake CoCo powers [agentic ML](/developer-guide/snowflake-ml/agentic-ml) by autonomously planning, executing, and iterating on machine learning workflows on your behalf. You can ask it to complete a single task or pursue a broader goal that requires multi-step reasoning and action. From a natural language prompt, CoCo can explore data, engineer features, train and evaluate models, debug issues, and prepare models for deployment. -### Model Training+## Model Training  ML training in Snowflake runs in [Container Runtime](/developer-guide/snowflake-ml/container-runtime-ml), a pre-built ML environment optimized for efficient data loading, distributed model training, and hyperparameter tuning on large amounts of data. Start training with preinstalled packages such as PyTorch, XGBoost, or Scikit-learn, or install any package from open-source repositories like Hugging Face or PyPI. You can access Container Runtime directly from Snowflake Notebooks which provide a Jupyter-like environment for training and fine-tuning large-scale models in Snowflake, without infrastructure management. -### Manage and Serve Features+## Manage and Serve Features -The [](/developer-guide/snowflake-ml/feature-store/overview) is an integrated solution for defining, managing, storing and discovering ML features derived from your data. The Snowflake Feature Store supports automated, incremental refresh from batch and streaming data sources, so that feature pipelines need be defined only once to be continuously updated with new data. It supports both batch and low-latency online feature retrieval, and ensures consistency between training and inference to reduce training-serving skew.+The [](/developer-guide/snowflake-ml/feature-store/overview) is an integrated solution for defining, managing, storing and discovering ML features derived from your data. The Snowflake Feature Store supports automated, incremental refresh from batch and streaming data sources, so that feature pipelines need only be defined once to be continuously updated with new data. It supports both batch and low-latency online feature retrieval, and ensures consistency between training and inference to reduce training-serving skew. -### Orchestrate and Automate+## Orchestrate and Automate  Use [](/developer-guide/snowflake-ml/ml-jobs/overview) to develop and automate ML pipelines. ML Jobs also enable teams that prefer working from an external IDE (VS Code, PyCharm, SageMaker Notebooks) to dispatch functions, files or modules down to Snowflake’s Container Runtime. -### Experiment Tracking+## Experiment Tracking  Use [experiments](/developer-guide/snowflake-ml/experiments) to record the results of your model training, and evaluate a collection of models in an organized way. Experiments help you select the best model for your use case to bring live to production. Training can either be logged in an experiment during model training on Snowflake, or you can upload your own metadata and artifacts from prior training. After concluding your training, view all of the results in %sf-web-interface% and pick the right model for your needs. -### Model Management and Serving+## Model Management and Serving  The [](/developer-guide/snowflake-ml/model-registry/overview) allows for the logging and management of all your ML models, regardless of whether they're trained on Snowflake or other platforms. You can use the models from the model registry to run inference at scale. You can use Model Serving to deploy the models to Snowpark Container Services for inference. -### ML Observability+## ML Observability  [ML Observability](/developer-guide/snowflake-ml/model-registry/model-observability) provides tools to monitor model performance metrics in Snowflake. You can track models in production, monitor performance and drift metrics, and set alerts for performance thresholds. Additionally, use the ML Explainability function to compute Shapley values for models in the Snowflake Model Registry, regardless of where they were trained. -### ML Lineage+## ML Lineage  [ML Lineage](/developer-guide/snowflake-ml/ml-lineage) is a capability to trace end-to-end lineage of ML artifacts from source data to features, datasets, and models. This enables reproducibility, compliance, and debugging across the full lifecycle of ML assets. 

--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/cost-byoc+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/cost-byoc@@ -41,5 +41,5 @@ within your "bring your own cloud (BYOC)" environment. You are charged for active runtimes only. The compute used for Openflow management processes is excluded from this specific charge.-Credits are billed per-second with a 60 second minimum.+Credits are billed per-second with a 60-second minimum.  For an example of using of VCPU and the impacts of scaling see [](#label-openflow-byoc-scaling-overview).@@ -112,11 +112,11 @@ The following table illustrates the scaling behavior of various runtimes and their associated costs: -| Runtimes                                                                          | Activity                                                                                                                         | Snowflake costs                                                                                                                                                 | Cloud costs                      |-| --------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------- |-| No runtimes                                                                       | None                                                                                                                             | No cost                                                                                                                                                         | Compute and storage of Dataplane |-| 1 small runtime (1vCPU) <br /> (min 1 max 2)                                      | Active for 1 hour <br /> Runtime does not scale to 2.                                                                            | 1 runtime x 1 node x 1 vCPU x 1 hour = 1 <br /> Total = 1 vCPU-hour                                                                                             | Compute and storage of Dataplane |-| 2 small runtime (1 vCPU) (min/max=2) <br /> 1 large runtime (8 vCPU) (min/max=10) | Small: 2 nodes active for 1 hour <br /> Large: 10 nodes active for 1 hour                                                        | 2 runtime2 x 2 node x 2 vCPU x 1 hour = 4 vCPU <br /> 1 runtime x 10 nodes x 8 vCPU x 1 hour = 80 vCPU <br /> Total = 84 vCPU-hours                             | Compute and storage of Dataplane |-| 1 medium (4vCPU) <br /> (min =1 max=2)                                            | First 20 minutes, 1 node is running <br /> Scales to 2 nodes for the remaining 40 minutes of the hour <br /> Total 1 hour <br /> | 20 minutes = 1/3 hour <br /> 1 runtime x 1 node x 4 vCPU x 1/3 hour = 4/3 <br /> 1 runtime x 2 nodes x 4 vCPU x 2/3 hour = 16/3 <br /> Total = 6 2/3 vCPU-hours | Compute and storage of Dataplane |-| 1 medium (4vCPU) <br /> (min/max=2)                                               | First 30 minutes 2 nodes running <br /> Suspends after first 30 minutes.                                                         | 30 minutes = 1/2 hour <br /> 1 runtime x 2 nodes x 4 vCPU x 1/2 hour = 4 <br /> Total = 4 vCPU-hours                                                            | Compute and storage of Dataplane |+| Runtimes                                                                           | Activity                                                                                                                         | Snowflake costs                                                                                                                                                 | Cloud costs                      |+| ---------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------- |+| No runtimes                                                                        | None                                                                                                                             | No cost                                                                                                                                                         | Compute and storage of Dataplane |+| 1 small runtime (1vCPU) <br /> (min 1 max 2)                                       | Active for 1 hour <br /> Runtime does not scale to 2.                                                                            | 1 runtime x 1 node x 1 vCPU x 1 hour = 1 <br /> Total = 1 vCPU-hour                                                                                             | Compute and storage of Dataplane |+| 2 small runtimes (1 vCPU) (min/max=2) <br /> 1 large runtime (8 vCPU) (min/max=10) | Small: 2 nodes active for 1 hour <br /> Large: 10 nodes active for 1 hour                                                        | 2 runtimes x 2 nodes x 1 vCPU x 1 hour = 4 vCPU <br /> 1 runtime x 10 nodes x 8 vCPU x 1 hour = 80 vCPU <br /> Total = 84 vCPU-hours                            | Compute and storage of Dataplane |+| 1 medium (4vCPU) <br /> (min =1 max=2)                                             | First 20 minutes, 1 node is running <br /> Scales to 2 nodes for the remaining 40 minutes of the hour <br /> Total 1 hour <br /> | 20 minutes = 1/3 hour <br /> 1 runtime x 1 node x 4 vCPU x 1/3 hour = 4/3 <br /> 1 runtime x 2 nodes x 4 vCPU x 2/3 hour = 16/3 <br /> Total = 6 2/3 vCPU-hours | Compute and storage of Dataplane |+| 1 medium (4vCPU) <br /> (min/max=2)                                                | First 30 minutes 2 nodes running <br /> Suspends after first 30 minutes.                                                         | 30 minutes = 1/2 hour <br /> 1 runtime x 2 nodes x 4 vCPU x 1/2 hour = 4 <br /> Total = 4 vCPU-hours                                                            | Compute and storage of Dataplane |  ### Mapping runtimes to EC2 instance types@@ -158,9 +158,9 @@  </dd>-<dt>A user creates 2 small runtimes with min/max of 2 nodes each, and one large runtime with min/max of 10 nodes. These Runtimes are active for 1 hour</dt>+<dt>A user creates 2 small runtimes with min/max of 2 nodes each, and one large runtime with min/max of 10 nodes. These runtimes are active for 1 hour</dt> <dd> -- 2 small runtimes at 2 nodes = 2 Runtimes x 2 nodes x 1 vCPU = 4 vCPUs-- 1 large runtime at 10 nodes = 1 Runtime x 10 nodes x 8 vCPU = 80 vCPUs+- 2 small runtimes at 2 nodes = 2 runtimes x 2 nodes x 1 vCPU = 4 vCPUs+- 1 large runtime at 10 nodes = 1 runtime x 10 nodes x 8 vCPU = 80 vCPUs - Total Openflow consumption = (4 vCPU + 80 vCPU) x 1 hour = 84 vCPU-hours  

--- ahttps://docs.snowflake.com/en/developer-guide/snowpark-container-services/working-with-compute-pool+++ bhttps://docs.snowflake.com/en/developer-guide/snowpark-container-services/working-with-compute-pool@@ -100,5 +100,5 @@  - **Specify DISTRIBUTED:** When you set `placement_group` to DISTRIBUTED, Snowflake attempts to distribute nodes for that compute pool-  across all available placement groups. You should set `placement_group` to `DISTRIBUTED` if you want to maintain healthy fault tolerance across multiple placement groups. When compute pool nodes are distributed across multiple placement groups, if one placement group goes down, you don't lose all the nodes+  across all available placement groups. You should set `placement_group` to `DISTRIBUTED` if you want to maintain healthy fault tolerance across multiple placement groups. When compute pool nodes are distributed across multiple placement groups, if one placement group goes down, you don't lose all the nodes.    The following behaviors apply when you set `placement_group` to DISTRIBUTED for a compute pool:@@ -119,5 +119,5 @@ <a id="label-spcs-working-with-compute-pools-instance-family-table"></a> -### Instance Families for Compute Pool Nodes+### Instance families for compute pool nodes  For a complete list of available instance families organized by cloud provider, see@@ -164,5 +164,5 @@ You can manage a compute pool using %sf-web-interface-link%, or SQL. -In %sf-web-interface-link%, you choose the more option (**...**) next to the compute pool name, and choose the desired operation from the menu. The section explains SQL commands you can use to manage a compute pool.+In %sf-web-interface-link%, you choose the more options menu (**...**) next to the compute pool name, and choose the desired operation from the menu. This section explains SQL commands you can use to manage a compute pool.  Snowpark Container Services provides the following commands to manage compute pools:@@ -198,5 +198,5 @@      ```sql-    ALTER COMPUTE POOL my_pool SET MIN_NODES = 2  MAX_NODES = 2;+    ALTER COMPUTE POOL my_pool SET MIN_NODES = 2 MAX_NODES = 2;     ``` @@ -219,5 +219,5 @@ to add or remove the nodes. -There are several properties related to the number of nodes in a compute pool. These includes: `min_nodes`, `max_nodes`, `active_nodes`, `idle_nodes`, and `target_nodes`. For more information about these properties, see [DESC COMPUTE POOL](/sql-reference/sql/desc-compute-pool) and [SHOW COMPUTE POOLS](/sql-reference/sql/show-compute-pools).+There are several properties related to the number of nodes in a compute pool. These include: `min_nodes`, `max_nodes`, `active_nodes`, `idle_nodes`, and `target_nodes`. For more information about these properties, see [DESC COMPUTE POOL](/sql-reference/sql/desc-compute-pool) and [SHOW COMPUTE POOLS](/sql-reference/sql/show-compute-pools).  The following examples demonstrate how to interpret the values in the `target_nodes` column.@@ -259,5 +259,5 @@ - **RESIZING:** When you create a compute pool, initially it enters the STARTING state. After it has one node provisioned, it enters the RESIZING state until the minimum number of nodes (as specified in CREATE COMPUTE POOL) are provisioned. When you change a compute pool (ALTER COMPUTE POOL) and update the minimum and maximum node values, the pool enters the RESIZING state until the minimum nodes are provisioned. Note that autoscaling of a compute pool also puts the compute pool in the RESIZING state. -For information about how the costs incurred during the different states of the compute pool lifecycle, see [](#label-compute-pool-cost).+For information about the costs incurred during the different states of the compute pool lifecycle, see [](#label-compute-pool-cost).  <a id="label-spcs-working-with-compute-pool-privileges"></a>@@ -291,5 +291,5 @@     <tr>       <td>MONITOR</td>-      <td>Enables viewing compute pool usage, including describing  compute pool properties. Enables access to the monitoring endpoint exposed by the compute pool.</td>+      <td>Enables viewing compute pool usage, including describing compute pool properties. Enables access to the monitoring endpoint exposed by the compute pool.</td>     </tr>     <tr>@@ -408,5 +408,5 @@     - In AWS, GPU_NV_S. -    Note that, the following regions do not support SYSTEM_COMPUTE_POOL_GPU:+    Note that the following regions do not support SYSTEM_COMPUTE_POOL_GPU:      - In AWS: Singapore, Switzerland North, Paris, and Osaka.@@ -428,5 +428,5 @@     - AUTO_SUSPEND_SECS=259200 -Note that,+Note that  - Compute pools are initially in a suspended state and only begin incurring costs when a supported Snowflake workload starts using them.@@ -464,5 +464,5 @@ </blockquote> -System compute pools can be associated with [budgets](/user-guide/budgets). for cost management.+System compute pools can be associated with [budgets](/user-guide/budgets) for cost management.  <a id="label-spcs-working-with-compute-pools-default-compute-pools-for-streamlit"></a>@@ -507,5 +507,5 @@ ### Configuring your own preferred compute pools for Notebooks -By default, Notebook services run in system compute pools. If you don't want to use the Snowflake-provisioned compute pools, you have the option to choose other compute pools in your account for Notebooks. To override the Snowflake-provisioned compute pools you can set these parameters ([](#label-default-notebook-compute-pool-cpu) and [](#label-default-notebook-compute-pool-gpu)). Note that, this will change your Snowsight experience. When creating a Notebook in Snowsight, the compute pool you configure using these parameters appears as the first preference in the UI. The following example commands set these parameters:+By default, Notebook services run in system compute pools. If you don't want to use the Snowflake-provisioned compute pools, you have the option to choose other compute pools in your account for Notebooks. To override the Snowflake-provisioned compute pools you can set these parameters ([](#label-default-notebook-compute-pool-cpu) and [](#label-default-notebook-compute-pool-gpu)). Note that this will change your Snowsight experience. When creating a Notebook in Snowsight, the compute pool you configure using these parameters appears as the first preference in the UI. The following example commands set these parameters:  - Configure `my_pool` as the account-level compute pool preferred for Notebooks using GPU runtime. 

--- ahttps://docs.snowflake.com/en/sql-reference/billing/focus_cost_usage_v1_3+++ bhttps://docs.snowflake.com/en/sql-reference/billing/focus_cost_usage_v1_3@@ -146,5 +146,5 @@       <td>ServiceCategory</td>       <td>TEXT</td>-      <td>High-level category of the Snowflake service (e.g., `Compute`, `Storage`, `AI and Machine Learning`).</td>+      <td>High-level category of the Snowflake service (for example, `Compute`, `Storage`, `AI and Machine Learning`).</td>     </tr>     <tr>@@ -156,15 +156,15 @@       <td>ChargeDescription</td>       <td>TEXT</td>-      <td>Human-readable description of the charge (e.g., `OVERAGE-COMPUTE`).</td>+      <td>Human-readable description of the charge (for example, `OVERAGE-COMPUTE`).</td>     </tr>     <tr>       <td>ConsumedQuantity</td>       <td>NUMBER(38,9)</td>-      <td>How the underlying resource was metered (up to 9 decimal places). May differ in unit from PricingQuantity (e.g., storage is metered in TiB-Days but priced in TiB-Months).</td>+      <td>How the underlying resource was metered (up to 9 decimal places). May differ in unit from PricingQuantity (for example, storage is metered in TiB-Days but priced in TiB-Months).</td>     </tr>     <tr>       <td>ConsumedUnit</td>       <td>TEXT</td>-      <td>Unit of metered consumption (e.g., `Credits`, `TiB-Days`, `TiB-Months`).</td>+      <td>Unit of metered consumption (for example, `Credits`, `TiB-Days`, `TiB-Months`).</td>     </tr>     <tr>@@ -176,5 +176,5 @@       <td>PricingUnit</td>       <td>TEXT</td>-      <td>Unit corresponding to PricingQuantity (e.g., `Credits`, `TiB-Months`).</td>+      <td>Unit corresponding to PricingQuantity (for example, `Credits`, `TiB-Months`).</td>     </tr>     <tr>@@ -231,15 +231,15 @@       <td>RegionId</td>       <td>TEXT</td>-      <td>Cloud provider region identifier (e.g., `AWS_US_WEST_2`).</td>+      <td>Cloud provider region identifier (for example, `AWS_US_WEST_2`).</td>     </tr>     <tr>       <td>RegionName</td>       <td>TEXT</td>-      <td>Cloud provider region display name (e.g., `AWS_US_WEST_2`).</td>+      <td>Cloud provider region display name (for example, `AWS_US_WEST_2`).</td>     </tr>     <tr>       <td>HostProviderName</td>       <td>TEXT</td>-      <td>Name of the underlying cloud infrastructure provider (e.g., `Aws`, `Azure`, `Gcp`).</td>+      <td>Name of the underlying cloud infrastructure provider (for example, `Aws`, `Azure`, `Gcp`).</td>     </tr>     <tr>@@ -295,10 +295,10 @@       <td>x_ServiceLevel</td>       <td>TEXT</td>-      <td>Snowflake edition/service level of the sub-account (e.g., `Enterprise`, `Business Critical`, `Standard`).</td>+      <td>Snowflake edition/service level of the sub-account (for example, `Enterprise`, `Business Critical`, `Standard`).</td>     </tr>     <tr>       <td>ContractApplied.x_BalanceSource</td>       <td>TEXT</td>-      <td>The balance source where usage is drawn down from (e.g., `capacity`, `rollover`, `free usage`, `overage`).</td>+      <td>The balance source where usage is drawn down from (for example, `capacity`, `rollover`, `free usage`, `overage`).</td>     </tr>     <tr>@@ -404,5 +404,5 @@     <tr>       <td>InvoiceId may be empty</td>-      <td>For Contract (capacity) customers, InvoiceId may be empty as usage is not tied directly to the invoice for capacity purchases. For On-Demand customers, InvoiceId will only be populated after month end.</td>+      <td>For Contract (capacity) customers, InvoiceId may be empty, as usage is not tied directly to the invoice for capacity purchases. For On-Demand customers, InvoiceId will only be populated after month end.</td>     </tr>     <tr> 

--- ahttps://docs.snowflake.com/en/connectors/postgres6/prereqs-datasource+++ bhttps://docs.snowflake.com/en/connectors/postgres6/prereqs-datasource@@ -38,5 +38,5 @@ %postgres6% requires [wal_level](https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-WAL-LEVEL) set to `logical`. -Depending on where PostgreSQL server is hosted it can be done in different ways+Depending on where the PostgreSQL server is hosted, it can be done in different ways.  <div className="colwidths-given">@@ -51,9 +51,9 @@       <td> -Execute following query with superuser or user with `ALTER SYSTEM` privilege:+Execute the following query with a superuser or a user with `ALTER SYSTEM` privilege:  <blockquote> -```ini+```sql ALTER SYSTEM SET wal_level = logical; ```@@ -115,9 +115,9 @@ %postgres6% requires [Publication](https://www.postgresql.org/docs/current/logical-replication-publication.html#LOGICAL-REPLICATION-PUBLICATION) to be created and configured. -Login as user with `CREATE` privilege in the database and execute the following query:+Log in as a user with `CREATE` privilege in the database and execute the following query:  <blockquote> -```ini+```sqlsyntax CREATE PUBLICATION <publication name>; ```@@ -137,18 +137,18 @@ **For Postgres v15 and later** -In case of publications created for subset of table's columns, please add tables for replication+In case of publications created for a subset of table's columns, add tables for replication using [ADD_TABLE_WITH_COLUMNS](#label-postgres-connector-add-table-with-columns) procedure, specifying exactly the same set of columns. -If `ADD_TABLES` will be used, the connector will work, but following non-obvious side effects will occur:+If `ADD_TABLES` is used, the connector will work, but the following non-obvious side effects will occur:  <blockquote> -- in the destination database, columns that are not included in filter will be suffixed with `_DELETED`. All data replicated during snapshot phase will still be there.-- in case of adding more columns to the publication, table will result in `Permanently Failed` state, requiring restarting the replication.+- in the destination database, columns that are not included in the filter will be suffixed with `_DELETED`. All data replicated during snapshot phase will still be there.+- in case of adding more columns to the publication, the table will result in a `Permanently Failed` state, requiring restarting the replication.  </blockquote> -For more information see [ALTER PUBLICATION documentation](https://www.postgresql.org/docs/current/sql-alterpublication.html).+For more information, see [ALTER PUBLICATION documentation](https://www.postgresql.org/docs/current/sql-alterpublication.html).  ### Create replication slot@@ -158,5 +158,5 @@ the one specified in [ADD_DATA_SOURCE](#label-postgres-connector-add-data-source-6) procedure. -If the connector is not used anymore, Replication Slot must be removed to not accumulate data in PostgreSQL server.+If the connector is not used anymore, Replication Slot must be removed to avoid accumulating data in the PostgreSQL server.  <blockquote> 

--- ahttps://docs.snowflake.com/en/developer-guide/native-apps/tutorials/na-spcs-tutorial+++ bhttps://docs.snowflake.com/en/developer-guide/native-apps/tutorials/na-spcs-tutorial@@ -134,5 +134,5 @@ ## Create a Snowflake CLI connection for the tutorial -To run the %sf-cli% commands in this tutorial, you must setup a %sf-cli% connection for the tutorial.+To run the %sf-cli% commands in this tutorial, you must set up a %sf-cli% connection for the tutorial.  To create a connection, perform the following tasks:@@ -186,5 +186,5 @@ specifies the correct values for the role, database, and warehouse connection properties. -## Setup a project for the app+## Set up a project for the app  In the previous section, you set up a %sf-cli% connection for the tutorial.@@ -227,5 +227,5 @@ 1. Create a folder called `service` inside the `na-spcs-tutorial` folder. -   This folder contains the source code for the container-based service we are about to build and publish to Snowflake.+   This folder contains the source code for the container-based service you are about to build and publish to Snowflake.  2. To obtain the Docker files required for the tutorial, download the@@ -240,5 +240,5 @@ ### Verify the directory structure of your project -After create the project for your app and adding the files for the service and Docker container, the project+After creating the project for your app and adding the files for the service and Docker container, the project should have the following structure within the `na-spcs-tutorial` folder: @@ -414,5 +414,5 @@      as well as the project README that is visible in %sf-web-interface%.    - The `privileges` property allows a service to respond to public requests as well-     as to create its own compute pool. These properties are required for instantiating our service+     as to create its own compute pool. These properties are required for instantiating the service      in the next step of the tutorial. @@ -560,5 +560,5 @@    ``` -2. Run the `app_public.start_app` procedure we defined in the `setup_script.sql` file.+2. Run the `app_public.start_app` procedure defined in the `setup_script.sql` file.     ```sql@@ -566,5 +566,5 @@    ``` -   This procedure creates the compute pool, instantiate the service, and creates the service function.+   This procedure creates the compute pool, instantiates the service, and creates the service function.  3. Confirm the function was created by running the following:@@ -579,5 +579,5 @@  -4. To verify that the service has been created and healthy, run the following command:+4. To verify that the service has been created and is healthy, run the following command:     ```sql@@ -602,5 +602,5 @@    ``` -## Teardown the app and objects created in the tutorial+## Tear down the app and objects created in the tutorial  If you plan to perform the [](/developer-guide/native-apps/tutorials/na-upgrade-tutorial) after completing this tutorial,@@ -631,5 +631,5 @@    this command does not drop the application package because it contains versions. -3. To confirm that the compute pool was dropped run the following command again:+3. To confirm that the compute pool was dropped, run the following command again:     ```snowcli 

--- ahttps://docs.snowflake.com/en/release-notes/clients-drivers/snowflake-cli-2024+++ bhttps://docs.snowflake.com/en/release-notes/clients-drivers/snowflake-cli-2024@@ -65,7 +65,7 @@ - Removed the requirement for an existing requirements.txt file for Python code executed with the `snow git execute` command. Previously, the file must have existed, even if empty, for the command to succeed. - Removed the requirement for needing a privilege to create a table or schema to execute the `snow app version create` command if the schema and table already exist.-- Fixed an issue relating to configuration file updates when the `connection.toml` file exists, no longer incorrectly copying connections from `connections.toml` to `config.toml` files.+- Fixed an issue relating to configuration file updates when the `connections.toml` file exists, no longer incorrectly copying connections from `connections.toml` to `config.toml` files. - Fixed an issue where the `snow connection generate-jwt` command failed with keys without a passphrase.-- Fixed a Windows permissions error for file created by %sf-cli% when the owner is part of a custom group with granted default permissions.+- Fixed a Windows permissions error for files created by %sf-cli% when the owner is part of a custom group with granted default permissions.  ## Version 3.1.0 (October 25, 2024)@@ -156,5 +156,5 @@ - Modified the behavior of the following Snowpark commands:   - The `snow snowpark build` creates a `.zip` file for each specified artifact that is a directory. Non-Anaconda dependencies are packaged once as `dependencies.zip`.-  - The `snow snowpark deploy` uploads all artifacts created during build step. The `dependencies.zip` file is upload once to every Snowpark stage specified in project definition.+  - The `snow snowpark deploy` uploads all artifacts created during build step. The `dependencies.zip` file is uploaded once to every Snowpark stage specified in the project definition.   - The `snow snowpark package` commands no longer fallback to Anaconda Channel metadata when fetching available packages information fails. @@ -195,5 +195,5 @@  - Fixed an issue where the `git execute` command did not correctly handle upper case in directory names.-- Fixed an issue where the `snow git setup` did note correctly handle fully qualified repository names.+- Fixed an issue where the `snow git setup` did not correctly handle fully qualified repository names. - Fixed the `snow git setup` command behavior in cases where API integration, or a secret with a default name, already exists. - Fixed an issue where the `snow snowpark package create` command created empty zip files when a package name contained capital letters.@@ -215,5 +215,5 @@  - Fixed an issue with invalid return values for `snow snowpark list`, `snow snowpark describe`, and `snow snowpark drop` commands.-- The `snow app run` command now shows warning returned by Snowflake.+- The `snow app run` command now shows warnings returned by Snowflake.  ## Version 2.7.0 (August 2, 2024)@@ -259,5 +259,5 @@ - Added the `snow object create` command. - Added support for a `title` field in Streamlit definition in the `snowflake.yml` project file.-- Added the `--auto-compress` flag to the `snow stage copy` command to enable gzip compression files during upload.+- Added the `--auto-compress` flag to the `snow stage copy` command to enable gzip compression of files during upload. - Added a new `native_app.application.post_deploy` section to `snowflake.yml` schema to execute actions after the application has been deployed via `snow app run`.   - Added the `sql_script` hook type to run SQL scripts with template support.@@ -273,5 +273,5 @@     - Variables from the `env` section of project definition file. -- The `snow sql` command now show query text before executing it.+- The `snow sql` command now shows query text before executing it.  ### Bug fixes@@ -298,5 +298,5 @@   - Added the `snow app bundle` command that prepares a local folder in the project directory with artifacts to upload to a stage as part of creating a Snowflake Native App. -    %native-app% projects can optionally generate CREATE FUNCTION and CREATE PROCEDURE declarations ins setup scripts from Snowpark Python code that includes decorators (such as `@sproc` and `@udf`).+    %native-app% projects can optionally generate CREATE FUNCTION and CREATE PROCEDURE declarations in setup scripts from Snowpark Python code that includes decorators (such as `@sproc` and `@udf`).    - Added the `snow app validate` command that validates the SQL in the setup script of a Snowflake Native App for valid syntax, invalid object references, and best practices.@@ -319,5 +319,5 @@ - Deploying functions or procedures with the `--replace` parameter now copies all grants. - Fixed MFA caching.-- Fixed issues with `DeprecationWarning` and `SyntaxWarning` caused to invalid escape sequences.+- Fixed issues with `DeprecationWarning` and `SyntaxWarning` caused by invalid escape sequences. - Improved error messages in the `snow spcs image-registry login` when Docker is not installed. - Improved detection of conflicts between artifact rules for %native-app% projects@@ -426,5 +426,5 @@ - Added support for fully qualified names (`database.schema.name`) in the Streamlit project definition `name` parameter. - Added support for fully qualified image repository names in `spcs image-repository` commands.-- Added the `--if-not-exists option` option to the `snow spcs service create` and `snow spcs compute-pool create` commands.+- Added the `--if-not-exists` option to the `snow spcs service create` and `snow spcs compute-pool create` commands. - Added the `--replace` and `--if-not-exists` options for the `snow spcs image-repository create` command. - Added support for Snowflake Connector for Python diagnostic reports. 

--- ahttps://docs.snowflake.com/en/migrations/aim-for-datawarehouses/code-conversion/function-references/sql-server+++ bhttps://docs.snowflake.com/en/migrations/aim-for-datawarehouses/code-conversion/function-references/sql-server@@ -330,5 +330,5 @@ ```sql :force:-VIEW_OBJECT_ID_UDF(NAME VARCHAR)+FUNCTION_OBJECT_ID_UDF(NAME VARCHAR) ``` @@ -443,5 +443,5 @@         <name type="VARCHAR">David</name>     </employee>-<employees>+</employees> ``` @@ -849,5 +849,5 @@ ### Definition -This user-defined function (UDF) determines whether an expression is a valid numeric type.+This user-defined function (UDF) returns a sequential integer expression to replicate the behavior of an IDENTITY column.  ```sql@@ -1019,5 +1019,5 @@ `SECOND_DATE` TIMESTAMP_TZ -The second date to be subtracted to.+The second date to be subtracted from.  ### Returns@@ -1268,5 +1268,5 @@ ### Definition -This user-defined function (UDF) determines the windows group membership by examining an access token.+This user-defined function (UDF) determines the Windows group membership by examining an access token.  ```sql@@ -1283,5 +1283,5 @@ ### Returns -Returns a boolean expression on true when the current user is a member of the role; otherwise returns false.+Returns a boolean expression that is true when the current user is a member of the role; otherwise returns false.  ### Usage example@@ -1358,5 +1358,5 @@ ```sql :force:-STR_UDF(FLOAT_EXPR FLOAT, FORMAT VARCHAR)+STR_UDF(FLOAT_EXPR FLOAT) ``` @@ -1673,5 +1673,5 @@ ```sql :force:-SELECT PARSENAME_UDF('Test_A.Test_B.Test_C]', 2);+SELECT PARSENAME_UDF('Test_A.Test_B.Test_C', 2); ``` @@ -1800,5 +1800,5 @@ ### Definition -This user-defined function (UDF) retrieves the WEEK_START configuration, which is equivalent to the @@FIRSTDATE function. To maintain consistency across platforms, ensure the [WEEK_START](https://docs.snowflake.com/en/sql-reference/parameters#week-start) parameter matches the DATEFIRST setting in Transact-SQL.+This user-defined function (UDF) retrieves the WEEK_START configuration, which is equivalent to the @@DATEFIRST function. To maintain consistency across platforms, ensure the [WEEK_START](https://docs.snowflake.com/en/sql-reference/parameters#week-start) parameter matches the DATEFIRST setting in Transact-SQL.  ```sql@@ -1833,5 +1833,5 @@ ### Definition -This user-defined function (UDF) gets the day of the week as a number (1-7) To ensure the consistency across platforms, please set the [WEEK_START](https://docs.snowflake.com/en/sql-reference/parameters#week-start) parameter to the same value as the DATEFIRST setting in Transact-SQL.+This user-defined function (UDF) gets the day of the week as a number (1-7). To ensure consistency across platforms, please set the [WEEK_START](https://docs.snowflake.com/en/sql-reference/parameters#week-start) parameter to the same value as the DATEFIRST setting in Transact-SQL.  ```sql 

--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/mysql/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/mysql/setup@@ -264,9 +264,9 @@   connectors on Small only when each source is genuinely light. - Moderate workload (approximately 1,000 to 5,000 events per second, hundreds-  of actively changing tables): a Medium runtime, typically running 5 to 8+  of actively changing tables): a Medium runtime can typically host 5 to 8   connectors. - Heavy workload (approximately 5,000 to 15,000 events per second, hundreds to-  low thousands of actively changing tables): a Large runtime, typically-  running 15 or more connectors. If you want a smaller blast radius, split+  low thousands of actively changing tables): a Large runtime can typically host+  15 or more connectors. If you want a smaller blast radius, split   across two Medium runtimes instead. @@ -545,5 +545,5 @@   BYOC deployments must have previously configured   [runtime roles](#label-deployment-byoc-setup-runtime-role) to use SNOWFLAKE_MANAGED.-- **BYOC:** Alternatively BYOC can use KEY_PAIR as the value for authentication strategy.+- **BYOC**: Alternatively, BYOC can use KEY_PAIR as the value for the authentication strategy.  </td>@@ -557,5 +557,5 @@  - **SNOWFLAKE_MANAGED** Authentication Strategy: Must be blank.-- **KEY_PAIR**: Snowflake account name formatted as [organization-name]-[account-name] where data is persisted.+- **KEY_PAIR**: Snowflake account name formatted as [organization-name]-[account-name].  </td>@@ -602,5 +602,5 @@ When using: -- **Session token authentication strategy**: The private key file must be blank.+- **SNOWFLAKE_MANAGED** Authentication Strategy: The private key file must be blank. - **KEY_PAIR**: Upload the file that contains the RSA private key used for authentication to Snowflake,   formatted according to PKCS8 standards and including standard PEM headers and footers.@@ -615,5 +615,5 @@       <td> -When using+When using:  - **SNOWFLAKE_MANAGED** Authentication Strategy: Must be blank.@@ -627,9 +627,9 @@       <td> -When using+When using:  - **SNOWFLAKE_MANAGED** Authentication Strategy: Use Snowflake Role assigned to the runtime or child role granted to this Snowflake Role.   You can find your runtime Snowflake Role in the Openflow UI, by expanding the **More Options [⋮]** button for your runtime and selecting **Set Snowflake role**.-- **KEY_PAIR** Authentication Strategy: Use a valid role configured for your service user.+- **KEY_PAIR**: Use a valid role configured for your service user.  </td>@@ -640,5 +640,5 @@       <td> -When using+When using:  - **SNOWFLAKE_MANAGED** Authentication Strategy: Must be blank. 

--- ahttps://docs.snowflake.com/en/migrations/aim-for-datawarehouses/manual-migration/renaming-feature+++ bhttps://docs.snowflake.com/en/migrations/aim-for-datawarehouses/manual-migration/renaming-feature@@ -5,5 +5,5 @@ Renaming objects during a database migration process is something that a lot of users need to do. For this reason, SnowConvert CLI enables the Renaming feature to allow defining new names for the following types of user-defined objects: -This feature is supported for Teradata, Sql Server and Redshift **ONLY**.+This feature is supported for Teradata, SQL Server, and Redshift **ONLY**.  - Schemas@@ -17,9 +17,9 @@ The renaming feature will apply to both the object definition and the object's uses. -These objects are usually qualified within a schema or a database, so, depending on the Database platform, the object `Table1` might be referenced simply as `Table1`, as `MySchema.Table1` or as `MyDatabase.MySchema.Table1`. It is **essential** to fully qualify each object in the renaming file to avoid ambiguity.+These objects are usually qualified within a schema or a database, so, depending on the database platform, the object `Table1` might be referenced simply as `Table1`, as `MySchema.Table1` or as `MyDatabase.MySchema.Table1`. It is **essential** to fully qualify each object in the renaming file to avoid ambiguity.  The new object names are specified via a .json file with the following format. -Note that this example contains a "Macros" section, this is a **Teradata** specific element, and may vary depending on the specified language.+Note that this example contains a "Macros" section. This is a **Teradata-specific** element and may vary depending on the specified language.  ```json@@ -86,5 +86,5 @@ ## Usage -In order to use the renaming feature you have to execute the SnowConvert CLI with the following argument `--RenamingFile` and provide the path to the .json file containing the renaming information. An example of the command can look like this:+To use the renaming feature, you have to execute the SnowConvert CLI with the following argument `--RenamingFile` and provide the path to the .json file containing the renaming information. An example of the command can look like this:  > snowct.exe -i "somePath/input" -o "somePath/output" --RenamingFile "somePath/renamings.json"@@ -92,5 +92,5 @@ ### Renaming modes -Notice there are two fields for each kind of object: `"Tables"` and `"TablesRegex"`_,_ `"Views"` and `"ViewsRegex"`, and so on. This is because there are two ways in which renamings can be specified.+Notice there are two fields for each kind of object: `"Tables"` and `"TablesRegex"`, `"Views"` and `"ViewsRegex"`, and so on. This is because there are two ways in which renamings can be specified.  #### Object by object (line by line)@@ -108,5 +108,5 @@ ``` -This information has to be specified in the `"Tables"`_,_ `"Views"`_,_ `"Procedures"`_,_ `"Macros"` _and_ `"Functions"` sections of the .json file and each line must be separated with a comma. Let's take a look at an example:+This information has to be specified in the `"Tables"`, `"Views"`, `"Procedures"`, `"Macros"`, and `"Functions"` sections of the .json file and each line must be separated with a comma. Let's take a look at an example:  **TableExample1**@@ -120,9 +120,9 @@ ``` -The above sample is saying that the only three tables in the whole workload to be renamed are the ones called "_Table1_", "_Table2_" and "_Table3_", all located inside the "Schema1" schema; they must be renamed to "_SF_Table1", "SF_\__Table2"_ and _"SF_\__Table3",_ respectively; and finally, they will be located under the _"SF_Schema1_" schema in Snowflake.+The above sample is saying that the only three tables in the whole workload to be renamed are the ones called "Table1", "Table2", and "Table3", all located inside the "Schema1" schema; they must be renamed to "SF_Table1", "SF_Table2", and "SF_Table3", respectively; and finally, they will be located under the "SF_Schema1" schema in Snowflake.  #### Regular expressions -If there is a need to rename multiple objects in the same way, the feature also allows regular expressions to define patterns to apply to objects of the same kind. Two lines are required to specify each renaming, the first line is `"RegexExpr"` which is the matching expression and the second line is the `"RegexReplace"` which is the replacing expression. This information has to be provided in the `"TablesRegex"`_,_ `"ViewsRegex"`_,_ `"ProceduresRegex"`_,_ `"MacrosRegex"` and `"FunctionsRegex"` sections of the .json file. So, the previous example can also be written in the following manner, using the regular expression feature.+If there is a need to rename multiple objects in the same way, the feature also allows regular expressions to define patterns to apply to objects of the same kind. Two lines are required to specify each renaming, the first line is `"RegexExpr"` which is the matching expression and the second line is the `"RegexReplace"` which is the replacing expression. This information has to be provided in the `"TablesRegex"`, `"ViewsRegex"`, `"ProceduresRegex"`, `"MacrosRegex"`, and `"FunctionsRegex"` sections of the .json file. So, the previous example can also be written in the following manner, using the regular expression feature.  **TableExample2**@@ -137,5 +137,5 @@ ``` -The only difference is that this way applies to all tables located within the "Schema1" schema. The regex expression would match all tables defined within the "Schema1" schema and will create a capturing group with everything after the dot. The regex replace will move the tables to the "SF_Schema1" schema and will add the "SF\_" prefix to all tables found referencing the first group created ($1) in the regex expression.+The only difference is that this way applies to all tables located within the "Schema1" schema. The regular expression would match all tables defined within the "Schema1" schema and will create a capturing group with everything after the dot. The regex replace will move the tables to the "SF_Schema1" schema and will add the "SF\_" prefix to all tables found referencing the first group created ($1) in the regex expression.  #### Renaming priority@@ -234,3 +234,3 @@ ``` -Notice how all the references to "CLIENT" are renamed to "USER"+Notice how all the references to "CLIENT" are renamed to "USER". 

--- ahttps://docs.snowflake.com/en/user-guide/cleanrooms/ml-jobs+++ bhttps://docs.snowflake.com/en/user-guide/cleanrooms/ml-jobs@@ -7,10 +7,10 @@ This feature is not available in the People's Republic of China. -  - [](/user-guide/cleanrooms/resources-code-specs) --  [](/user-guide/cleanrooms/spec-code-spec) --  [](/user-guide/cleanrooms/collaboration-api-reference) --  [](/user-guide/cleanrooms/activation) --  [](/user-guide/cleanrooms/collab-lookalike-modeling) --  [](/user-guide/cleanrooms/collab-mljobs-rmn-hpo)+  - [](/user-guide/cleanrooms/resources-code-specs)+  - [](/user-guide/cleanrooms/spec-code-spec)+  - [](/user-guide/cleanrooms/collaboration-api-reference)+  - [](/user-guide/cleanrooms/activation)+  - [](/user-guide/cleanrooms/collab-lookalike-modeling)+  - [](/user-guide/cleanrooms/collab-mljobs-rmn-hpo)  ## Overview@@ -68,5 +68,5 @@   installed. - The analysis runner must have a compute pool available for running ML Jobs. For GPU-accelerated-  workloads, a GPU compute pool is required. GPU availability varies by region — see+  workloads, a GPU compute pool is required. GPU availability varies by region: see   [Compute pool errors](/user-guide/cleanrooms/v2/troubleshooting#ml-jobs) in the troubleshooting guide. @@ -197,5 +197,5 @@ ### 2. Set up the compute pool -ML Jobs run in containers on a compute pool instead of a warehouse. Create a compute pool for the installed clean room+ML Jobs runs in containers on a compute pool instead of a warehouse. Create a compute pool for the installed clean room application: @@ -437,5 +437,5 @@ high memory CPU node or a large GPU node. -**Code change — replace raw XGBoost with the distributed trainer:**+**Code change: replace raw XGBoost with the distributed trainer:**  ```python@@ -457,5 +457,5 @@ ``` -**Template change — increase `num_instances` for multi-node:**+**Template change: increase `num_instances` for multi-node:**  ```yaml 

--- ahttps://docs.snowflake.com/en/sql-reference/account-usage+++ bhttps://docs.snowflake.com/en/sql-reference/account-usage@@ -20,5 +20,5 @@ with the following differences: -- Records for dropped objects included in each view.+- Records for dropped objects are included in each view. - Longer retention time for historical usage data. - Data latency.@@ -78,5 +78,5 @@     <tr>       <td>Retention of historical data</td>-      <td>1 Year</td>+      <td>1 year</td>       <td>From 7 days to 6 months (varies by view/table function)</td>     </tr>@@ -92,10 +92,10 @@ additional `DELETED` column that displays the timestamp when the object was dropped. -In addition, because objects can be dropped and recreated with the same name, to differentiate between objects records that have the+In addition, because objects can be dropped and recreated with the same name, to differentiate between object records that have the same name, the account usage views include ID columns, where appropriate, that display the internal IDs generated and assigned to each record by the system. -If a column for an object name (e.g. the `TABLE_NAME` column) is NULL, that object has been dropped. In this case, the-columns for the names and IDs of the parent objects (e.g. the `DATABASE_NAME` and `SCHEMA_NAME` columns) are also+If a column for an object name (for example, the `TABLE_NAME` column) is NULL, that object has been dropped. In this case, the+columns for the names and IDs of the parent objects (for example, the `DATABASE_NAME` and `SCHEMA_NAME` columns) are also NULL. @@ -416,5 +416,5 @@       <td>[CORTEX_ANALYST_USAGE_HISTORY](/sql-reference/account-usage/cortex_analyst_usage_history)</td>       <td>Historical</td>-      <td>One hour</td>+      <td>1 hour</td>       <td></td>       <td>Data retained for 1 year.</td>@@ -502,5 +502,5 @@       <td>3 hours</td>       <td>Enterprise Edition (or higher)</td>-      <td>Data is retained for one year.</td>+      <td>Data retained for 1 year.</td>     </tr>     <tr>@@ -1207,5 +1207,5 @@       <td>[SNOWPARK_CONTAINER_SERVICES_HISTORY](/sql-reference/account-usage/snowpark_container_services_history)</td>       <td>Historical</td>-      <td>3 hour</td>+      <td>3 hours</td>       <td></td>       <td>Data retained for 1 year.</td>@@ -1526,5 +1526,5 @@ </blockquote> -A user with that is granted the `customrole1` role can query a view as follows:+A user who is granted the `customrole1` role can query a view as follows:  <blockquote>@@ -1544,5 +1544,5 @@ ### ACCOUNT_USAGE schema SNOWFLAKE database roles -In addition, you can grant finer control to accounts using SNOWFLAKE Database roles.+In addition, you can grant finer control to accounts using SNOWFLAKE database roles. For more information on database roles, see [database roles](#label-access-control-considerations-database-roles).  

--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/postgres/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/postgres/setup@@ -351,9 +351,9 @@   connectors on Small only when each source is genuinely light. - Moderate workload (approximately 1,000 to 5,000 events per second, hundreds-  of actively changing tables): a Medium runtime, typically running 5 to 8+  of actively changing tables): a Medium runtime can typically host 5 to 8   connectors. - Heavy workload (approximately 5,000 to 15,000 events per second, hundreds to-  low thousands of actively changing tables): a Large runtime, typically-  running 15 or more connectors. If you want a smaller blast radius, split+  low thousands of actively changing tables): a Large runtime can typically host+  15 or more connectors. If you want a smaller blast radius, split   across two Medium runtimes instead. @@ -644,5 +644,5 @@   BYOC deployments must have previously configured   [runtime roles](#label-deployment-byoc-setup-runtime-role) to use SNOWFLAKE_MANAGED.-- **BYOC:** Alternatively BYOC can use KEY_PAIR as the value for authentication strategy.+- **BYOC**: Alternatively, BYOC can use KEY_PAIR as the value for the authentication strategy.  </td>@@ -656,5 +656,5 @@  - **SNOWFLAKE_MANAGED** Authentication Strategy: Must be blank.-- **KEY_PAIR**: Snowflake account name formatted as [organization-name]-[account-name] where data is persisted.+- **KEY_PAIR**: Snowflake account name formatted as [organization-name]-[account-name].  </td>@@ -742,5 +742,5 @@  - **SNOWFLAKE_MANAGED** Authentication Strategy: Must be blank.-- **KEY_PAIR**: Provide the user name used to connect to the Snowflake instance.+- **KEY_PAIR**: Provide the username used to connect to the Snowflake instance.  </td>@@ -816,5 +816,5 @@ Select tables either by name or by Regex. If you use both, all matching tables from either option will be included. -Tables being sub-partitions are always excluded from ingestion. See+Sub-partition tables are always excluded from ingestion. See [](#label-postgres-connector-replicate-partitioned-table) for more information. @@ -831,5 +831,5 @@ Select tables either by name or by Regex. If you use both, all matching tables from either option will be included. -Tables being sub-partitions are always excluded from ingestion. See+Sub-partition tables are always excluded from ingestion. See [](#label-postgres-connector-replicate-partitioned-table) for more information. @@ -1157,5 +1157,5 @@  If you have multiple connector instances replicating from the same PostgreSQL database,-each instance will create its own uniquely-named replication slot. When dropping a replication slot manually, make sure+each instance will create its own uniquely named replication slot. When dropping a replication slot manually, make sure it's the right one. You can see which replication slot is used by a given connector instance by checking the state of the `CaptureChangePostgreSQL` processor. @@ -1355,4 +1355,4 @@ ## Run the flow -1. Right-click on the plane and select **Enable all Controller Services**.+1. Right-click on the canvas and select **Enable all Controller Services**. 2. Right-click on the imported process group and select **Start**. The connector starts the data ingestion. 

--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-task+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-task@@ -12,5 +12,5 @@ <dd> -[](/sql-reference/sql/alter-task) , [](/sql-reference/sql/drop-task) , [](/sql-reference/sql/show-tasks) , [](/sql-reference/sql/desc-task)+[](/sql-reference/sql/alter-task), [](/sql-reference/sql/drop-task), [](/sql-reference/sql/show-tasks), [](/sql-reference/sql/desc-task)  </dd>@@ -143,5 +143,5 @@ - Procedural logic using [Snowflake Scripting](/developer-guide/snowflake-scripting/index) -The SQL code is executed when the task runs. Verify that the `{sql}` executes as expected before using it in a task.+The SQL code is executed when the task runs. Verify that the `sql` executes as expected before using it in a task.  </dd>@@ -186,5 +186,5 @@ CREATE OR REPLACE *&lt;object&gt;* statements are atomic. That is, when an object is replaced, the old object is deleted and the new object is created in a single transaction. -  - Tasks with large definitions can cause errors. If you experience an error due to task size, try using stored procedure or making your task definition less complex.+  - Tasks with large definitions can cause errors. If you experience an error due to task size, try using a stored procedure or making your task definition less complex.    When you replace a task, any ongoing task run is completed.@@ -595,5 +595,5 @@ <dd> -Specifies the desired task completion time. This parameter only applies to serverless tasks. This property is only set on a Task.+Specifies the desired task completion time. This parameter only applies to serverless tasks. This property is only set on a task.  This parameter is required when you create serverless [](/user-guide/tasks-triggered).@@ -609,5 +609,5 @@ <dd> -Specifies the minimum allowed warehouse size for the serverless task. This parameter only applies to serverless tasks. This parameter can be specified on the Task, Schema, Database, or Account. Precedence follows the standard parameter hierarchy.+Specifies the minimum allowed warehouse size for the serverless task. This parameter only applies to serverless tasks. This parameter can be specified on the task, schema, database, or account. Precedence follows the standard parameter hierarchy.  Values: Minimum `XSMALL`, Maximum `XXLARGE`. Values are consistent with [WAREHOUSE_SIZE values](/sql-reference/sql/create-warehouse).@@ -623,5 +623,5 @@ <dd> -Specifies the maximum allowed warehouse size for the serverless task. This parameter only applies to serverless tasks. This parameter can be specified on the Task, Schema, Database, or Account. Precedence follows the standard parameter hierarchy.+Specifies the maximum allowed warehouse size for the serverless task. This parameter only applies to serverless tasks. This parameter can be specified on the task, schema, database, or account. Precedence follows the standard parameter hierarchy.  Values: Minimum `XSMALL`, Maximum `XXLARGE`.@@ -629,7 +629,7 @@ Also supports the notation: X2LARGE. -Default: *XXLARGE*--If both SERVERLESS_TASK_MIN_STATEMENT_SIZE and SERVERLESS_TASK_MAX_STATEMENT_SIZE are specified, SERVERLESS_TASK_MIN_STATEMENT_SIZE must be less than or equal to SERVERLESS_TASK_MAX_STATEMENT_SIZE. SERVERLESS_TASK_MAX_STATEMENT_SIZE must be equal to or greater than USER_TASK_MANAGED_INITIAL_WAREHOUSE_SIZE+Default: `XXLARGE`++If both SERVERLESS_TASK_MIN_STATEMENT_SIZE and SERVERLESS_TASK_MAX_STATEMENT_SIZE are specified, SERVERLESS_TASK_MIN_STATEMENT_SIZE must be less than or equal to SERVERLESS_TASK_MAX_STATEMENT_SIZE. SERVERLESS_TASK_MAX_STATEMENT_SIZE must be equal to or greater than USER_TASK_MANAGED_INITIAL_WAREHOUSE_SIZE.  </dd>@@ -743,5 +743,5 @@ - All limitations of the [](/sql-reference/sql/alter-task) command apply. - A task cannot be resumed or suspended using the CREATE OR ALTER TASK command. To resume or suspend a task, use the ALTER TASK command.-- Setting or unsetting a tag is not supported; however existing tags are *not* altered by a CREATE OR ALTER statement and remain unchanged.+- Setting or unsetting a tag is not supported; however, existing tags are *not* altered by a CREATE OR ALTER statement and remain unchanged.  ## Examples 

--- ahttps://docs.snowflake.com/en/developer-guide/native-apps/event-old+++ bhttps://docs.snowflake.com/en/developer-guide/native-apps/event-old@@ -41,5 +41,5 @@  - [View the log and trace level](#label-nativeapps-provider-logging-view-level-old).-- [View the logs and events in the event table](#label-nativeapps-provider-logging-view-logs-and-events).+- [View the logs and events in the event table](#label-nativeapps-provider-logging-view-logs-and-events-old).  <a id="label-nativeapps-provider-logging-considerations-old"></a>@@ -51,6 +51,6 @@ - Providers are responsible for all costs associated with event sharing on the provider side, including data   ingestion and storage.-- Providers must have [an account to store shared events](#label-nativeapps-provider-logging-configure-event-account)-  in each region where you want to support event sharing.+- Providers must have [an account to store shared events](#label-nativeapps-provider-logging-configure-event-account-old)+  in each region where they want to support event sharing. - Providers must define the default log level and trace level for an app in the manifest file. @@ -176,7 +176,7 @@ You must use an [organization administrator role](/user-guide/organization-administrators) to call this function. -### Un-set an account as the events account--To unset an account to be the events account for a region, call the SYSTEM$UNSET_EVENT_SHARING_ACCOUNT_FOR_REGION system function:+### Unset an account as the events account++To unset an account as the events account for a region, call the SYSTEM$UNSET_EVENT_SHARING_ACCOUNT_FOR_REGION system function:  ```sqlsyntax@@ -221,5 +221,5 @@ This system function returns a string in JSON format containing a list of event accounts within the organization. Because the metadata takes some time to propagate to all regions, this function might experience some delay when-showing latest events account after the user set/unset an events account for the organization.+showing the latest events account after the user sets or unsets an events account for the organization.  <a id="label-nativeapps-provider-logging-view-level-old"></a>@@ -234,5 +234,5 @@ ``` -Use the [](/sql-reference/sql/show-versions) command to view the logging level the app versions defined in an application+Use the [](/sql-reference/sql/show-versions) command to view the logging level of the app versions defined in an application package, as shown in the following example: @@ -274,5 +274,5 @@  To protect consumer information, the following fields from the `RESOURCE_ATTRIBUTES` column are-not shared with provider:+not shared with the provider:  - snow.database.id@@ -334,5 +334,5 @@ ### Determine if event sharing is enabled using the %native-app-perms% -The %native-app-perms% provides the following functions to determine if even sharing is enabled in+The %native-app-perms% provides the following functions to determine if event sharing is enabled in a consumer account:  

--- ahttps://docs.snowflake.com/en/user-guide/tables-auto-reclustering+++ bhttps://docs.snowflake.com/en/user-guide/tables-auto-reclustering@@ -76,8 +76,8 @@ ### Optimal efficiency -With Automatic Clustering, Snowflake internally manages the state of clustered tables, as well as the resources (servers, memory, etc.) used for all automated clustering+With Automatic Clustering, Snowflake internally manages the state of clustered tables, as well as the resources (servers, memory, and so on) used for all automated clustering operations. This allows Snowflake to dynamically allocate resources as needed, resulting in the most efficient and effective reclustering. -Also, Automatic Clustering does not perform any unnecessary reclustering. Reclustering is triggered only if/when the table would benefit from the operation.+Also, Automatic Clustering does not perform any unnecessary reclustering. Reclustering is triggered only when the table would benefit from the operation.  ## Enabling Automatic Clustering for a table@@ -87,5 +87,5 @@  However, the rule does not apply to tables created by cloning ([CREATE TABLE ... CLONE ...](/sql-reference/sql/create-clone))-from a source table that has clustering keys. The new table starts with Automatic Clustering suspended – even if Automatic+from a source table that has clustering keys. The new table starts with Automatic Clustering suspended, even if Automatic Clustering for the source table is not suspended. (This is true whether the `CLONE` command cloned the table, the schema containing the table, or the database containing the table.)@@ -93,8 +93,8 @@ Before you define a clustering key for a table, consider the following conditions, which may cause reclustering activity (and corresponding credit charges): -- The table is not optimally-clustered. For more details, see [](/user-guide/tables-clustering-micropartitions).+- The table is not optimally clustered. For more details, see [](/user-guide/tables-clustering-micropartitions). - The clustering key on the table has changed. -As such, we recommend starting with one or two selected tables and assessing the impact of Automatic Clustering on these tables. Once you are comfortable/familiar with how+As such, we recommend starting with one or two selected tables and assessing the impact of Automatic Clustering on these tables. Once you are comfortable or familiar with how Automatic Clustering performs reclustering, you can then define clustering keys for your other tables. @@ -169,5 +169,5 @@ Before you resume Automatic Clustering on a clustered table, consider the following conditions, which may cause reclustering activity (and corresponding credit charges): -- The table is not optimally-clustered (e.g. significant DML has been performed on the table since it was last reclustered).+- The table is not optimally clustered (for example, significant DML has been performed on the table since it was last reclustered). - The clustering key on the table has changed. @@ -206,5 +206,5 @@  As with Clustering Classic, changing a clustering key triggers a one-time clustering cost. For Optima Clustering, that one-time cost is-based on the existing table size at the time of the key change. Snowflake applies the Overlap Factor as if the whole table were newly+based on the existing table size at the time of the key change. Snowflake applies the overlap factor as if the whole table were newly written data, so a small key change that doesn't require rewriting much data results in minimal charges. @@ -223,5 +223,5 @@  </dd>-<dt>Storage Costs</dt>+<dt>Storage costs</dt> <dd> @@ -246,6 +246,6 @@  After enabling or resuming Automatic Clustering on a clustered table, if it has been a while since the table was reclustered, you may-experience reclustering activity (and corresponding credit charges) as Snowflake brings the table to an optimally-clustered state. Once-the table is optimally-clustered, the reclustering activity will drop off.+experience reclustering activity (and corresponding credit charges) as Snowflake brings the table to an optimally clustered state. Once+the table is optimally clustered, the reclustering activity will drop off.  Likewise, defining a clustering key on an existing table or changing the clustering key on a clustered table may trigger reclustering and 

--- ahttps://docs.snowflake.com/en/developer-guide/declarative-sharing/command-reference+++ bhttps://docs.snowflake.com/en/developer-guide/declarative-sharing/command-reference@@ -71,5 +71,5 @@ ALTER APPLICATION PACKAGE <name> [ ADD LIVE VERSION-| ADD VERSION FROM @STAGE/path+| ADD VERSION FROM @/<path> | BUILD | COMMIT@@ -153,11 +153,12 @@ </dl> -`COMMENT = 'string_literal'`--<blockquote>+<dl>+<dt>`COMMENT = 'string_literal'`</dt>+<dd>  Optional: Adds a comment or overwrites an existing comment for the app version. This comment is displayed in SHOW APPLICATION PACKAGES. -</blockquote>+</dd>+</dl>  ### Access control requirements@@ -208,7 +209,7 @@   ``` -- After adding a live version of the app end and editing it, stop editing and restore to the last committed version:-  ```sql-  ALTER APPLICATION PACKAGE market_data_app ABORT LIVE VERSION+- After adding a live version of the app and editing it, stop editing and restore to the last committed version:+  ```sql+  ALTER APPLICATION PACKAGE market_data_app ABORT LIVE VERSION;   ``` @@ -225,5 +226,5 @@ ### Access control requirements -This command requires a role with the OWNER privilege for the installed app.+This command requires a role with the OWNERSHIP privilege for the installed app.  ### Syntax 

--- ahttps://docs.snowflake.com/en/sql-reference/account-usage/query_history+++ bhttps://docs.snowflake.com/en/sql-reference/account-usage/query_history@@ -95,5 +95,5 @@       <td>`query_type`</td>       <td>VARCHAR</td>-      <td>DML, query, etc.  If the query failed, then the query type may be UNKNOWN.</td>+      <td>DML, query, and so on. If the query failed, then the query type may be UNKNOWN.</td>       <td></td>     </tr>@@ -167,5 +167,5 @@       <td>`error_code`</td>       <td>NUMBER</td>-      <td>Error code, if the query returned an error</td>+      <td>Error code, if the query returned an error.</td>       <td>%cm%</td>     </tr>@@ -179,5 +179,5 @@       <td>`start_time`</td>       <td>TIMESTAMP_LTZ</td>-      <td>Statement start time (in the local time zone)</td>+      <td>Statement start time (in the local time zone).</td>       <td>%cm%</td>     </tr>@@ -209,5 +209,5 @@       <td>`bytes_written`</td>       <td>NUMBER</td>-      <td>Number of bytes written (e.g. when loading into a table).</td>+      <td>Number of bytes written (for example, when loading into a table).</td>       <td></td>     </tr>@@ -215,5 +215,5 @@       <td>`bytes_written_to_result`</td>       <td>NUMBER</td>-      <td>Number of bytes written to a result object.  For example, `SELECT * FROM ...` would produce a set of results in tabular format representing each field in the selection.  <br /> <br /> In general, the results object represents whatever is produced as a result of the query, and `bytes_written_to_result` represents the size of the returned result.</td>+      <td>Number of bytes written to a result object.  For example, `SELECT * FROM ...` would produce a set of results in tabular format representing each field in the selection. <br /> <br /> In general, the results object represents whatever is produced as a result of the query, and `bytes_written_to_result` represents the size of the returned result.</td>       <td></td>     </tr>@@ -293,5 +293,5 @@       <td>`compilation_time`</td>       <td>NUMBER</td>-      <td>Compilation time (in milliseconds)</td>+      <td>Compilation time (in milliseconds).</td>       <td>%cm%</td>     </tr>@@ -299,5 +299,5 @@       <td>`execution_time`</td>       <td>NUMBER</td>-      <td>Execution time (in milliseconds)</td>+      <td>Execution time (in milliseconds).</td>       <td>%cm%</td>     </tr>@@ -533,5 +533,5 @@       <td>`user_database_id`</td>       <td>VARCHAR</td>-      <td>When the value in the `user_type` column is SNOWFLAKE_SERVICE, it specifies the internal, Snowflake-generated identifier for the service's database; otherwise, it's NULL</td>+      <td>When the value in the `user_type` column is SNOWFLAKE_SERVICE, it specifies the internal, Snowflake-generated identifier for the service's database; otherwise, it's NULL.</td>       <td></td>     </tr>@@ -545,5 +545,5 @@       <td>`user_schema_id`</td>       <td>VARCHAR</td>-      <td>When the value in the _user_type_ column is SNOWFLAKE_SERVICE, it specifies the internal, Snowflake-generated identifier for the service's schema; otherwise, it's NULL.</td>+      <td>When the value in the `user_type` column is SNOWFLAKE_SERVICE, it specifies the internal, Snowflake-generated identifier for the service's schema; otherwise, it's NULL.</td>       <td></td>     </tr> 

--- ahttps://docs.snowflake.com/en/user-guide/tutorials/script-data-load-transform-json+++ bhttps://docs.snowflake.com/en/user-guide/tutorials/script-data-load-transform-json@@ -6,10 +6,10 @@  - Store JSON objects natively in a VARIANT type column (as shown in [](/user-guide/tutorials/data-load-internal-tutorial)).-- Store JSON object natively in an intermediate table and then use FLATTEN function to extract JSON elements into separate columns in a table (as shown in [](/user-guide/tutorials/json-basics-tutorial))+- Store JSON objects natively in an intermediate table and then use the FLATTEN function to extract JSON elements into separate columns in a table (as shown in [](/user-guide/tutorials/json-basics-tutorial)). - Transform JSON elements directly into table columns as shown in this tutorial.  The COPY command in this tutorial uses a SELECT statement to query for individual elements in a staged JSON file. -The example commands provided in this tutorial includes a [](/sql-reference/sql/put) statement.+The example commands provided in this tutorial include a [](/sql-reference/sql/put) statement. We recommend executing these commands in SnowSQL which supports the PUT command. Clients such as [Snowsight](/user-guide/ui-snowsight-gs) do not support the PUT command.@@ -31,14 +31,14 @@ link/file to your local file system. -The tutorial assumes you unpacked the JSON data file in to the following directories:+The tutorial assumes you unpacked the JSON data file into the following directories:  <blockquote>  - Linux/macOS: `/tmp/load`-- Windows: `C:\tempload`+- Windows: `C:\temp\load`  </blockquote> -The data file include sample home sales JSON data. An example JSON object is shown:+The data file includes sample home sales JSON data. An example JSON object is shown:  ```sqljson@@ -81,6 +81,6 @@ ``` -Note these commands create temporary table. Temporary tables persist only for-the duration of the user session and is not visible to other users.+Note these commands create a temporary table. Temporary tables persist only for+the duration of the user session and are not visible to other users.  ## Create file format object@@ -146,6 +146,6 @@ The query also uses the following functions: -- The [](/sql-reference/functions/substr) function to extract city and state values from state_city JSON key.-- The [](/sql-reference/functions/to_timestamp) to cast the sale_date JSON key value to a timestamp.+- The [](/sql-reference/functions/substr) function to extract city and state values from the state_city JSON key.+- The [](/sql-reference/functions/to_timestamp) function to cast the sale_date JSON key value to a timestamp.  Execute the following query to verify data is copied.