Merge pull request #302069 from Lucky-Wang16/0701-Update_Netezza_v2

Update Netezza v2 doc

Author: v-ccolin

articles/data-factory/connector-netezza.md

@@ -6,7 +6,7 @@ author: jianleishen
 ms.subservice: data-movement
 ms.custom: synapse
 ms.topic: conceptual
-ms.date: 01/02/2025
+ms.date: 07/01/2025
 ms.author: jianleishen
 ---
 # Copy data from Netezza by using Azure Data Factory or Synapse Analytics
@@ -17,14 +17,17 @@ This article outlines how to use Copy Activity in Azure Data Factory or Synapse
 >[!TIP]
 >For data migration scenario from Netezza to Azure, learn more from [Migrate data from on-premises Netezza server to Azure](data-migration-guidance-netezza-azure-sqldw.md).
 
+> [!IMPORTANT]
+> The Netezza connector version 2.0 provides improved native Netezza support. If you are using the Netezza connector version 1.0 in your solution, please [upgrade your Netezza connector](#upgrade-the-netezza-connector) before **September 30, 2025**. Refer to this [section](#differences-between-netezza-version-20-and-version-10) for details on the difference between version 2.0 and version 1.0.
+
 ## Supported capabilities
 
 This Netezza connector is supported for the following capabilities:
 
 | Supported capabilities|IR |
 |---------| --------|
-|[Copy activity](copy-activity-overview.md) (source/-)|① ②|
-|[Lookup activity](control-flow-lookup-activity.md)|① ②|
+|[Copy activity](copy-activity-overview.md) (source/-)|① (only for version 1.0) ②|
+|[Lookup activity](control-flow-lookup-activity.md)|① (only for version 1.0) ②|
 
 *① Azure integration runtime ② Self-hosted integration runtime*
 
@@ -38,9 +41,23 @@ This Netezza connector supports:
 
 The service provides a built-in driver to enable connectivity. You don't need to manually install any driver to use this connector.
 
+For version 2.0, you need to [install a IBM Netezza ODBC driver](#install-netezza-odbc-driver-for-the-version-20) manually. For version 1.0, the service provides a built-in driver to enable connectivity. You don't need to manually install any driver to use this connector.
+
 ## Prerequisites
 
-[!INCLUDE [data-factory-v2-integration-runtime-requirements](includes/data-factory-v2-integration-runtime-requirements.md)]
+If your data store is located inside an on-premises network, an Azure virtual network, or Amazon Virtual Private Cloud, you need to configure a [self-hosted integration runtime](create-self-hosted-integration-runtime.md) to connect to it.
+
+For more information about the network security mechanisms and options supported by Data Factory, see [Data access strategies](data-access-strategies.md).
+
+### For version 1.0
+
+If your data store is a managed cloud data service, you can use the Azure Integration Runtime. If the access is restricted to IPs that are approved in the firewall rules, you can add [Azure Integration Runtime IPs](azure-integration-runtime-ip-addresses.md) to the allow list. 
+
+You can also use the [managed virtual network integration runtime](tutorial-managed-virtual-network-on-premise-sql-server.md) feature in Azure Data Factory to access the on-premises network without installing and configuring a self-hosted integration runtime.
+
+### <a name="install-netezza-odbc-driver-for-the-version-20"></a> Install Netezza ODBC driver for the version 2.0
+
+To use Netezza connector with version 2.0, [install the IBM Netezza ODBC driver](https://knowledge.informatica.com/s/article/HOW-TO-Download-the-Netezza-ODBC-driver?language=en_US) version 11.02.02 or higher on the machine running the self-hosted Integration runtime.
 
 ## Get started
 
@@ -75,7 +92,57 @@ The following sections provide details about properties you can use to define en
 
 ## Linked service properties
 
-The following properties are supported for the Netezza linked service:
+The Netezza connector now supports version 2.0. Refer to this [section](#upgrade-the-netezza-connector) to upgrade your Netezza connector version from version 1.0. For the property details, see the corresponding sections.
+
+- [Version 2.0](#version-20)
+- [Version 1.0](#version-10)
+
+### <a name="version-20"></a> Version 2.0
+
+The Netezza linked service supports the following properties when apply version 2.0:
+
+| Property | Description | Required |
+|:--- |:--- |:--- |
+| type | The **type** property must be set to **Netezza**. | Yes |
+| version | The version that you specify. The value is `2.0`. | Yes |
+| server | The hostname or the IP address of the Netezza server. | Yes |
+| port | The port number of the server listener. | Yes |
+| database | Name of the Netezza database. | Yes |
+| uid | The user id used to connect to the database. | Yes |
+| pwd | The password used to connect to the database. | Yes |
+| SecurityLevel | The level of security that the driver uses for the connection to the data store. <br>Example: `SecurityLevel=preferredUnSecured`. Supported values are:<br/>- **Only unsecured** (**onlyUnSecured**): The driver doesn't use SSL.<br/>- **Preferred unsecured (preferredUnSecured) (default)**: If the server provides a choice, the driver doesn't use SSL.  | No |
+| connectVia | The [Integration Runtime](concepts-integration-runtime.md) to use to connect to the data store. Learn more from [Prerequisites](#prerequisites) section. You can only use the self-hosted integration runtime. |No |
+
+**Example**
+
+```json
+{
+    "name": "NetezzaLinkedService",
+    "properties": {
+        "type": "Netezza",
+        "version": "2.0",
+        "typeProperties": {
+            "server": "<server>",
+	        "port": "<port>",
+            "database": "<database>",
+ 		    "uid": "<username>",
+		    "pwd": {
+                "type": "SecureString",
+                "value": "<password>"
+             },
+		    "securityLevel": "preferredUnSecured"
+        },
+        "connectVia": {
+            "referenceName": "<name of Integration Runtime>",
+            "type": "IntegrationRuntimeReference"
+        }
+    }
+}
+```
+
+### Version 1.0
+
+The following properties are supported for the Netezza linked service when apply version 1.0:
 
 | Property | Description | Required |
 |:--- |:--- |:--- |
@@ -263,10 +330,48 @@ You are suggested to enable parallel copy with data partitioning especially when
 }
 ```
 
+## Data type mapping for Netezza
+
+When you copy data from Netezza, the following mappings apply from Netezza's data types to the internal data types used by the service. To learn about how the copy activity maps the source schema and data type to the sink, see [Schema and data type mappings](copy-activity-schema-and-type-mapping.md).
+
+| Netezza data type | Interim service data type (for version 2.0) | Interim service data type (for version 1.0) |
+|:--- |:--- |:--- |
+| BOOLEAN | Boolean | Boolean |
+| CHAR | String | String |
+| VARCHAR | String | String |
+| NCHAR | String | String |
+| NVARCHAR | String | String |
+| DATE | Date | DateTime |
+| TIMESTAMP | DateTime | DateTime |
+| TIME | Time | TimeSpan |
+| INTERVAL | Not Supported | TimeSpan |
+| TIME WITH TIME ZONE | String | String |
+| NUMERIC(p,s) | Decimal | Decimal |
+| REAL | Single | Single |
+| DOUBLE PRECISION | Double | Double |
+| INTEGER | Int32 | Int32 |
+| BYTEINT | Int16 | SByte |
+| SMALLINT | Int16 | Int16 |
+| BIGINT | Int64 | Int64 |
+
 ## Lookup activity properties
 
 To learn details about the properties, check [Lookup activity](control-flow-lookup-activity.md).
 
+## <a name="differences-between-netezza-version-20-and-version-10"></a> Netezza connector lifecycle and upgrade
+
+The following table shows the release stage and change logs for different versions of the Netezza connector:
+
+| Version  | Release stage | Change log |  
+| :----------- | :------- |:------- |
+| Version 1.0 | End of support announced | / |  
+| Version 2.0 | GA version available | • Only support the self-hosted integration runtime. <br><br>• BYTEINT is read as Int16 data type. <br><br> • DATE is read as Date data type. <br><br>• TIME is read as Time data type. <br><br>• INTERVAL is not supported.|
+
+### <a name="upgrade-the-netezza-connector"></a> Upgrade the Netezza connector from version 1.0 to version 2.0
+
+1. In **Edit linked service** page, select 2.0 for version. For more information, see [linked service version 2.0 properties](#version-20).
+1. The data type mapping for the Netezza linked service version 2.0 is different from that for the version 1.0. To learn the latest data type mapping, see [Data type mapping for Netezza](#data-type-mapping-for-netezza).
+1. Only support the self-hosted integration runtime. Azure integration runtime is not supported by version 2.0.
 
 ## Related content
 

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

@@ -56,6 +56,8 @@ For comprehensive details on support levels and recommended usage at each stage,
 | [Marketo (Preview)](connector-marketo.md)                  | /              | End of support                    | December 31, 2024     | December 31, 2024     |
 | [MySQL](connector-mysql.md)                              | version 2.0    | GA                                | /                   | /                   |
 |                                    | version 1.0    | End of support                | October 31, 2024      | September 30, 2025    |
+| [Netezza](connector-netezza.md)                          | version 2.0    | GA                                | /                   | /                   |
+|                                    | version 1.0    | End of support announced          | September 30, 2025         | October 31, 2025    |
 | [Oracle](connector-oracle.md)                             | version 2.0    | GA                                | /                   | /                   |
 |                                    | version 1.0    | End of support announced          | October 31, 2025         | March 31, 2026      |
 | [Oracle Eloqua (Preview)](connector-oracle-eloqua.md)      | /              | End of support                    | December 31, 2024     | December 31, 2024     |

articles/data-factory/guidance-for-byod-approach.md

@@ -7,7 +7,7 @@ ms.service: azure-data-factory
 ms.subservice: data-movement
 ms.topic: concept-article
 ms.custom: references_regions
-ms.date: 07/11/2025
+ms.date: 07/14/2025
 ---
 
 # Guidance on using the Bring Your Own Driver (BYOD) approach
@@ -90,6 +90,7 @@ This article provides step-by-step guidance for using connectors with Bring Your
 ### Related connectors
 
 - [Amazon Redshift (version 2.0 (Preview))](connector-amazon-redshift.md)
+- [Netezza (version 2.0)](connector-netezza.md)
 - [Vertica (version 2.0)](connector-vertica.md)
 
 ## Related content