sephrobbertse (8/30/2012)
Hi, managed to put the DB in emergency mode and do a dbcc repair.
So I assume you have no good backup, since emergency mode repair is the absolute last resort for when there is no backup and every other attempt at resolving the problem has failed.
I strongly suggest that after you've ensured that you database is logically consistent (it probably isn't after the repair), you get a backup routine in place so that if this happens again you don't have to resort the the absolute last chance option.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability