See the SQL Server errorlog for more information. 01:35:44.45 spid98 Database 'DatabaseName' cannot be opened. Elapsed time: 0 hours 0 minutes 9 seconds. 01:35:44.07 spid98 DBCC CHECKDB (DatabaseName) WITH all_errormsgs, no_infomsgs, data_purity executed by Domain\UserName found 0 errors and repaired 0 errors. 01:35:44.04 spid75 E:\SQLData\MSSQL.1\DatabaseName.mdf:MSSQL_DBCC16: Operating system error 1784(The supplied user buffer is not valid for the requested operation.) encountered. The errors produced were as below (borrowed from Jonathan's blog post): As things progressed it dawned on me that his CHECKDBs were fine using regular database snapshots, but failed using the automatically-created snapshots, which use NTFS alternate streams (see this blog post where I explain about them).
#Www diskkeeper movie
I was settling down to watch a movie with my laptop nearby when I got involved helping fellow-MVP Jonathan Kehayias ( blog | twitter ).
At the time I'd only seen the issue a couple of times so thought no more about it until a few weeks ago.
A couple of years ago I blogged about 3rd-party file system filter drivers and how if they're not coded correctly to cope with NTFS alternate streams they will cause all kinds of weird corruption errors to be reported when DBCC CHECKDB is running.
0 kommentar(er)
