Post reply

Backing up the transaction logs - whats the need to do so?

  • June 4, 2006 at 4:26 pm

    #113305

    Is it worth me backing up teh transaction log files when scheduling a backup? What am I missing if i decide to not backup the transaction logs?

    Thanks

    Tryst

  • June 4, 2006 at 8:27 pm

    #641597

    Firstly, if the recovery model of your database set to SIMPLE, then the answer is NO!

    Secondly, do you have many transactions (inserts, update and deletes) against that database? If yes, then you should consider transaction log backups. This has the advantage of keeping check on the growth of your transaction log size.

    Thirdly, is the database very large and you only have a small backup window? If so, then performing full backups on a weekly basis, with daily differential backups and transaction log backups every few minutes might be the way to go.

    Lastly, do you need to have point-in-time recovery? If so, then frequent transaction log backups (together with your full and differential backups) will enable you to recover your database to a desired point-in-time.

     

  • June 5, 2006 at 10:51 am

    #641789

    I think Paul's last point is the most important.  Your business's tolerance for data loss dictates whether point-in-time recovery, and therefore log backups, is required.

    If you make full backups with no log or differential backups, you'll only be able to recover to the point-in-time when the full backup was made. 

    Greg

    Greg

  • June 6, 2006 at 2:38 am

    #641883

    Just another point..........if your database is set to 'full' recovery and you don't backup the transaction log........ you will come in one morning to find that the transaction log has filled the hard drive, no one can get into the system and the boss has steam coming out of his ears...........

    Madame Artois

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

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