MS SQL DBLog file huge

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
LVL 1
John DarbyPMAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dustin SaundersDirector of OperationsCommented:
Is your DB bulk logged, and if so, does it need to be?
0
John DarbyPMAuthor Commented:
I don't believe so
0
John DarbyPMAuthor Commented:
How do I set to minimal logging and reduce the size of the DBlog.ldf file?
0
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

Dustin SaundersDirector of OperationsCommented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Scott PletcherSenior DBACommented:
"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
Jason clarkDBA FreelancerCommented:
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
John DarbyPMAuthor Commented:
Thank you for your help!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.