mitzyturbo (1/17/2013)
Cheers Gilla, have read a few blogs and articles about it and it would appear that if all else fails, recreate the database and import the data back across.
That's what I'd recommend. There's no automated fix for this, checkDB can't repair it. Dropping objects is not going to fix it.
Don't suppose you have any links to threads about doing this in a nice powershell script??
What's powershell? 😀
Sorry, that's not something I use much, so don't know very well.
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