Äiskeeper issued a fix a couple of weeks back, and Microsoft Product Support also put out a blog post with some details. You can read Jonathan's more in-depth recounting of the story on his blog here. Lo-and-behold, it turned out to be a Diskeeper 10 filter driver that had a bug in it. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |