Skip to content

Commit 0bdc6ab

Browse files
Update known-issues.md
Update known issues page as one of the issues resolved today. Do not merge this change & I will sign off when this is 100% ready.
1 parent d593e2b commit 0bdc6ab

File tree

1 file changed

+21
-13
lines changed

1 file changed

+21
-13
lines changed

articles/synapse-analytics/known-issues.md

Lines changed: 21 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ titleSuffix: Azure Synapse Analytics
44
description: Learn about the currently known issues with Azure Synapse Analytics, and their possible workarounds or resolutions.
55
author: charithdilshan
66
ms.author: ccaldera
7-
ms.date: 3/6/2023
7+
ms.date: 3/8/2023
88
ms.service: synapse-analytics
99
ms.subservice: overview
1010
ms.topic: conceptual
@@ -24,13 +24,12 @@ To learn more about Azure Synapse Analytics, see the [Overview](index.yml), and
2424
|---------|---------|---------|
2525
|[Queries using Azure AD authentication fails after 1 hour](#queries-using-azure-ad-authentication-fails-after-1-hour)|Has Workaround|Azure Synapse Serverless SQL Pool|
2626
|[Query failures from Serverless SQL to Cosmos DB analytical store](#query-failures-from-serverless-sql-pool-to-azure-cosmos-db-analytical-store)|Has Workaround|Azure Synapse Serverless SQL pool|
27-
|[Query failures while reading Cosmos Data using OPENROWSET](#query-failures-while-reading-cosmos-data-using-openrowset)|Has Workaround|Azure Synapse Serverless SQL Pool|
2827
|[Cosmos DB analytical store view propagates wrong attributes in the column](#cosmos-db-analytical-store-view-propagates-wrong-attributes-in-the-column)|Has Workaround|Azure Synapse Serverless SQL Pool|
2928
|[Queries failing with Data Exfiltration Error](#queries-failing-with-data-exfiltration-error)|Has Workaround|Azure Synapse Dedicated SQL Pool|
3029
|[Blob storage linked service with User Assigned Managed Identity (UAMI) is not getting listed](#blob-storage-linked-service-with-user-assigned-managed-identity-uami-is-not-getting-listed)|Has Workaround|Azure Synapse Workspace|
3130
|[Failed to delete Synapse workspace & Unable to delete virtual network](#failed-to-delete-synapse-workspace--unable-to-delete-virtual-network)|Has Workaround|Azure Synapse Workspace|
3231

33-
## Azure Synapse Analytics Serverless SQL Pool known issues summary
32+
## Azure Synapse Analytics Serverless SQL Pool active known issues summary
3433

3534
### Queries using Azure AD authentication fails after 1 hour
3635

@@ -59,14 +58,6 @@ The following conditions must be true to confirm this issue:
5958
1) Retry the failed query. It will automatically refresh the expired token.
6059
2) Disable the private endpoint. Before applying this change, confirm with your security team that it meets your company security policies.
6160

62-
### Query failures while reading Cosmos Data using OPENROWSET
63-
64-
Queries from serverless SQL pool to Cosmos DB Analytical Store using OPENROWSET fails with the following error message:
65-
66-
`Resolving CosmosDB path has failed with error 'bad allocation'.`
67-
68-
**Workaround**: The engineering team is aware of this behavior and working on a fix. If you encounter this error engage Microsoft Support Team for assistance.
69-
7061
### Cosmos DB analytical store view propagates wrong attributes in the column
7162

7263
While using views in Synapse serverless pool over CosmosDB analytical store, If there is a change on files in the CosmosDB analytical store, the change does not get propagated correctly to the SELECT statements, the customer is using on the view. As a result of that, the attributes get incorrectly mapped to a different column in the results.
@@ -76,7 +67,7 @@ While using views in Synapse serverless pool over CosmosDB analytical store, If
7667
1) Recreate the view by renaming the columns.
7768
2) Avoid using views if possible.
7869

79-
## Azure Synapse Analytics Dedicated SQL pool known issues summary
70+
## Azure Synapse Analytics Dedicated SQL pool active known issues summary
8071

8172
### Queries failing with Data Exfiltration Error
8273

@@ -86,7 +77,7 @@ Synapse workspaces created from an existing dedicated SQL Pool report query fail
8677

8778
**Workaround**: If you encountered a similar error, engage Microsoft Support Team for assistance.
8879

89-
## Azure Synapse workspace known issues summary
80+
## Azure Synapse workspace active known issues summary
9081

9182
The following are known issues with the Synapse workspace.
9283

@@ -104,6 +95,23 @@ Deleting a Synapse workspace fails with the error message:
10495

10596
**Workaround**: The problem can be mitigated by retrying the delete operation. The engineering team is aware of this behavior and working on a fix.
10697

98+
## Recently Closed Known issues
99+
100+
|Issue |Status |Synapse Component|
101+
|---------|---------|---------|
102+
|[Query failures while reading Cosmos Data using OPENROWSET](#query-failures-while-reading-cosmos-data-using-openrowset)|Resolved|Azure Synapse Serverless SQL Pool|
103+
104+
## Azure Synapse Analytics Serverless SQL Pool recently closed known issues summary
105+
106+
### Query failures while reading Cosmos Data using OPENROWSET
107+
108+
Queries from serverless SQL pool to Cosmos DB Analytical Store using OPENROWSET fails with the following error message:
109+
110+
`Resolving CosmosDB path has failed with error 'bad allocation'.`
111+
112+
**Workaround**: The engineering team is aware of this behavior and working on a fix. If you encounter this error engage Microsoft Support Team for assistance.
113+
114+
107115
## Next steps
108116

109117
- [Synapse Studio troubleshooting](troubleshoot/troubleshoot-synapse-studio.md)

0 commit comments

Comments
 (0)