Skip to content

Commit 9bdf342

Browse files
Update known-issues.md
1 parent 0bdc6ab commit 9bdf342

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

articles/synapse-analytics/known-issues.md

Lines changed: 12 additions & 12 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/8/2023
7+
ms.date: 3/9/2023
88
ms.service: synapse-analytics
99
ms.subservice: overview
1010
ms.topic: conceptual
@@ -20,14 +20,14 @@ To learn more about Azure Synapse Analytics, see the [Overview](index.yml), and
2020

2121
## Active Known issues
2222

23-
|Issue |Status |Synapse Component|
23+
|Synapse Component|Status|Issue|
2424
|---------|---------|---------|
25-
|[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|
26-
|[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-
|[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|
28-
|[Queries failing with Data Exfiltration Error](#queries-failing-with-data-exfiltration-error)|Has Workaround|Azure Synapse Dedicated SQL Pool|
29-
|[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|
30-
|[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|
25+
|Azure Synapse Serverless SQL Pool|[Queries using Azure AD authentication fails after 1 hour](#queries-using-azure-ad-authentication-fails-after-1-hour)|Has Workaround|
26+
|Azure Synapse Serverless SQL pool|[Query failures from Serverless SQL to Cosmos DB analytical store](#query-failures-from-serverless-sql-pool-to-azure-cosmos-db-analytical-store)|Has Workaround|
27+
|Azure Synapse Serverless SQL Pool|[Cosmos DB analytical store view propagates wrong attributes in the column](#cosmos-db-analytical-store-view-propagates-wrong-attributes-in-the-column)|Has Workaround|
28+
|Azure Synapse Dedicated SQL Pool|[Queries failing with Data Exfiltration Error](#queries-failing-with-data-exfiltration-error)|Has Workaround|
29+
|Azure Synapse Workspace|[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|
30+
|Azure Synapse Workspace|[Failed to delete Synapse workspace & Unable to delete virtual network](#failed-to-delete-synapse-workspace--unable-to-delete-virtual-network)|Has Workaround|
3131

3232
## Azure Synapse Analytics Serverless SQL Pool active known issues summary
3333

@@ -97,9 +97,9 @@ Deleting a Synapse workspace fails with the error message:
9797

9898
## Recently Closed Known issues
9999

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|
100+
|Synapse Component|Issue|Status|Date Resolved
101+
|---------|---------|---------|---------|
102+
|Azure Synapse Serverless SQL Pool|[Query failures while reading Cosmos Data using OPENROWSET](#query-failures-while-reading-cosmos-data-using-openrowset)|Resolved|March 2023
103103

104104
## Azure Synapse Analytics Serverless SQL Pool recently closed known issues summary
105105

@@ -109,7 +109,7 @@ Queries from serverless SQL pool to Cosmos DB Analytical Store using OPENROWSET
109109

110110
`Resolving CosmosDB path has failed with error 'bad allocation'.`
111111

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.
112+
**Status**: Resolved
113113

114114

115115
## Next steps

0 commit comments

Comments
 (0)