Log file very very big

Posted on 2003-11-24
Last Modified: 2012-06-27
Hi all xperts,
I'm runnig Sql Server 2000 and my log file suddenly grew up to 17GB!!!. I have ran the Shrink Database command via Enterprise Manager and  the Backup Log too (with Truncate_Only option). After that the log file shrunk down 3 GB, now it has 14 GB. What should I do???. Need help please.

Thanks in advance
Question by:EBatista
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
LVL 34

Expert Comment

ID: 9813276
See what transactions that are running making the log file big (sp_who or sp_who2 in query analyzer).  If you don't need point in time recovery, change the database recovery mode to simple or bulk logged.


Assisted Solution

kauf earned 50 total points
ID: 9813792
if the transaction log is primary you probably wont have a chance to shrink it. (as far as i got)
did you try following?

and after that shrinking it? (this will clear the t-log and allow you to resize, but resize is not allowed on primary t-logs, just an secondaries)

the last time i had this problem i had to detach db, and re-attach after moving the t-log somewhere else (probably not a good method to do :)).
LVL 10

Author Comment

ID: 9813797
albert, the sp_who dont show nothing strange, everything seems to be ok.
and yes,  I need point in time recovery.
I cant be sure right now if this issue come suddenly or it was a more slower process that I dont realize.
Edgartown IT Case Study

Learn about Edgartown's quest to ensure the safety and security of the entire town's employee and citizen data. Read the case study!

LVL 34

Expert Comment

ID: 9813832
Do you have any DTS jobs or import functions that happen on your database?  Any big deletes or inserts?

You can also run Profiler to capture SQL traffic for a while to figure out what's going on.

LVL 75

Expert Comment

by:Anthony Perkins
ID: 9815257
Please let me know if you need help maintianing this old open question:

LVL 10

Author Comment

ID: 9817250
kauf, I have also done the Backup log with truncate_only method and then shrink the database, after that  nothing happen with the t-log. Should I detach the db exactly how you did. I cant think there isnt any other cleanest way.

arbert: I ran a DTS package when I migrated from DBFs data files to SQL server, but it was several month ago and I have never used it again.

LVL 34

Accepted Solution

arbert earned 75 total points
ID: 9817765
Well, if you really don't know why the log file is growing, I would run profiler for a while and see what's causing the transactions.


Expert Comment

ID: 9818761
Have you configured any replications...or as Arbert has said capture the events in the profiler and check. Also "truncate at check point" option will truncate the log.
LVL 34

Expert Comment

ID: 9819008
rsrsm, "truncate on check point" is a sql server 7.0 option....Doesn't apply to 2000 (bulk logged or simple recovery mode is about the same)....

Expert Comment

ID: 9819575
There is a simple problem with 'truncate at checkpoint' option or bulk logged or simple recovery options if you will.

The problem is a Checkpoint does not occur until the atomic transaction is completed.  In other words, the atomic transaction that is building the log size will not be truncated with this option.  So, it does not matter what you do - your log size is going to grow.

A simple example - Update all rows of a 5 million row table.  It is an implicit transaction and the checkpoint does not occur until this update is completed.  Even if it occurs, the checkpoint is put prior to this transaction and the log is truncated only till that part.

In other words, you don't have choice but to look for the culprit SQL that is filling up the log.

Good luck..
LVL 10

Author Comment

ID: 9820196
ok guys I did it, finally my T-Log is now 4MB again, this is what I did:
First I ran BACKUP LOG [DATABASE] WITH TRUNCATE_ONLY option from Query Analizer,
then I made a complete database backup,
then I made a normal backup to the T-Log file within Enterprise Manager (the resulting backup file was 180MB),
and finally I ran the Shrink Database command with "Move page to beginning of file before shrinking" option checked, and this time I have selected only the T-Log file for shrink, in "Shrink file to" I wrote the minimum value suggested for this file.

That was all, I dont know if all that steps are necessary or not, I just write what I did,  but I this issue really stressed me a lot.

Thanks you for your time

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
Can we attach PDF to table 2 46
SQL Server for XML PATH giving wrong results. 6 59
store vs query adhoc - no show rows 4 37
Restore a log backup compressed 3 16
Introduction SQL Server Integration Services can read XML files, that’s known by every BI developer.  (If you didn’t, don’t worry, I’m aiming this article at newcomers as well.) But how far can you go?  When does the XML Source component become …
Introduction In my previous article ( I showed you how the XML Source component can be used to load XML files into a SQL Server database, us…
Familiarize people with the process of retrieving data from SQL Server using an Access pass-thru query. Microsoft Access is a very powerful client/server development tool. One of the ways that you can retrieve data from a SQL Server is by using a pa…
Via a live example, show how to backup a database, simulate a failure backup the tail of the database transaction log and perform the restore.

732 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