Skip to content

Commit d54a38b

Browse files
Update known-issues.md
1 parent e41ee70 commit d54a38b

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/synapse-analytics/known-issues.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Learn about the currently known issues with Azure Synapse Analytics
55
author: charithcaldera
66
ms.author: ccaldera
77
ms.reviewer: wiassaf, joanpo
8-
ms.date: 04/08/2024
8+
ms.date: 01/30/2025
99
ms.service: azure-synapse-analytics
1010
ms.subservice: overview
1111
ms.topic: troubleshooting-known-issue
@@ -44,13 +44,13 @@ To learn more about Azure Synapse Analytics, see the [Azure Synapse Analytics Ov
4444

4545
### Data Factory copy command fails with error "The request could not be performed because of an I/O device error"
4646

47-
Azure Data Factory pipelines use the COPY INTO statement to ingest data at scale into dedicated SQL Pool tables. In some rare cases, the COPY INTO statement can fail when loading CSV files into dedicated SQL Pool table when file split is used in an Azure Data Factory pipeline. File splitting is a mechanism that improves load performance when a small number of larger (1GB+) files are loaded in a single copy task. When file splitting is enabled, a single file can be loaded by multiple parallel threads, where every thread is assigned a part of the file.
47+
Azure Data Factory pipelines use the `COPY INTO` Transact-SQL statement to ingest data at scale into dedicated SQL pool tables. In some rare cases, the `COPY INTO` statement can fail when loading CSV files into dedicated SQL pool table when file split is used in an Azure Data Factory pipeline. File splitting is a mechanism that improves load performance when a small number of larger (1 GB+) files are loaded in a single copy task. When file splitting is enabled, a single file can be loaded by multiple parallel threads, where every thread is assigned a part of the file.
4848

49-
**Workaround**: Impacted customers may need to disable file split in Azure Data Factory.
49+
**Workaround**: Impacted customers should disable file split in Azure Data Factory.
5050

5151
### COPY INTO statement fails with error “An internal DMS error occurred that caused this operation to fail.” when managed identity is used
5252

53-
when using COPY INTO command with managed identity, the statement can fail after a long-running query with error message “An internal DMS error occurred that caused this operation to fail”.
53+
When using `COPY INTO` command with a managed identity, the statement can fail after a long-running query with error message “An internal DMS error occurred that caused this operation to fail”.
5454

5555
**Workaround**: Impacted customers may use an alternative authentication method for the storage account, such as a Shared Access Key.
5656

0 commit comments

Comments
 (0)