Final answer:
In Azure Synapse Analytics T-SQL, the COPY INTO command requires a Shared Access Signature (SAS) to authenticate to Blob storage.
Step-by-step explanation:
In Azure Synapse Analytics T-SQL, the COPY INTO command must use a Shared Access Signature (SAS) to authenticate to Blob storage. This means that when using the COPY INTO command, you need to provide a SAS token to access the Blob storage.
The statement that the 'COPY INTO' command in Azure Synapse Analytics T-SQL must use a Shared Access Signature (SAS) to authenticate to Blob storage is false. While a SAS is one authentication method, managed identities and storage account keys can also be used.
In Azure Synapse Analytics T-SQL, the COPY INTO command is used to copy data from various sources into a Synapse SQL pool. It is false that the COPY INTO command must use a Shared Access Signature (SAS) to authenticate to Blob storage. While SAS is one of the authentication methods that can be used for accessing Azure Blob Storage, there are also other methods like using managed identities for Azure resources or providing the storage account key. Therefore, while a SAS can be used, it is not the only method for authentication.