From 1c72ca624ecdf9f26cb60e77afd9de907332d6fc Mon Sep 17 00:00:00 2001 From: "Pericles (Peri) Rocha" <12371744+periclesrocha@users.noreply.github.com> Date: Wed, 15 Oct 2025 16:13:39 -0700 Subject: [PATCH 1/3] Updated remarks for COPY INTO --- docs/t-sql/statements/copy-into-transact-sql.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/t-sql/statements/copy-into-transact-sql.md b/docs/t-sql/statements/copy-into-transact-sql.md index 90f702d9ef0..fc6003a6fc3 100644 --- a/docs/t-sql/statements/copy-into-transact-sql.md +++ b/docs/t-sql/statements/copy-into-transact-sql.md @@ -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 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. + ## Examples ### A. Load from a public storage account From be678c6176c844cc519561d3ac5d6ea8c2cfb6cf Mon Sep 17 00:00:00 2001 From: "Pericles (Peri) Rocha" <12371744+periclesrocha@users.noreply.github.com> Date: Wed, 15 Oct 2025 16:17:02 -0700 Subject: [PATCH 2/3] Update copy-into-transact-sql.md --- docs/t-sql/statements/copy-into-transact-sql.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/t-sql/statements/copy-into-transact-sql.md b/docs/t-sql/statements/copy-into-transact-sql.md index fc6003a6fc3..8b9834c98b5 100644 --- a/docs/t-sql/statements/copy-into-transact-sql.md +++ b/docs/t-sql/statements/copy-into-transact-sql.md @@ -854,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. + ## Limitations for OneLake as source From 403b0a8fc2e0102d17fb817d322772a8444b75c0 Mon Sep 17 00:00:00 2001 From: William Assaf MSFT <74387232+WilliamDAssafMSFT@users.noreply.github.com> Date: Wed, 15 Oct 2025 21:13:46 -0700 Subject: [PATCH 3/3] Update date and clarify COPY INTO operation details Updated the date and improved wording for clarity regarding the COPY INTO operation. --- docs/t-sql/statements/copy-into-transact-sql.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/t-sql/statements/copy-into-transact-sql.md b/docs/t-sql/statements/copy-into-transact-sql.md index 8b9834c98b5..76a106c951a 100644 --- a/docs/t-sql/statements/copy-into-transact-sql.md +++ b/docs/t-sql/statements/copy-into-transact-sql.md @@ -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 @@ -347,9 +347,9 @@ 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 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. +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