Solved

MS SQL DBLog file huge

Posted on 2016-07-18
7
42 Views
Last Modified: 2016-07-19
Greetings, the *.ldf file has suddenly grown large. Should I force a commit or rollback? Not sure how to determine next step. The volume hosing the DB is nearing 0 bytes.

Thanks,
johnD
0
Comment
Question by:johndarby
7 Comments
 
LVL 12

Expert Comment

by:Dustin Saunders
ID: 41717845
Is your DB bulk logged, and if so, does it need to be?
0
 
LVL 1

Author Comment

by:johndarby
ID: 41717852
I don't believe so
0
 
LVL 1

Author Comment

by:johndarby
ID: 41717899
How do I set to minimal logging and reduce the size of the DBlog.ldf file?
0
Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

 
LVL 12

Accepted Solution

by:
Dustin Saunders earned 250 total points
ID: 41717916
To shrink the log, you can right click on the database and go to Tasks>Shrink>File.  Be sure to change to the log file (attached 1&2).

You can set the recovery model to simple to reduce the overall size of the log file.  In most cases Simple should be fine, but if you have a requirement for bulk logs please consider that.

More info on shrinking the log file.
ee_shrink1.png
ee_shrink2.png
ee_shrink3.png
0
 
LVL 69

Assisted Solution

by:Scott Pletcher
Scott Pletcher earned 125 total points
ID: 41717921
"Large" is nebulous.  But first, you need to check if there is an open transaction in the db.

USE your_db_name
DBCC OPENTRAN

If you get a response along the lines of:
No active open transactions.

You can proceed with a log shrink, being aware that the log may grown again if another large trans comes thru.
CHECKPOINT:
DBCC SHRINKFILE(2, <preferred_max_log_size_in_mb> )

DO NOT USE THE GUI TO DO A LOG SHRINK!  The gui can be flaky, and for log shrink especially, you can't risk any flakiness.  Without a working log, the db cannot be used,.

But if there is an open tran(s), you need to resolve those first.
0
 
LVL 8

Assisted Solution

by:Jason clark
Jason clark earned 125 total points
ID: 41718211
You need to back up your log file and free up space and check If you set the recovery to simple from full, then shrink the log file then you can set it back to full recovery if you need to. read here for more options: https://support.microsoft.com/en-in/kb/317375
0
 
LVL 1

Author Closing Comment

by:johndarby
ID: 41719702
Thank you for your help!
0

Featured Post

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

Question has a verified solution.

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

This article explains how to reset the password of the sa account on a Microsoft SQL Server.  The steps in this article work in SQL 2005, 2008, 2008 R2, 2012, 2014 and 2016.
For both online and offline retail, the cross-channel business is the most recent pattern in the B2C trade space.
Using examples as well as descriptions, and references to Books Online, show the different Recovery Models available in SQL Server and explain, as well as show how full, differential and transaction log backups are performed
Viewers will learn how to use the INSERT statement to insert data into their tables. It will also introduce the NULL statement, to show them what happens when no value is giving for any given column.

828 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