First of all, a good backup strategy should prevent "out of control"
transaction log growth.

With that said, you should be able to use DBCC SHRINKFILE to shrink the
transaction log file. Read up on its usage within Books Online (within the
SQL Server program group).

--
Keith


"Roy Goldhammer" <roygoldh (AT) hotmail (DOT) com> wrote

Hello there

I have huge place with huge database

It's log file is growing very fast

Is there a way to shrink it from time to time or remove old changes?

Have a look at these:

http://www.nigelrivett.net/Transacti...leGrows_1.html Log File issues
http://www.support.microsoft.com/?id=317375 Log File Grows too big
http://www.support.microsoft.com/?id=110139 Log file filling up
http://www.mssqlserver.com/faq/logs-shrinklog.asp Shrink File
http://www.support.microsoft.com/?id=315512 Considerations for Autogrow
and AutoShrink
http://www.support.microsoft.com/?id=256650 INF: How to Shrink the SQL
Server 7.0 Tran Log
http://www.support.microsoft.com/?id=272318 INF: Shrinking Log in SQL
Server 2000 with DBCC SHRINKFILE
http://www.karaszi.com/SQLServer/info_dont_shrink.asp Shrinking
considerations


--
Andrew J. Kelly SQL MVP


"Roy Goldhammer" <roygoldh (AT) hotmail (DOT) com> wrote

By the way, if you don't care about your transaction log at all you can set
the recovery model to simple. I would not suggest doing that for production
databases, however. Transaction logs allow you to recover the transactions
that happened since the last database backup.

--
Keith


"Keith Kratochvil" <sqlguy.back2u (AT) comcast (DOT) net> wrote