March 22, 2010 at 3:21 am
Not urgent, but irritating.
I've recently started working through the MS training kit book for 70-433. One of the databases (Adventureworks2008) uses Filestream. I haven't done anything with this db yet, so all I need to do when it goes suspect is delete it and drag the files from the cd again. And when I attach the files everything is fine - I can run queries against it and all seems happy.
Then it will go suspect, usually when I start SS, but sometimes it is fine then but goes suspect later.
In the log it says:
"Unknown,FILESTREAM's file system log record 'placeholder.txt' under log folder '\\?\C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\Documents\$FSLOG' is corrupted."
Placeholder.txt is just a text file with "this is a placeholder." in it, and I can still open it in Notepad.
DBCC CHECKDB (AdventureWorks2008, REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS, ALL_ERRORMSGS; responds with:
"Msg 5028, Level 16, State 4, Line 1
The system could not activate enough of the database to rebuild the log.
Msg 7909, Level 20, State 1, Line 1
The emergency-mode repair failed.You must restore from backup."
As I've said, all I need to do now is delete it all and drag the files over again, as I've done nothing to it. However, I am interested to know why it behaves in this way, and if it could be an indication of a more serious issue. Once I start playing with it I will of course be taking backups.
BrainDonor.
March 24, 2010 at 7:33 am
I had the exact same problem with the same source (the 70-433 book CD), but found the fix here:
"The fix to backup successfully, is to delete the file
MSSQL10.MSSQLSERVER\MSSQL\DATA\Documents\$FSLOG\placeholder.txt
This file causes the initial backup to fail. Afterwards, you should be okay."
Works perfectly for me since.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply