You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/data-factory/connector-troubleshoot-azure-cosmos-db.md
+31-4Lines changed: 31 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: jianleishen
6
6
ms.service: data-factory
7
7
ms.subservice: data-movement
8
8
ms.topic: troubleshooting
9
-
ms.date: 07/29/2022
9
+
ms.date: 04/20/2023
10
10
ms.author: jianleishen
11
11
ms.custom: has-adal-ref, synapse, ignite-2022
12
12
---
@@ -21,9 +21,36 @@ This article provides suggestions to troubleshoot common problems with the Azure
21
21
22
22
-**Symptoms**: When you copy data into Azure Cosmos DB with a default write batch size, you receive the following error: `Request size is too large.`
23
23
24
-
-**Cause**: Azure Cosmos DB limits the size of a single request to 2 MB. The formula is *request size = single document size \* write batch size*. If your document size is large, the default behavior will result in a request size that's too large. You can tune the write batch size.
25
-
26
-
-**Resolution**: In the copy activity sink, reduce the *write batch size* value (the default value is 10000).
24
+
-**Cause**: Azure Cosmos DB limits the size of a single request to 2 MB. The formula is *request size = single document size \* write batch size*. If your document size is large, the default behavior will result in a request size that's too large.
25
+
26
+
-**Resolution**: <br>
27
+
You can tune the write batch size. In the copy activity sink, reduce the *write batch size* value (the default value is 10000). <br>
28
+
If reducing the *write batch size* value to 1 still doesn't work, change your Azure Cosmos DB SQL API from V2 to V3. To complete this configuration, you have two options:
29
+
30
+
- **Option 1**: Change your authentication type to service principal or system-assigned managed identity or user-assigned managed identity.
31
+
- **Option 2**: If you still want to use account key authentication, follow these steps:
32
+
1. Create an Azure Cosmos DB for NoSQL linked service.
33
+
2. Update the linked service with the following template.
0 commit comments