• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 492
  • Last Modified:

Cannot shrink SQL 2005 Logfile, continues to grow

HELP! I have a SQL 2005 database with a logfile that is 27gb and growing.

I have tried using the GUI to shrink, but it just says that it 'completes successfully' and never does anything to the file.

The database recovery mode is already set to simple. I have tried executing the DBCC ShrinkFile query and while it says that it is completing successfully, it's not. The file not only remains the same size, it continues to grow for some reason.

I'm afraid of detaching the database and deleting this file because I'm worried about uncommitted transactions.

What can I do? I need help!
0
IT Gal
Asked:
IT Gal
  • 5
  • 3
  • 2
  • +3
5 Solutions
 
IT GalAuthor Commented:
By the way, the message I'm getting is:

"Cannot shrink log file 2 (xxxxxxxxxx_Log) because all logical log files are in use."

How do I get around this?
0
 
Anthony PerkinsCommented:
Have you verified the database is or ever was involved in Replication?
0
 
IT GalAuthor Commented:
"Have you verified the database is or ever was involved in Replication?"

It's the only running SQL server we have, so I don't believe its involved in any replication.
0
Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

 
Anthony PerkinsCommented:
Then I am afraid I am out of ideas.
0
 
IT GalAuthor Commented:
Ok, well how about just backing the logfile up somewhere else, detaching the DB and then deleting the logfile and reattach it?

I've had to stop SQL server for the interim because the file just continues growing and I'm out of disk space. I have no idea whats happening.
0
 
Anthony PerkinsCommented:
Ok, well how about just backing the logfile up somewhere else, detaching the DB and then deleting the logfile and reattach it?
If in fact you are using the Simple Recovery Model, then you will not be able to backup the Transaction Log.  Secondly the Transaction Log is an integral part of the database so deleting  the log file is reckless to say the least.  Whatever you do, please please do a full backup of your database before you make matters worse.
0
 
IT GalAuthor Commented:
The database is backed up daily using MozyPro, so I'm not worried about that.

I agree that its potentially reckless, but what other alternative do I have? I can't shrink it, can't delete it, wtf am I supposed to do?
0
 
QlemoC++ DeveloperCommented:
If nothing helps, I suggest to rename the DB, back it up and recreate the original DB from backup. Make sure you also rename the "old" DB files, so there will be no filename conflicts with the restored one.

Are you certain the DB shows to have free log space in that 27 GB?
0
 
Scott PletcherSenior DBACommented:
Woah!  Don't do anything outside the normal SQL realm yet!

First let's see what, if anything, SQL says is preventing it from truncating log records:


SELECT
    log_reuse_wait_desc,
    state_desc,
    recovery_model_desc,
    name --for verification that we're looking at the right db
FROM sys.databases
WHERE
    name = N'<your_db_name_here>'
0
 
Scott PletcherSenior DBACommented:
If you're getting into emergency territory, and you have additional disk space on another drive, add a log file to the db to keep your current drive from filling and causing all kinds of problems.


ALTER DATABASE <your_db_name>
ADD LOG FILE ( NAME = your_db_name_log2, FILENAME = 'd:\full\path\on\new\drive\your_db_name_log2.ldf', SIZE = 2GB, FILEGROWTH = 50MB )
0
 
Kernel_Recovery_ToolsCommented:
0
 
RRobinhoCommented:
Perform the bellow operation:

•      Take a full backup of your database
•      Take transaction-log backup of your database frequently like in every Half an hour so that log file will not continuously grow
•      Shrink if you do not have any free space. You can perform this operation manually if required.

NOTE :  Most of DBAs suggest to avoid shrinking database because when you shrink the database to gain space keeping in mind it will help to increase in performance, but in fact it leads to increase in fragmentation which reduces the performance.
0
 
QlemoC++ DeveloperCommented:
RRobinho,

The Asker already told us (in the original question) that the DB is in Simple recovery mode - no Tranaction Log backup hence.
0
 
IT GalAuthor Commented:
Thanks everyone. It turned out that replication was, in fact, turned on. Something weird must have happened with the replication trying to catch up or generating bogus logs, because its been that way for a long time and this issue never occurred before.

Anyway, a normal shrink was possible after just stopping replication. I'll just split points evenly for everyone that offered a possible solution. Thanks.
0
 
Kernel_Recovery_ToolsCommented:
Thanks pir8matt for choosing us.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

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