jdbrown239 (9/10/2012)
Wouldn't last nights backup have the same corruption? If so I would have to use one from a few days ago.
Depends when the corruption happened. When was your last clean checkDB?
Full recovery model and log backups?
Would DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS fix the issue?
Sure, if you accept that it allows data loss.
btw, would you mind re-running the checkDB and specifying the No_InfoMsgs option, then posting that output here? Trying to sort the errors from the useless info is time consuming.
DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
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