Solved

SQL transaction log growth during maintenance plan

Posted on 2011-09-06
8
575 Views
Last Modified: 2012-05-12
I have a reasonably large database (25GB) with a backup plan:

Full database backup daily at 10pm
Transaction log backup every 30minutes between 8am - 9.30pm

Additionally there is a maintenance plan which runs at midnight.

When the maintenance plan runs the transaction log grows to about 6GB.
Why is this? Could it/should it be avoided?

When the transaction log backups start in the morning, I "think" the log is cleared down (when I checked at 9am it was 98% free space) but after several hours (a few more transaction log backups) it eventually shrinks back to 10MB (and will remain roughly this size throughout the day).
Why is this? Could it/should it be avoided?

Thanks

Lee
0
Comment
Question by:tickett
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
  • 2
  • +1
8 Comments
 
LVL 8

Expert Comment

by:Andrei Fomitchev
ID: 36487862
What your maintenance plan does? - What steps are included in it?

There is SHRINK step - it decreases LOG SIZE.
0
 
LVL 11

Author Comment

by:tickett
ID: 36487906
Check Database Integrity
Reorganize Indexes
Update Statistics
Shrink Database
Clean Up History

And the option is set to "Return freed space to the operating system".
0
 
LVL 19

Expert Comment

by:Bardobrave
ID: 36488376
As you backup your transaction log every half an hour, it's probably at very low size all over the day, as it get shrinked after the backup.

However, when you run your maintenance plan, lots of operations get made and are pushed to the log.

I would try to run the maintenance plan operations separately seeing the growth of the transaction log between each one of them. If there is any of the operations specially hard with operations on transaction log I would try to make a log backup after that operation.
0
Complete VMware vSphere® ESX(i) & Hyper-V Backup

Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)

 
LVL 11

Author Comment

by:tickett
ID: 36488932
I think I'm more looking for a best practice solution? It almost makes sense why it is happening (although it definitely doesn't seem right- surely SQL is designed better than that!?). This would be a common issue and there must be a common solution/best practice approach?

L
0
 
LVL 19

Expert Comment

by:Bardobrave
ID: 36489145
Sincerely I don't know, I'm not a dba, only have some knowledge of it.
0
 
LVL 21

Expert Comment

by:mastoo
ID: 36489677
You might rethink the reorg indices nightly.  They might be happy with a weekly index maintenance depending on the database volatility.

And regardless, don't worry about shrinking the database each night.  You need sufficient disk space for the max size each day anyway, so you might as well let it stabilize at the larger size.
0
 
LVL 11

Author Comment

by:tickett
ID: 36501956
Thanks Bardobrave

mastoo: can you state a source? i think what you're saying is probably right but was hoping for more reasoning/documented practice.

I have found scripts in the past which identify certain indexes based on the number of pages and fragmentation- so it might be that i need to drop the maintenance plan and actually run my own custom script to only process the tables/indexes which need to be improved.

L
0
 
LVL 21

Accepted Solution

by:
mastoo earned 500 total points
ID: 36502037
A source as to frequency of index maint?  If we can count microsoft mvp discussions as authoritative, this discusses it and has a few good links itself:

http://social.msdn.microsoft.com/Forums/en-US/sqlgetstarted/thread/aecc91b8-d0b8-4567-9c01-155c5c28306c/

and yes, tailoring your index maint can reduce the impact but is just slightly more work
0

Featured Post

MIM Survival Guide for Service Desk Managers

Major incidents can send mastered service desk processes into disorder. Systems and tools produce the data needed to resolve these incidents, but your challenge is getting that information to the right people fast. Check out the Survival Guide and begin bringing order to chaos.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Why is this different from all of the other step by step guides?  Because I make a living as a DBA and not as a writer and I lived through this experience. Defining the name: When I talk to people they say different names on this subject stuff l…
In this article we will get to know that how can we recover deleted data if it happens accidently. We really can recover deleted rows if we know the time when data is deleted by using the transaction log.
Via a live example, show how to extract information from SQL Server on Database, Connection and Server properties
Via a live example, show how to set up a backup for SQL Server using a Maintenance Plan and how to schedule the job into SQL Server Agent.

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question