Skip to content

Commit 68a9524

Browse files
20251016 COPY INTO remarks
Co-authored-by: "Pericles (Peri) Rocha" <12371744+periclesrocha@users.noreply.github.com>
1 parent 5cd86ef commit 68a9524

1 file changed

Lines changed: 9 additions & 1 deletion

File tree

docs/t-sql/statements/copy-into-transact-sql.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Use the COPY statement in Azure Synapse Analytics and Warehouse in
55
author: WilliamDAssafMSFT
66
ms.author: wiassaf
77
ms.reviewer: procha, mikeray, fresantos
8-
ms.date: 07/29/2025
8+
ms.date: 10/15/2025
99
ms.service: sql
1010
ms.subservice: t-sql
1111
ms.topic: reference
@@ -347,6 +347,10 @@ The COPY statement accepts only UTF-8 and UTF-16 valid characters for row data a
347347

348348
The MAXDOP query hint is not supported with COPY INTO.
349349

350+
To ensure reliable execution, the source files and folders must remain unchanged throughout the duration of the `COPY INTO` operation.
351+
- Modifying, deleting, or replacing any referenced files or folders while the command is running can cause the operation to fail or result in inconsistent data ingestion.
352+
- Before executing `COPY INTO`, verify that all source data is stable and will not be altered during the process.
353+
350354
## Examples
351355

352356
### A. Load from a public storage account
@@ -850,6 +854,10 @@ When using OneLake as the source, the user must have **Contributor** or higher p
850854

851855
The COPY statement accepts only UTF-8 and UTF-16 valid characters for row data and command parameters. Source files or parameters (such as `ROW TERMINATOR` or `FIELD TERMINATOR`) that use invalid characters might be interpreted incorrectly by the COPY statement and cause unexpected results such as data corruption, or other failures. Make sure your source files and parameters are UTF-8 or UTF-16 compliant before you invoke the COPY statement.
852856

857+
To ensure reliable execution, the source files and folders must remain unchanged throughout the duration of the COPY INTO operation.
858+
- Modifying, deleting, or replacing any referenced files or folders while the command is running may cause the operation to fail or result in inconsistent data ingestion.
859+
- Before executing COPY INTO, verify that all source data is stable and will not be altered during the process.
860+
853861
<a id="limitations-for-onelake-as-source-public-preview"></a>
854862

855863
## Limitations for OneLake as source

0 commit comments

Comments
 (0)