Merge pull request #304114 from Lucky-Wang16/0812-Update_Snowflake_V11_GA

Update SnowflakeV2 1.1 preview to GA

Author: prmerger-automator[bot]

articles/data-factory/connector-release-stages-and-timelines.md

@@ -78,7 +78,7 @@ For comprehensive details on support levels and recommended usage at each stage,
 | [Salesforce Service Cloud V1](connector-salesforce-service-cloud-legacy.md) | /              | End of support         | June 30, 2025         | September 30, 2025    |
 | [ServiceNow V2](connector-servicenow.md)                   | /              | GA                                | /                   | /                   |
 | [ServiceNow V1](connector-servicenow-legacy.md)            | /              | End of support          | June 30, 2025         | September 30, 2025    |
-| [Snowflake V2](connector-snowflake.md)                     | version 1.1    | Public Preview                    | /                   | /                   |
+| [Snowflake V2](connector-snowflake.md)                     | version 1.1    | GA                                | /                   | /                   |
 |                                    | version 1.0    | GA                                | /                   | /                   |
 | [Snowflake V1](connector-snowflake-legacy.md)              | /              | End of support        | June 30, 2025         | September 30, 2025    |
 | [Spark](connector-spark.md)                               | version 2.0    | GA                 | /                   | /                   |

articles/data-factory/connector-snowflake.md

@@ -7,7 +7,7 @@ author: jianleishen
 ms.subservice: data-movement
 ms.topic: conceptual
 ms.custom: synapse
-ms.date: 05/15/2025
+ms.date: 08/12/2025
 ai-usage: ai-assisted
 ---
 
@@ -29,7 +29,7 @@ This Snowflake connector is supported for the following capabilities:
 |[Copy activity](copy-activity-overview.md) (source/sink)|① ②|
 |[Mapping data flow](concepts-data-flow-overview.md) (source/sink)|① |
 |[Lookup activity](control-flow-lookup-activity.md)|① ②|
-|[Script activity](transform-data-using-script.md) (Apply version 1.1 (Preview) when you use the script parameter)|① ②|
+|[Script activity](transform-data-using-script.md) (Apply version 1.1 when you use the script parameter)|① ②|
 
 *① Azure integration runtime ② Self-hosted integration runtime*
 
@@ -93,7 +93,7 @@ These generic properties are supported for the Snowflake linked service:
 | Property         | Description                                                  | Required |
 | :--------------- | :----------------------------------------------------------- | :------- |
 | type             | The type property must be set to **SnowflakeV2**.              | Yes      |
-| version           | The version that you specify. Recommend upgrading to the latest version to take advantage of the newest enhancements.       | Yes for version 1.1 (Preview)     |
+| version           | The version that you specify. Recommend upgrading to the latest version to take advantage of the newest enhancements.       | Yes for version 1.1     |
 | accountIdentifier | The name of the account along with its organization. For example, myorg-account123.   | Yes |
 | database | The default database used for the session after connecting. | Yes |
 | warehouse | The default virtual warehouse used for the session after connecting. |Yes|
@@ -715,7 +715,7 @@ The following table shows the release stage and change logs for different versio
 | :----------- | :------- |:------- |
 | Snowflake V1 | End of support announced | / |  
 | Snowflake V2 (version 1.0) | GA version available | • Add support for Key pair authentication. <br><br>• Add support for `storageIntegration` in Copy activity. <br><br>• The `accountIdentifier`, `warehouse`, `database`, `schema` and `role` properties are used to establish a connection instead of `connectionstring` property.<br><br>• Add support for Decimal in Lookup activity. The NUMBER type, as defined in Snowflake, will be displayed as a string in Lookup activity. If you want to covert it to numeric type in V2, you can use the pipeline parameter with [int function](control-flow-expression-language-functions.md#int) or [float function](control-flow-expression-language-functions.md#float). For example, `int(activity('lookup').output.firstRow.VALUE)`, `float(activity('lookup').output.firstRow.VALUE)`<br><br>• timestamp data type in Snowflake is read as DateTimeOffset data type in Lookup and Script activity. If you still need to use the Datetime value as a parameter in your pipeline after upgrading to V2, you can convert DateTimeOffset type to DateTime type by using [formatDateTime function](control-flow-expression-language-functions.md#formatdatetime) (recommended) or [concat function](control-flow-expression-language-functions.md#concat). For example: `formatDateTime(activity('lookup').output.firstRow.DATETIMETYPE)`, `concat(substring(activity('lookup').output.firstRow.DATETIMETYPE, 0, 19), 'Z')` <br><br>• NUMBER (p,0) is read as Decimal data type.<br><br>• TIMESTAMP_LTZ, TIMESTAMP_NTZ and TIMESTAMP_TZ is read as DateTimeOffset data type.<br><br>• Script parameters are not supported in Script activity. As an alternative, utilize dynamic expressions for script parameters. For more information, see [Expressions and functions in Azure Data Factory and Azure Synapse Analytics](control-flow-expression-language-functions.md).<br><br>• Multiple SQL statements execution in Script activity is not supported. |  
-| Snowflake V2 (version 1.1) | Preview version available | • Add support for script parameters.<br><br>• Add support for multiple statement execution in Script activity. |  
+| Snowflake V2 (version 1.1) | GA version available | • Add support for script parameters.<br><br>• Add support for multiple statement execution in Script activity. |  
 
 ### <a name="upgrade-the-snowflake-linked-service"></a> Upgrade the Snowflake connector from V1 to V2
 
@@ -792,7 +792,7 @@ To perform an in-place upgrade, you need to edit the existing linked service pay
 >[!NOTE]
 >When transitioning linked services, the override template parameter section might only display database properties. You can resolve this by manually editing the parameters. After that the **Override template parameters** section will show the connection strings.
 
-### Upgrade the Snowflake V2 connector from version 1.0 to version 1.1 (Preview)
+### Upgrade the Snowflake V2 connector from version 1.0 to version 1.1
 
 In **Edit linked service** page, select 1.1 for version. For more information, see [Linked service properties](#linked-service-properties).