Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have two SQL Agent jobs which are scheduled to run at different intervals. The first job runs a full backup once a day. The second job runs transaction log backups every fifteen minutes.

As the database has grown, the full backup is taking longer than originally planned (even with compression). And I've noticed from my logs that the transaction log backups are now running at the same time.

Should I change the schedule of the transaction log backup so that doesn't run when the full backup is running? Does it matter?

share|improve this question
up vote 22 down vote accepted

As you can see on this table, there is no conflict between Full backup and Log backup. They can occur at same time, and, when log backup completes, log will not be cleaned until full backup (or diff backup) completes.

share|improve this answer
3  
That is one of those tables that you just want to save for later. Thanks for the link. +1 – Thomas Stringer Aug 6 '11 at 5:09

No, there is no need to do this.

share|improve this answer

No, it does not. There is no need to make any changes. The full database backup does not corrupt the transaction log and does not truncate it. Only when you make a transaction log backup the transaction log will be truncated.

share|improve this answer
    
Aren't you telling the same thing Alex_L posted a while ago? – dezso Nov 25 '15 at 10:11
    
We have similar answers – Alexandr Omelchenko Nov 25 '15 at 11:00

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.