• Restore then, run a checkDB with data_purity, update all stats with fullscan, run DBCC updateusage. Then consider whether you're going to change the compatibility level

    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