Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 94
  • Last Modified:

SQL 2012 database log file too big, no disk space

Dear all,

I have MS SQL 2012 server and the transaction log file has grown too big and the partition where the log file resides is out of space. Unable to run queries due to this issue. Any help on what best to do in this scenario would be appreciated.

Dee
0
ghco
Asked:
ghco
  • 3
  • 3
  • 2
  • +3
1 Solution
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Are you performing transaction log backups? If you weren't then that explains the transaction log being growing without any kind of truncation.
So to solve your issue you'll need to perform ASAP a transaction log backup and then schedule regular transaction log backups.
0
 
Lee SavidgeCommented:
First of all why has this happened? Is the recovery model set to full or simple? If set to full, you MUST back up the database AND transaction log as part of your maintenance schedule.

If you don't your log file will simply increase until it runs out of disk space. This is perhaps the single most common problem that people face with a database.

So, what can you do? Well, if the disk is full, the application is not working, so try and do a database back up and then a transaction log backup to a different partition. Then when you've backed the transaction log up, you will need to shrink it.

https://msdn.microsoft.com/en-GB/library/ms189493.aspx

Try that, then come back to let us know if it has worked. There are things you can do if it doesn't work so don't worry.
0
 
ghcoAuthor Commented:
Thanks for the quick respond, the recovery model is set to simple. Will try what you suggested and let you know the outcome.

As an alternative can the log file be moved to another partition while the database is active?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Vitor MontalvãoMSSQL Senior EngineerCommented:
If the database is set to Simple then you can't perform transaction log backups. I'm wondering what can made the transaction log growing too much in a Simple Recovery model database. How big is the database and the transaction log file?

For moving a transaction log location you'll need to detach the database, copy the transaction log file to the new location and re attach the database.
0
 
ghcoAuthor Commented:
The database grew from 3GB to 40GB and the log file is 45GB. Apparently there was a massive entry to database table that wasn't necessary which made it grew, have tried deleting those entries but script wouldn't run because of the disk space issue.
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
A massive data task can really justifies the grow but then it would empty the transaction log when the task is done. Mind that emptying the tlog is not the same that shrinking it so it may be your case. Did you try to Shrink the transaction log to see if you can recall any free space? If not then it means that the transaction it still active (still running or waiting for a commit/rollback).
0
 
ZberteocCommented:
Use this script to shrink the log file:
USE [YourDatabase] 

ALTER DATABASE [YourDatabase] SET RECOVERY SIMPLE WITH NO_WAIT 

DBCC SHRINKFILE(N'YourDatabase_log', 1) 

Open in new window

where YourDatabase_log should be the logica file name of the transaction log file.
0
 
Scott PletcherSenior DBACommented:
Yes, use commands, not the gui, to shrink the log file.

USE [db_name]
DBCC SHRINKFILE(2, 4096)

That will shrink it to 4GB.  I wouldn't shrink too small, because when the log is forced to grow again, that will be very bad for performance.

Also, check to be sure that nothing is preventing the log from shrinking/being reused, with this command:

DBCC OPENTRAN
0
 
ghcoAuthor Commented:
Found an MSDN link that shows how to shrink the database/log file from the SQL Management Studio so this worked for us. Thanks for all the help.

https://msdn.microsoft.com/en-GB/library/ms190757.aspx
0
 
ZberteocCommented:
In that article under "Using Transact-SQL" section is exactly what I posted as a solution at: 41759429
0
 
Jason clarkDBA FreelancerCommented:
By querying the sys.databases catalog view you can see information describing the reason your log file may be waiting on truncate/reuse. see here to know other reasons for that: http://www.sqlmvp.org/transaction-log-is-too-big-or-growing-unexpectedly/
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 3
  • 3
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now