Skip to content

Updated remarks for COPY INTO #10204

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from
Closed

Updated remarks for COPY INTO #10204

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1c72ca6
Updated remarks for COPY INTO
periclesrocha Oct 15, 2025
be678c6
Update copy-into-transact-sql.md
periclesrocha Oct 15, 2025
403b0a8
Update date and clarify COPY INTO operation details
WilliamDAssafMSFT Oct 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion docs/t-sql/statements/copy-into-transact-sql.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ description: Use the COPY statement in Azure Synapse Analytics and Warehouse in
author: WilliamDAssafMSFT
ms.author: wiassaf
ms.reviewer: procha, mikeray, fresantos
ms.date: 07/29/2025
ms.date: 10/15/2025
ms.service: sql
ms.subservice: t-sql
ms.topic: reference
Expand Down Expand Up @@ -347,6 +347,10 @@ The COPY statement accepts only UTF-8 and UTF-16 valid characters for row data a

The MAXDOP query hint is not supported with COPY INTO.

To ensure reliable execution, the source files and folders must remain unchanged throughout the duration of the `COPY INTO` operation.
- 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.
- Before executing `COPY INTO`, verify that all source data is stable and will not be altered during the process.

## Examples

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

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.

To ensure reliable execution, the source files and folders must remain unchanged throughout the duration of the COPY INTO operation.
- 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.
- Before executing COPY INTO, verify that all source data is stable and will not be altered during the process.

<a id="limitations-for-onelake-as-source-public-preview"></a>

## Limitations for OneLake as source
Expand Down