Skip to content

Commit 171ddb0

Browse files
prmerger-automator[bot]prmerger-automator[bot]
authored
Merge pull request #288106 from Clare-Zheng82/1009-Update_upgrade_section_title
[Doc update] Update upgrade section title
2 parents f9a7517 + 092e868 commit 171ddb0

7 files changed

+73
-72
lines changed

‎articles/data-factory/connector-google-bigquery.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: jianleishen
77
ms.subservice: data-movement
88
ms.topic: conceptual
99
ms.custom: synapse
10-
ms.date: 05/22/2024
10+
ms.date: 10/09/2024
1111
---
1212

1313
# Copy data from Google BigQuery using Azure Data Factory or Synapse Analytics
@@ -220,9 +220,10 @@ To copy data from Google BigQuery, set the source type in the copy activity to *
220220

221221
To learn details about the properties, check [Lookup activity](control-flow-lookup-activity.md).
222222

223-
## Upgrade the Google BigQuery linked service
224223

225-
To upgrade the Google BigQuery linked service, create a new Google BigQuery linked service and configure it by referring to [Linked service properties](#linked-service-properties).
224+
## <a name="upgrade-the-google-bigquery-linked-service"></a> Upgrade the Google BigQuery connector
225+
226+
To upgrade the Google BigQuery connector, create a new Google BigQuery linked service and configure it by referring to [Linked service properties](#linked-service-properties).
226227

227228
## Differences between Google BigQuery and Google BigQuery (legacy)
228229

‎articles/data-factory/connector-mariadb.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: jianleishen
66
ms.subservice: data-movement
77
ms.custom: synapse
88
ms.topic: conceptual
9-
ms.date: 05/22/2024
9+
ms.date: 10/09/2024
1010
ms.author: jianleishen
1111
---
1212

@@ -16,7 +16,7 @@ ms.author: jianleishen
1616
This article outlines how to use the Copy Activity in an Azure Data Factory or Synapse Analytics pipeline to copy data from MariaDB. It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.
1717

1818
>[!IMPORTANT]
19-
>MariaDB connector using the recommended driver version provides improved native MariaDB support. If you are using it with the legacy driver version, please [upgrade your driver version](#upgrade-the-mariadb-driver-version) before **October 31, 2024**. Refer to this [section](#differences-between-the-recommended-and-the-legacy-driver-version) for details on the difference between the legacy and recommended version.
19+
>MariaDB connector using the recommended driver version provides improved native MariaDB support. If you are using the connector with the legacy driver version, please [upgrade it](#upgrade-the-mariadb-driver-version) before **October 31, 2024**. Refer to this [section](#differences-between-the-recommended-and-the-legacy-driver-version) for details on the difference between the legacy and recommended version.
2020
2121
## Supported capabilities
2222

@@ -286,9 +286,9 @@ When copying data from MariaDB, the following mappings are used from MariaDB dat
286286

287287
To learn details about the properties, check [Lookup activity](control-flow-lookup-activity.md).
288288

289-
## Upgrade the MariaDB driver version
289+
## <a name="upgrade-the-mariadb-driver-version"></a> Upgrade the MariaDB connector
290290

291-
Here are steps that help you upgrade your MariaDB driver version:
291+
Here are steps that help you upgrade your MariaDB connector:
292292

293293
1. In **Edit linked service** page, select **Recommended** under **Driver version** and configure the linked service by referring to [Linked service properties](connector-mariadb.md#linked-service-properties).
294294

‎articles/data-factory/connector-mysql.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: jianleishen
66
ms.subservice: data-movement
77
ms.custom: synapse
88
ms.topic: conceptual
9-
ms.date: 05/22/2024
9+
ms.date: 10/09/2024
1010
ms.author: jianleishen
1111
---
1212

@@ -20,7 +20,7 @@ This article outlines how to use the Copy Activity in Azure Data Factory and Syn
2020
>To copy data from or to [Azure Database for MySQL](/azure/mysql/overview) service, use the specialized [Azure Database for MySQL connector](connector-azure-database-for-mysql.md).
2121
2222
>[!IMPORTANT]
23-
>MySQL connector using the recommended driver version provides improved native MySQL support. If you are using it with the legacy driver version, please [upgrade your driver version](#upgrade-the-mysql-driver-version) before **October 31, 2024**. Refer to this [section](#differences-between-the-recommended-and-the-legacy-driver-version) for details on the difference between the legacy and recommended version.
23+
>MySQL connector using the recommended driver version provides improved native MySQL support. If you are using the connector with the legacy driver version, please [upgrade it](#upgrade-the-mysql-driver-version) before **October 31, 2024**. Refer to this [section](#differences-between-the-recommended-and-the-legacy-driver-version) for details on the difference between the legacy and recommended version.
2424
2525
## Supported capabilities
2626

@@ -315,9 +315,9 @@ When copying data from MySQL, the following mappings are used from MySQL data ty
315315

316316
To learn details about the properties, check [Lookup activity](control-flow-lookup-activity.md).
317317

318-
## Upgrade the MySQL driver version
318+
## <a name="upgrade-the-mysql-driver-version"></a> Upgrade the MySQL connector
319319

320-
Here are steps that help you upgrade your MySQL driver version:
320+
Here are steps that help you upgrade your MySQL connector:
321321

322322
1. In **Edit linked service** page, select **Recommended** under **Driver version** and configure the linked service by referring to [Linked service properties](connector-mysql.md#linked-service-properties).
323323

‎articles/data-factory/connector-postgresql.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: jianleishen
66
ms.subservice: data-movement
77
ms.custom: synapse
88
ms.topic: conceptual
9-
ms.date: 05/22/2024
9+
ms.date: 10/09/2024
1010
ms.author: jianleishen
1111
---
1212
# Copy data from PostgreSQL using Azure Data Factory or Synapse Analytics
@@ -308,9 +308,9 @@ When copying data from PostgreSQL, the following mappings are used from PostgreS
308308

309309
To learn details about the properties, check [Lookup activity](control-flow-lookup-activity.md).
310310

311-
## Upgrade the PostgreSQL linked service
311+
## <a name="upgrade-the-postgresql-linked-service"></a> Upgrade the PostgreSQL connector
312312

313-
Here are steps that help you upgrade your PostgreSQL linked service:
313+
Here are steps that help you upgrade your PostgreSQL connector:
314314

315315
1. Create a new PostgreSQL linked service and configure it by referring to [Linked service properties](#linked-service-properties).
316316

‎articles/data-factory/connector-salesforce-service-cloud.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: jianleishen
77
ms.subservice: data-movement
88
ms.topic: conceptual
99
ms.custom: synapse
10-
ms.date: 08/21/2024
10+
ms.date: 10/09/2024
1111
---
1212

1313
# Copy data from and to Salesforce Service Cloud using Azure Data Factory or Azure Synapse Analytics
@@ -325,9 +325,9 @@ When you copy data from Salesforce Service Cloud, the following mappings are use
325325

326326
To learn details about the properties, check [Lookup activity](control-flow-lookup-activity.md).
327327

328-
## Upgrade the Salesforce Service Cloud linked service
328+
## <a name="upgrade-the-salesforce-service-cloud-linked-service"></a> Upgrade the Salesforce Service Cloud connector
329329

330-
Here are steps that help you upgrade your linked service and related queries:
330+
Here are steps that help you upgrade your Salesforce Service Cloud connector:
331331

332332
1. Configure the connected apps in Salesforce portal by referring to [Prerequisites](connector-salesforce-service-cloud.md#prerequisites).
333333

‎articles/data-factory/connector-salesforce.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: jianleishen
77
ms.subservice: data-movement
88
ms.topic: conceptual
99
ms.custom: synapse
10-
ms.date: 09/30/2024
10+
ms.date: 10/09/2024
1111
---
1212

1313
# Copy data from and to Salesforce using Azure Data Factory or Azure Synapse Analytics
@@ -369,9 +369,9 @@ When you copy data from Salesforce, the following mappings are used from Salesfo
369369

370370
To learn details about the properties, check [Lookup activity](control-flow-lookup-activity.md).
371371

372-
## Upgrade the Salesforce linked service
372+
## <a name="upgrade-the-salesforce-linked-service"></a> Upgrade the Salesforce connector
373373

374-
Here are steps that help you upgrade your linked service and related queries:
374+
Here are steps that help you upgrade your Salesforce connector:
375375

376376
1. Configure the connected apps in Salesforce portal by referring to [Prerequisites](connector-salesforce.md#prerequisites).
377377

‎articles/data-factory/connector-snowflake.md

Lines changed: 52 additions & 52 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: jianleishen
77
ms.subservice: data-movement
88
ms.topic: conceptual
99
ms.custom: synapse
10-
ms.date: 09/23/2024
10+
ms.date: 10/09/2024
1111
ai-usage: ai-assisted
1212
---
1313

@@ -682,9 +682,9 @@ By setting the pipeline Logging Level to None, we exclude the transmission of in
682682

683683
For more information about the properties, see [Lookup activity](control-flow-lookup-activity.md).
684684

685-
## Upgrade the Snowflake linked service
685+
## <a name="upgrade-the-snowflake-linked-service"></a> Upgrade the Snowflake connector
686686

687-
To upgrade the Snowflake linked service, you can do a side-by-side upgrade, or an in-place upgrade.
687+
To upgrade the Snowflake connector, you can do a side-by-side upgrade, or an in-place upgrade.
688688

689689
### Side-by-side upgrade
690690

@@ -696,63 +696,63 @@ To perform a side-by-side upgrade, complete the following steps:
696696

697697
### In-place upgrade
698698

699-
To perform an in-place upgrade, you need to edit the existing linked service payload.
699+
To perform an in-place upgrade, you need to edit the existing linked service payload and update dataset to use the new linked service.
700700

701-
1. Update the type from ‘Snowflake’ to ‘SnowflakeV2’.
702-
1. Modify the linked service payload from its legacy format to the new pattern. You can either fill in each field from the user interface after changing the type mentioned above, or update the payload directly through the JSON Editor. Refer to the [Linked service properties](#linked-service-properties) section in this article for the supported connection properties. The following examples show the differences in payload for the legacy and new Snowflake connectors:
701+
1. Update the type from **Snowflake** to **SnowflakeV2**.
702+
1. Modify the linked service payload from its legacy format to the new pattern. You can either fill in each field from the user interface after changing the type mentioned above, or update the payload directly through the JSON Editor. Refer to the [Linked service properties](#linked-service-properties) section in this article for the supported connection properties. The following examples show the differences in payload for the legacy and new Snowflake linked services:
703703

704-
**Legacy Snowflake connector JSON payload:**
704+
**Legacy Snowflake linked service JSON payload:**
705705
```json
706-
{
707-
    "name": "Snowflake1",
708-
    "type": "Microsoft.DataFactory/factories/linkedservices",
709-
    "properties": {
710-
        "annotations": [],
711-
        "type": "Snowflake",
712-
        "typeProperties": {
713-
            "authenticationType": "Basic",
714-
            "connectionString": "jdbc:snowflake://<fake_account>.snowflakecomputing.com/?user=FAKE_USER&db=FAKE_DB&warehouse=FAKE_DW&schema=PUBLIC",
715-
            "encryptedCredential": "<your_encrypted_credential_value>"
716-
        },
717-
        "connectVia": {
718-
            "referenceName": "AzureIntegrationRuntime",
719-
            "type": "IntegrationRuntimeReference"
720-
        }
721-
    }
722-
}
706+
{
707+
"name": "Snowflake1",
708+
"type": "Microsoft.DataFactory/factories/linkedservices",
709+
"properties": {
710+
"annotations": [],
711+
"type": "Snowflake",
712+
"typeProperties": {
713+
"authenticationType": "Basic",
714+
"connectionString": "jdbc:snowflake://<fake_account>.snowflakecomputing.com/?user=FAKE_USER&db=FAKE_DB&warehouse=FAKE_DW&schema=PUBLIC",
715+
"encryptedCredential": "<your_encrypted_credential_value>"
716+
},
717+
"connectVia": {
718+
"referenceName": "AzureIntegrationRuntime",
719+
"type": "IntegrationRuntimeReference"
720+
}
721+
}
722+
}
723723
```
724724

725-
**New Snowflake connector JSON payload:**
725+
**New Snowflake linked service JSON payload:**
726726
```json
727-
{
728-
    "name": "Snowflake2",
729-
    "type": "Microsoft.DataFactory/factories/linkedservices",
730-
    "properties": {
731-
        "parameters": {
732-
          "schema": {
733-
                "type": "string",
734-
                "defaultValue": "PUBLIC"
735-
            }
736-
        },
737-
        "annotations": [],
738-
        "type": "SnowflakeV2",
739-
        "typeProperties": {
740-
            "authenticationType": "Basic",
741-
            "accountIdentifier": "<FAKE_Account",
742-
            "user": "FAKE_USER",
743-
            "database": "FAKE_DB",
744-
            "warehouse": "FAKE_DW",
745-
            "encryptedCredential": "<placeholder>"
746-
        },
747-
        "connectVia": {
748-
            "referenceName": "AutoResolveIntegrationRuntime",
749-
            "type": "IntegrationRuntimeReference"
750-
        }
751-
    }
752-
}
727+
{
728+
"name": "Snowflake2",
729+
"type": "Microsoft.DataFactory/factories/linkedservices",
730+
"properties": {
731+
"parameters": {
732+
"schema": {
733+
"type": "string",
734+
"defaultValue": "PUBLIC"
735+
}
736+
},
737+
"annotations": [],
738+
"type": "SnowflakeV2",
739+
"typeProperties": {
740+
"authenticationType": "Basic",
741+
"accountIdentifier": "<FAKE_Account>",
742+
"user": "FAKE_USER",
743+
"database": "FAKE_DB",
744+
"warehouse": "FAKE_DW",
745+
"encryptedCredential": "<placeholder>"
746+
},
747+
"connectVia": {
748+
"referenceName": "AutoResolveIntegrationRuntime",
749+
"type": "IntegrationRuntimeReference"
750+
}
751+
}
752+
}
753753
```
754754

755-
1. Update dataset to use the new linked service. You can either create a new dataset based on the newly created linked service, or update an existing dataset's type property from _SnowflakeTable_ to _SnowflakeV2Table_.
755+
1. Update dataset to use the new linked service. You can either create a new dataset based on the newly created linked service, or update an existing dataset's type property from **SnowflakeTable** to **SnowflakeV2Table**.
756756

757757
## Differences between Snowflake and Snowflake (legacy)
758758

0 commit comments

Comments
 (0)