• SQL Server doesn't. Corruption is, in the vast majority of cases due to a faulty IO subsystem. That means that there's a problem somewhere in your drives, san controller, fibre switch, firmware, cables, etc.

    If you want help fixing, run the following and post the fill and unedited results

    DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

    Take a look at this article. http://www.sqlservercentral.com/articles/65804/

    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