• With no clean backups you don't really have any good options. This is why regular integrity checks are essential (regular enough that restore from a clean backup is always an option)

    CheckDB with repair allow data loss (because without a clean backup there's no other option available), accept that you will lose data. How much, I can't tell, don't have the time right now to analyse 30 oddpages of checkDB output. Once complete, run checkDB again without a repair option, see if everything's fixed. If not, repeat the repair and the check until everything is fixed.

    Once you've got rid of the corruption, fix your backup strategies and have a long, hard look at the IO subsystem, corruption doesn't just happen for no reason.

    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

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass