Symptoms
Assume that you save your database files in Azure Premium Storage. When you run DBCC CHECKDB on the database in SQL Server 2014, you may receive error messages that resemble the following:
Msg 1823, Level 16, State 2, Line 3
A database snapshot cannot be created because it failed to start.
Msg 1823, Level 16, State 8, Line 3
A database snapshot cannot be created because it failed to start.
Msg 5120, Level 16, State 147, Line 3
Unable to open the physical file blob_storage_URL_path. Operating system error 24: "24(The program issued a command but the command length is incorrect.)".
Msg 7928, Level 16, State 1, Line 3
The database snapshot for online checks could not be created. Either the reason is given in a previous error or one of the underlying volumes does not support sparse files or alternate streams. Attempting to get exclusive access to run checks offline.
Msg 5030, Level 16, State 12, Line 3
The database could not be exclusively locked to perform the operation.
Msg 7926, Level 16, State 1, Line 3
Check statement aborted. The database could not be checked as a database snapshot could not be created and the database or table could not be locked. See Books Online for details of when this behavior is expected and what workarounds exist. Also see previous errors for more details.
Resolution
This problem was first fixed in the following cumulative update for SQL Server:
Cumulative Update 8 for SQL Server 2014 Service Pack 1
Cumulative update 2 for SQL Server 2014 SP2
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Premium Storage support for Data files on Azure Storage
Create a SQL Server 2014 Database directly on Azure Blob storage with SQLXI
Learn about the terminology Microsoft uses to describe software updates.
