Merge pull request #245987 from Clare-Zheng82/0724-Upgrade_MongoDB_LS

[Doc update] Upgrade MongoDB linked service

Author: v-regandowner

articles/data-factory/connector-mongodb.md

@@ -8,7 +8,7 @@ ms.service: data-factory
 ms.subservice: data-movement
 ms.topic: conceptual
 ms.custom: synapse, ignite-2022
-ms.date: 10/25/2022
+ms.date: 07/24/2023
 ---
 
 # Copy data from or to MongoDB using Azure Data Factory or Synapse Analytics
@@ -251,6 +251,20 @@ To achieve such schema-agnostic copy, skip the "structure" (also called *schema*
 
 To copy data from MongoDB to tabular sink or reversed, refer to [schema mapping](copy-activity-schema-and-type-mapping.md#schema-mapping).
 
+## Upgrade the MongoDB linked service
+
+Here are steps that help you upgrade your linked service and related queries:
+
+1. Create a new MongoDB linked service and configure it by referring to [Linked service properties](#linked-service-properties).
+1. If you use SQL queries in your pipelines that refer to the old MongoDB linked service, replace them with the equivalent MongoDB queries. See the following table for the replacement examples:
+
+    | SQL query | Equivalent MongoDB query | 
+    |:--- |:--- |
+    | `SELECT * FROM users` | `db.users.find({})` |
+    | `SELECT username, age FROM users` |`db.users.find({}, {username: 1, age: 1})` |
+    | `SELECT username AS User, age AS Age, statusNumber AS Status, CASE WHEN Status = 0 THEN "Pending" CASE WHEN Status = 1 THEN "Finished" ELSE "Unknown" END AS statusEnum LastUpdatedTime + interval '2' hour AS NewLastUpdatedTime FROM users` | `db.users.aggregate([{ $project: { _id: 0, User: "$username", Age: "$age", Status: "$statusNumber", statusEnum: { $switch: { branches: [ { case: { $eq: ["$Status", 0] }, then: "Pending" }, { case: { $eq: ["$Status", 1] }, then: "Finished" } ], default: "Unknown" } }, NewLastUpdatedTime: { $add: ["$LastUpdatedTime", 2 * 60 * 60 * 1000] } } }])`|
+    | `SELECT employees.name, departments.name AS department_name FROM employees LEFT JOIN departments ON employees.department_id = departments.id;`|`db.employees.aggregate([ { $lookup: { from: "departments", localField: "department_id", foreignField: "_id", as: "department" } }, { $unwind: "$department" }, { $project: { _id: 0, name: 1, department_name: "$department.name" } } ])` |
+
 
 ## Next steps
 For a list of data stores supported as sources and sinks by the copy activity, see [supported data stores](copy-activity-overview.md#supported-data-stores-and-formats).

articles/data-factory/connector-troubleshoot-mongodb.md

@@ -1,12 +1,12 @@
 ---
-title: Troubleshoot the mongodb connector
+title: Troubleshoot the MongoDB connector
 titleSuffix: Azure Data Factory & Azure Synapse
-description: Learn how to troubleshoot issues with the mongodb connector in Azure Data Factory and Azure Synapse Analytics. 
+description: Learn how to troubleshoot issues with the MongoDB connector in Azure Data Factory and Azure Synapse Analytics. 
 author: jianleishen
 ms.service: data-factory
 ms.subservice: data-movement
 ms.topic: troubleshooting
-ms.date: 12/02/2022
+ms.date: 07/24/2023
 ms.author: jianleishen
 ms.custom: has-adal-ref, synapse
 ---
@@ -28,6 +28,18 @@ This article provides suggestions to troubleshoot common problems with the Mongo
 
 - **Resolution**: In the MongoDB connection string, add the *uuidRepresentation=standard* option. For more information, see [MongoDB connection string](connector-mongodb.md#linked-service-properties).
 
+## Migrate to the new version of MongoDB connector
+
+- **Symptoms**: You meet the following error code and error message:
+    - **Error code**: `DeprecatedMongoDbOdbcConnector`
+    - **Error message**: `The legacy MongoDB connector has been deprecated. To ensure your pipeline works, please create a new MongoDB linked service. Detailed instructions can be found in this documentation: https://learn.microsoft.com/azure/data-factory/connector-mongodb#upgrade-the-mongodb-linked-service`
+
+- **Cause**: 
+    Your pipeline is still running on a legacy MongoDB connector that causes the error. 
+
+- **Resolution**: 
+    Upgrade your MongoDB linked service to the latest version. Refer to this [article](connector-mongodb.md#upgrade-the-mongodb-linked-service).
+
 ## Next steps
 
 For more troubleshooting help, try these resources: