AutoShrink Database Transaction Log

I am using SQL Server 2000 Enterprise Edition with SP3A.
Is there away that can I autoshrink the database
transaction log and not the database? Is there a command
I can run periodically to shrink the transaction log file?
Is there away I can tell which process caused the database
transaction log to grow so large?
Thank You,
DanShrink implies actually reducing the amount of space used by the actual OS
file. Shrink does not mean freeing up space within the transaction log
itself. You probably understand this, but I wanted to make the distinction
clear since generally speaking... you shoud NEVER autoshrink an important
production database. Why? Shrinking a file can create any number of
bottlenecks. Shink operations in large systems should be planned operations
in a managed production enviornment. And... Since you're running SQL EE...
you're probably running something very big. Otherwise you paid 4X more for
your license than you should have paid...
There is not a check box setting to autoshrink the log and not the database.
However, it would be easy to create a job to do this periodically that
issues dbcc shrinkfile. Again, I wouldn't recommend this...
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Dan" <anonymous@.discussions.microsoft.com> wrote in message
news:129a301c4431f$a28949d0$a401280a@.phx
.gbl...
> I am using SQL Server 2000 Enterprise Edition with SP3A.
> Is there away that can I autoshrink the database
> transaction log and not the database? Is there a command
> I can run periodically to shrink the transaction log file?
> Is there away I can tell which process caused the database
> transaction log to grow so large?
> Thank You,
> Dan|||Here are a couple of good KB articles that should provided you with the
information necessary to shrink your tranlog
http://support.microsoft.com/defaul...8&Product=sql2k
http://support.microsoft.com/defaul...kb;EN-US;256650
As far as knowing what application is causing your tranlog to grow becomes a
little more difficult. You really need to know what applications you have
running against your database and how they are commiting transactions. Here
is an article that might help you understand why the transaction log grows.
Hopefully this will give you some ideas on what it is that is causing your
problems.
http://support.microsoft.com/defaul...5&Product=sql2k
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Dan" <anonymous@.discussions.microsoft.com> wrote in message
news:129a301c4431f$a28949d0$a401280a@.phx
.gbl...
> I am using SQL Server 2000 Enterprise Edition with SP3A.
> Is there away that can I autoshrink the database
> transaction log and not the database? Is there a command
> I can run periodically to shrink the transaction log file?
> Is there away I can tell which process caused the database
> transaction log to grow so large?
> Thank You,
> Dan