Skip to content

Commit d3117e5

Browse files
Merge pull request #287807 from jonburchel/patch-1
Update connector-snowflake.md
2 parents 2779cb4 + 2f82959 commit d3117e5

File tree

1 file changed

+54
-54
lines changed

1 file changed

+54
-54
lines changed

articles/data-factory/connector-snowflake.md

Lines changed: 54 additions & 54 deletions
Original file line numberDiff line numberDiff line change
@@ -699,60 +699,60 @@ To perform a side-by-side upgrade, complete the following steps:
699699
To perform an in-place upgrade, you need to edit the existing linked service payload.
700700

701701
1. Update the type from ‘Snowflake’ to ‘SnowflakeV2’.
702-
2. 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:
703-
704-
**Legacy Snowflake connector JSON payload:**
705-
```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": "<placeholder>"
716-
        },
717-
        "connectVia": {
718-
            "referenceName": "AzureIntegrationRuntime",
719-
            "type": "IntegrationRuntimeReference"
720-
        }
721-
    }
722-
}
723-
```
724-
725-
**New Snowflake connector JSON payload:**
726-
```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-
}
753-
```
754-
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_.
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:
703+
704+
**Legacy Snowflake connector JSON payload:**
705+
```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+
}
723+
```
724+
725+
**New Snowflake connector JSON payload:**
726+
```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+
}
753+
```
754+
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)