model database stuck on Restore

  • How could the CLeanup Task result in the model database going into (recovering) mode ?

  • When the database was checking for errors during the maintenance plan it when into recovery mode. So for the time being I just backing up the model database. Last night plan ran fine.

  • sufiyan.sarguroh (7/25/2012)


    How could the CLeanup Task result in the model database going into (recovering) mode ?

    It can't. They were unrelated errors.

    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
  • gkuiper (7/25/2012)


    When the database was checking for errors during the maintenance plan it when into recovery mode. So for the time being I just backing up the model database. Last night plan ran fine.

    CheckDB (checking for errors) cannot cause a DB to go into the recovering state. You need to run CheckDB on model, just like every database.

    The root cause is that someone, somehow ran BACKUP DATABASE mode WITH NORECOVERY or BACKUP LOG model WITH NORECOVERY. It should be in the SQL error log, check there for the backup log entry, it may give you some indication who ran the command.

    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
  • Hello,

    I've got the same problem. the model database is "recovering". I checked the maintenance plan and I saw that the box "Back up the tail of the log, and leave the database in the restoring state" was cheked.

    Now I think thats my problem!

    Can I just uncheck the box and rerun the maintenance plan?

    Backup type: Transaction Log

    Database: all databases

    Kind Regards,

    Jeremy Alberts

  • Run RESTORE DATABASE model WITH RECOVERY, then go and fix that maintenance plan. The 'backup the tail of the log' is for disaster scenarios

    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
  • Thanks for your reply.

    Would doing what you just told me change anything in the current database? Would users lose data?

    Jeremy

  • It'll recover the model database, that's all. A restore statement run against a particular database cannot affect any other database on the server.

    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
  • Thanks,

    I'll give it a try tomorrow!

    regards,

    Jeremy

  • Gail,

    I did wat you sugested.

    Ran into a error though;

    BackupTapeFile::OpenMedia: Backup device '{A61601E7-5888-4F14-8FF3-F4E298005F23}1' failed to open. Operating system error 2(failed to retrieve text for this error. Reason: 15105).

    Now what if i only restorede the transactions logs. Would that be enough?

    Regards,

    Jeremy

  • OS Error 2, I believe, is file not found. Either you have the name or path wrong.

  • Thanks guy's!

    Got it back up and running.

    Regards,

    Jeremy

Viewing 12 posts - 16 through 26 (of 26 total)

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