Azure SQL Database (single database and Managed Instance) enables you to load files from Azure Blob Storage. If you experience issues while you are loading files from Azure blob storage, below are some suggestions on steps you can take to troubleshoot and mitigate the issue.
BULK INSERT
or BULK INSERT
check that you are using supported syntax in this statement. As an example, if you are trying to load data via network share path note that this option is not supported in Managed Instance.
EXTERNAL DATA SOURCE
with type BLOB_STORAGE
targeting the URL of the blob storage where you placed the files that should be restored to your database.CREDENTIAL
to SQL Server 2017 and try to load the files. If you are troubleshooting the issue on Managed Instance make sure that SQL Server is in the subnet that is within the same VNet as the Managed Instance.SECRET
option of the CREATE DATABASE SCOPED CREDENTIAL
statement valid. The most common errors in SAS token parameters are:
?
is not removed from the beginning of the SAS token because the Azure portal generates SAS token with the leading ?
. Remove this character if you see it.se
(expiry date) property is set to some value in the past (note that this is UTC time).st
(start date) property is not in the past (note that this is UTC time).sp
(permission) property should allow reading the file on the storage account.sip
(ip range) remove this parameter if it is present in SAS token.You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.