This problem is resolved in Microsoft SQL Server 2014. This problem occurs because SQL Server cannot create the internal snapshot database by using named streams when the database files are located on an ReFS volume.
If there are no users connected to the database, the DBCC CHECKDB command will obtain exclusive lock against the database, and then perform the checks against the database, instead of using the internal snapshot that it typically uses. Also see previous errors for more details. See Books Online for details of when this behavior is expected and what workarounds exist. The database could not be checked as a database snapshot could not be created and the database or table could not be locked. The database could not be exclusively locked to perform the operation.Ĭheck statement aborted. The error messages resemble the following: In Microsoft SQL Server 2012 or an earlier version of SQL Server, you may encounter error messages when you run the DBCC CHECKDB command for a database that has its files located on an Resilient File System (ReFS) -formatted volume. Microsoft SQL Server 2005 Developer Edition Microsoft SQL Server 2005 Enterprise Edition Microsoft SQL Server 2005 Enterprise X64 Edition Microsoft SQL Server 2005 Evaluation Edition Microsoft SQL Server 2005 Express Edition Microsoft SQL Server 2005 Standard Edition Microsoft SQL Server 2005 Standard X64 Edition Microsoft SQL Server 2005 Workgroup Edition SQL Server 2008 Developer SQL Server 2008 Enterprise SQL Server 2008 Express SQL Server 2008 Standard SQL Server 2008 Web SQL Server 2008 Workgroup SQL Server 2008 R2 Datacenter SQL Server 2008 R2 Developer SQL Server 2008 R2 Enterprise SQL Server 2008 R2 Express SQL Server 2008 R2 Standard SQL Server 2008 R2 Web SQL Server 2008 R2 Workgroup SQL Server 2012 Developer SQL Server 2012 Enterprise SQL Server 2012 Express SQL Server 2012 Standard SQL Server 2012 Web SQL Server 2012 Enterprise Core More.
0 kommentar(er)
