Recent content by lacuruv

Googling it, it looks like somehow the database was damaged. I found this thread SQL Server Repair Toolbox which may have more information.But it looks like the best solution is to roll back your database to a stable state "if possible."