Log file very very big

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
LVL 10
Who is Participating?
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.

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.

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 :)).
EBatistaAuthor Commented:
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.
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

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.

Anthony PerkinsCommented:
Please let me know if you need help maintianing this old open question:


EBatistaAuthor Commented:
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.

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.


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
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.
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)....
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..
EBatistaAuthor Commented:
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
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.