Like Us
Plus One
Follow Us
Search
 Author James Love  Views 855 View Original Article

EDIT: Upon closer inspection of the DBCC CHECKDB output, running REPAIR_ALLOW_DATA_LOSS might not have actually been the fix. The restart of SQLServer service, or dropping the database into Single User then back to Multi may have done the trick. Try these two steps before doing the full DBCC. As part of a project I’m working on, I’m flooding my development site with GBs of (sample) documents. This means the database fills quite quick and to restart my scenario I’m deleting the …
View Original Article