I have an issue running DBCC CHECKDB on one of our SQL Server Azure wm's .
DBCC CHECKDB are runing just fine on all databases on the server except one,
which fails with the error below.
The one database that fails has it's data files in Azure premium storage (https:\xxx.xxxxx.blob.core.windows.net\xxxx), the rest is on
classic storage, as is the Azure VM server itself.
While running the DBCC Check db against the failing database, it seems that the DBCC snapshot file generated, does not get cleaned up
correctly which I believe to be the cause of the error.(https://xxxxxxxx.blob.core.windows.net/xxxx/xxxxxxxmdf_MSSQL_DBCC22) The file can be see from the Azure storage interface.
I cannot find a solution for this, so any help will be much appreciated!
Error message:----------------------------------------------------------------------------
Msg 1823, Level 16, State 2, Line 1
A database snapshot cannot be created because it failed to start.
Msg 1823, Level 16, State 8, Line 1
A database snapshot cannot be created because it failed to start.
Msg 5120, Level 16, State 144, Line 1
Unable to open the physical file "xxxxxx.xxxxxxx.xxxxxx/xxxx/xxxxxx.mdf_MSSQL_DBCC22". Operating system error 80: "80(The file exists.)".
Msg 7928, Level 16, State 1, Line 1
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 1
The database could not be exclusively locked to perform the operation.
Msg 7926, Level 16, State 1, Line 1
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.