Log File full / Database Down

  • I am a newbie and we ran a script that made our logfile drive go to 100%. We tried to do a restore of the database and now the database will not come up. Any suggestions would be appreciated.

  • What is the status of your databse as per management studio?

    What error you have in your error log?

    ----------------------------------------------------------------------------------------------------------------------------------------------------
    Roshan Joe

    Jeff Moden -Forum Etiquette: How to post data/code on a forum to get the best help[/url]

  • Why did you restore a dB ?

    Instead you would have been taken a log backup that should cleaned the log file.

    Is it a production database ?

    [font="Tahoma"]
    --SQLFRNDZ[/url]
    [/font]

  • We are currently not getting any errors . The database status show (inRecovery). There is a lot of read on the log file directory.

  • It is a production database. We restored it since the transaction we ran did not complete and we had to remove it.

  • How did you restore the database?.

    While restoring did you add with norecovery?

    ----------------------------------------------------------------------------------------------------------------------------------------------------
    Roshan Joe

    Jeff Moden -Forum Etiquette: How to post data/code on a forum to get the best help[/url]

  • Whats current Log size? and database size?

    if its showing Inrecovery then wait for some time let database recover and then shrink database log file or change recovery mode to simple

  • Please read through this - Managing Transaction Logs[/url] and - http://www.sqlservercentral.com/articles/Transaction+Log/72488/

    Don't just shrink or change recovery models without analysing and knowing the effects of the actions.

    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
  • Hmm, now that the db is in recovering status, you may not be able to (temporarily) add another log file on a different drive to allow the db to keep processing while you clean up.

    Instead, see if there is another db(s) with large log file(s) that you can afford to do w/o for a few seconds/minutes while you move their log file(s) to another drive.

    That is, your log drive needs free space to do work in. It's full. You can free up space on that drive by moving one (or more) of the other log files to a different drive temporarily).

    That might (or might not) allow the original db to complete recovery.

    If you want to try moving an existing db's log to another drive temporarily, let me know, and I can help you build a script to do it. NOTE: you should use ALTER DATABASE, NOT detach to do this.

    SQL DBA,SQL Server MVP(07, 08, 09) A socialist is someone who will give you the shirt off *someone else's* back.

Viewing 9 posts - 1 through 8 (of 8 total)

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