Solved

Sql 2012 log file huge

Posted on 2012-12-21
5
2,060 Views
Last Modified: 2013-05-29
Hello,
I'm running a SQL 2012 Always-On Group with a DB inside.
The DB is set to Full logging.  However after doing a full backup the log file is not going down in size.
0
Comment
Question by:casit
5 Comments
 
LVL 22

Assisted Solution

by:Steve Wales
Steve Wales earned 250 total points
ID: 38713453
Full backups aren't what cause a log file to be able to be shrunk.

You need to do a transaction log backup in order to flag it for reuse.

Have a read of these two blog entries from Kimberly Tripp:

http://www.sqlskills.com/blogs/kimberly/post/8-steps-to-better-transaction-log-throughput.aspx
http://www.sqlskills.com/blogs/kimberly/post/transaction-log-vlfs-too-many-or-too-few.aspx

Oh, and here's the relevant piece from SQL Server 2012 Books Online:
http://msdn.microsoft.com/en-us/library/ms190925.aspx
0
 
LVL 68

Expert Comment

by:Qlemo
ID: 38713706
Exactly. Full Recovery Mode requires to perform DB and Transaction Log backups. Usually you perform the log backup more often (say once every 4 hours), while the DB backup is once a day or even less often. It doesn't matter whether the DB backup is differential or full.
0
 

Author Comment

by:casit
ID: 38713878
I did both a full backup and also a trans log backup and the size is still the same.
0
 
LVL 22

Expert Comment

by:Steve Wales
ID: 38713931
The transaction log backup in and of itself won't shrink the log file - it just enables the space to be reused.  If you had never done a log backup before and the log file had grown large, extra steps need to be taken to shrink the logfile and then regrow in a controlled manner to a better size.

The two blog posts I listed above cover this in great detail and I don't want to steal Kimberly's work by replicating it here.   Have a read of those two posts and come back here with any other questions.

It's important to understand the impact of large numbers of VLF's brought about by incorrect sizing of your transaction log through autogrow, the impact autogrow can have on performance as well as the proper steps to shrink the transaction log back to a reasonable size.
0
 
LVL 42

Accepted Solution

by:
EugeneZ earned 250 total points
ID: 38715752
you are probably have active transaction there
run this query to see it:

select name, database_id, log_reuse_wait, log_reuse_wait_desc from sys.databases

more:

Unable to shrink the transaction log of SQL Server database

http://zarez.net/?p=913
0

Featured Post

Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

Question has a verified solution.

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

Suggested Solutions

I wrote this interesting script that really help me find jobs or procedures when working in a huge environment. I could I have written it as a Procedure but then I would have to have it on each machine or have a link to a server-related search that …
Introduction In my previous article (http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/SSIS/A_9150-Loading-XML-Using-SSIS.html) I showed you how the XML Source component can be used to load XML files into a SQL Server database, us…
Via a live example, show how to shrink a transaction log file down to a reasonable size.
Using examples as well as descriptions, and references to Books Online, show the documentation available for datatypes, explain the available data types and show how data can be passed into and out of variables.

911 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

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now