system databases crruption

  • Hi all,

    If system databases got corrupted and we don't have backups of the system databases... how to handle this situation

  • Well, if you don't have backups of the system databases, someone's not doing their job.

    If you happen to end up in that situation, then update your resume, rebuild the system databases (it's documented in BoL) then spend a few entertaining days attaching the databases, updating configuration settings, recreating all the lost logins, linked servers, server-level permissions, jobs, maintenance plans and SSIS packages.

    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
  • Of course now you never forget to make (and check) back-ups from the system databases :w00t:

    Without a backup you'll need to re-install SQL and manually adjust all changed settings to be the same as the instance with the corrupt databases. Then attach all user databases to the new instance. Finally add all jobs, SSIS packages, triggers, etc.

    Perhaps some other steps must also be done, but this will give you a good starter.

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **
  • HanShi (6/4/2013)


    Without a backup you'll need to re-install SQL

    Rebuilding the system databases is enough, reinstall would be a waste of time.

    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

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply