The Art of SQL Server FILESTREAM - Red Gate Software

Chapter 7: FILESTREAM Database AdministrationAs you can see, SQL Server cannot fix an inconsistency error of this type. If it findsa foreign file in the FILESTREAM data container, it will return an error, butDBCC CHECKTABLE or DBCC CHECKDB will not remove the unwanted file. You mustremove it yourself to fix the corruption.Corruption can leak into your backup filesNote that, if you take a backup of the database, the backup will also include the orphaned file. If yousubsequently restore the backup, the new database will be corrupted as well.Before moving on, delete the orphaned file from the FILESTREAM data container,then run DBCC CHECKDB again, to make sure that the database is no longer in acorrupted state.Corruption caused by deleting the garbage filesmanuallyAs discussed earlier in the Garbage files and recovery models section, there is sometimes adelay before garbage files are deleted. If you lose patience and delete garbage files yourself,you may create a problem for the garbage collector, as it will try to remove files that nolonger exist.If you have been following through with the example over the previous sections, theItems table in NorthPole database has only one record. Go to the FILESTREAM datacontainer and note down the name of the file. Next, run the script in Listing 7-17 toupdate the FILESTREAM data value. The update operation will generate a new file withthe modified value and the old file will become garbage.292