Skip to content

Commit 6123076

Browse files
Merge pull request #310874 from MicrosoftDocs/main
Auto Publish – main to live - 2026-01-26 12:00 UTC
2 parents 394c578 + e19c1c2 commit 6123076

2 files changed

Lines changed: 6 additions & 17 deletions

File tree

articles/data-factory/connector-mongodb.md

Lines changed: 3 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: jianleishen
66
ms.author: jianleishen
77
ms.subservice: data-movement
88
ms.topic: conceptual
9-
ms.date: 06/30/2025
9+
ms.date: 01/26/2026
1010
ms.custom:
1111
- synapse
1212
- sfi-image-nochange
@@ -275,23 +275,12 @@ The following table shows the release stage and change logs for different versio
275275

276276
| Version | Release stage | Change log |
277277
| :------- | :---------------------- |:---------- |
278-
| MongoDB (legacy) | End of support | / |
278+
| MongoDB (legacy) | Removed | Not applicable. |
279279
| MongoDB | GA version available | • Support the equivalent MongoDB queries only. <br><br>• Double is read as String data type. |
280280

281281
### Upgrade the MongoDB linked service
282282

283-
Here are steps that help you upgrade your linked service and related queries:
284-
285-
1. Create a new MongoDB linked service and configure it by referring to [Linked service properties](#linked-service-properties).
286-
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:
287-
288-
| SQL query | Equivalent MongoDB query |
289-
|:--- |:--- |
290-
| `SELECT * FROM users` | `db.users.find({})` |
291-
| `SELECT username, age FROM users` |`db.users.find({}, {username: 1, age: 1})` |
292-
| `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] } } }])`|
293-
| `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" } } ])` |
294-
283+
Create a new MongoDB linked service and configure it by referring to [Linked service properties](#linked-service-properties).
295284

296285
## Related content
297286
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-postgresql.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Learn how to copy data from PostgreSQL V2 to supported sink data st
55
author: jianleishen
66
ms.subservice: data-movement
77
ms.topic: conceptual
8-
ms.date: 04/14/2025
8+
ms.date: 01/26/2026
99
ms.author: jianleishen
1010
ms.custom:
1111
- synapse
@@ -80,8 +80,8 @@ The following properties are supported for PostgreSQL linked service:
8080
| server | Specifies the host name - and optionally port - on which PostgreSQL is running. | Yes |
8181
| port | The TCP port of the PostgreSQL server.| No |
8282
| database | The PostgreSQL database to connect to. | Yes |
83-
| username | The username to connect with. Not required if using IntegratedSecurity. | Yes |
84-
| password | The password to connect with. Not required if using IntegratedSecurity. | Yes |
83+
| username | The username to connect with. | Yes |
84+
| password | The password to connect with. | Yes |
8585
| sslMode | Controls whether SSL is used, depending on server support. <br/>- **Disable**: SSL is disabled. If the server requires SSL, the connection will fail.<br/>- **Allow**: Prefer non-SSL connections if the server allows them, but allow SSL connections.<br/>- **Prefer**: Prefer SSL connections if the server allows them, but allow connections without SSL.<br/>- **Require**: Fail the connection if the server doesn't support SSL.<br/>- **Verify-ca**: Fail the connection if the server doesn't support SSL. Also verifies server certificate.<br/>- **Verify-full**: Fail the connection if the server doesn't support SSL. Also verifies server certificate with host's name. <br/>Options: Disable (0) / Allow (1) / Prefer (2) **(Default)** / Require (3) / Verify-ca (4) / Verify-full (5) | No |
8686
| authenticationType | Authentication type for connecting to the database. Only supports **Basic**. | Yes |
8787
| connectVia | The [Integration Runtime](concepts-integration-runtime.md) to be used to connect to the data store. Learn more from [Prerequisites](#prerequisites) section. If not specified, it uses the default Azure Integration Runtime. |No |

0 commit comments

Comments
 (0)