Post reply

if database crashes how to recover in sql server 2008

  • March 1, 2011 at 12:32 am

    #235248

    Hi..

    i am using sql server 2008..

    if suddenly database crashes then how to recover it?

    what about data?

  • March 1, 2011 at 1:23 am

    #1292745

    This is a very generic question. You may refer some books for the same.

    M&M

  • March 1, 2011 at 4:37 am

    #1292814

    A simple answer would be "Restore the Backup".

    --------------------------------------------------------------------------------------------------
    I am just an another naive wannabe DBA trying to learn SQL Server

  • March 1, 2011 at 6:25 am

    #1292864

    i have an old backup..

    i have modified database after that backup.

    what about that data(modifications)?

    i want that data(modifications) also..

  • March 1, 2011 at 10:25 pm

    #1293325

    goldspoon (3/1/2011)

    i have an old backup..

    i have modified database after that backup.

    what about that data(modifications)?

    i want that data(modifications) also..

    Take tail log backup. Then restore the old backup and the tail log backup. The stored database will have your modifications.

  • March 1, 2011 at 11:45 pm

    #1293341

    Depends what kind of crash and how bad. If the server is running and the database is still connected and the log is intact, you can do a tail-log backup. Otherwise you will lose that data.

    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

  • March 2, 2011 at 9:49 pm

    #1293841

    thanks for reply..

    my doubt is

    what if the server is not running and database is not connecting?

    then how to take tail log backup..

  • March 2, 2011 at 11:45 pm

    #1293858

    If you can't get SQL to start, then see 'Otherwise you will lose that data'

    You don't need to be able to connect to the DB to do a tail log backup. SQL running and the database still listed is usually enough. Depends how bad the damage is.

    This is why the interval between log backups is so important.

    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

  • March 3, 2011 at 12:24 am

    #1293870

    thank u ..

    Actually i'm taking backup for every 4 hrs.. with in 4 hrs if database crashes then i have to lose data if SQL server should not run(as u mentioned)

    it is must and should the SQL server should run otherwise the data will be lost .. other than sql server running, is there any option to recover the data.. ?

    and other than tail log backup is there any option to recover data?

  • March 3, 2011 at 12:46 am

    #1293873

    Full backup every 4 hours or transaction log?

    Will your business tolerate up to 4 hours of data loss? If not, you really need to increase the frequency of the log backups.

    As for other methods of recovery, depends on how bad the disaster was and what the situation is. If the data file is lost, no.

    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

  • March 3, 2011 at 1:17 am

    #1293876

    full backup every 4 hrs..

  • March 3, 2011 at 8:02 am

    #1294038

    And your log backups?

    Tail log backup requires full recovery, full recovery requires regular log backups. Please read through this: http://www.sqlservercentral.com/articles/64582/

    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

  • March 14, 2011 at 6:38 am

    #1298283

    Thanks for the reply..

    In how many ways the database will be crashed?

    in which cases it can be recovered and in which cases it can't?

  • March 14, 2011 at 6:47 am

    #1298287

    There are so many ways things could go wrong...

    If you have backups, full and log, you can recover at least to the last log backup. If the DB is online and the log file undamaged you can restore to point of failure.

    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

  • March 4, 2021 at 11:29 am

    This was removed by the editor as SPAM

Viewing 15 posts - 1 through 15 (of 16 total)

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