Liveside_log.ldf TOO LARGE?

Hi,
I don't usually support SQL 7 but there is a file on the
server called liveside_log.ldf that is taking over 57 GB
and the disk is almost full. What are the chances of this
being a corrupt file?
thanks,
RandyRandy,
Just because it is 57GB doesnt make it corrupt <g>The ldf files are the
transaction log file of a SQL Server database.Most probably the database is
'liveside'.The transaction log is of that size because of the lack of any
maintenance measure to keep its growth down.The ldf file wont automatically
shrink or truncate unless you take steps for it.Since its allowed to consume
as much space as required, it has grown to this far.
To truncate ( or empty ) a transaction log, you need to take regular log
backups.But if your system doesnt care for log backups, then make sure to
check the option "Truncate log on checkpoint" in the database properties in
enterprise manager.You can even empty the log by doing : 'backup log
<databasename>with truncate_only' .By doing this, the log would be truncated
or emptied at every checkpoint.Please note that these wont reduce the
physical size of the file.For that, you need to shrink it.The below articles
would help you with that:
INF: How to Shrink the SQL Server 7.0 Transaction Log
http://support.microsoft.com/support/kb/Articles/q256/6/50.asp and/or
www.sqlserverfaq.com and search for "sql7shrinklognowork.txt"
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Randy Hughes" <hughesrandall@.hotmail.com> wrote in message
news:245201c373f1$340cc2f0$a301280a@.phx.gbl...
> Hi,
> I don't usually support SQL 7 but there is a file on the
> server called liveside_log.ldf that is taking over 57 GB
> and the disk is almost full. What are the chances of this
> being a corrupt file?
> thanks,
> Randy|||"Dinesh.T.K" ,
Thanks for your rapid response. I will follow up with this
and see what happens.
Thanks again,
Randy
>--Original Message--
>Randy,
>Just because it is 57GB doesnt make it corrupt <g>The ldf
files are the
>transaction log file of a SQL Server database.Most
probably the database is
>'liveside'.The transaction log is of that size because of
the lack of any
>maintenance measure to keep its growth down.The ldf file
wont automatically
>shrink or truncate unless you take steps for it.Since its
allowed to consume
>as much space as required, it has grown to this far.
>To truncate ( or empty ) a transaction log, you need to
take regular log
>backups.But if your system doesnt care for log backups,
then make sure to
>check the option "Truncate log on checkpoint" in the
database properties in
>enterprise manager.You can even empty the log by
doing : 'backup log
><databasename>with truncate_only' .By doing this, the log
would be truncated
>or emptied at every checkpoint.Please note that these
wont reduce the
>physical size of the file.For that, you need to shrink
it.The below articles
>would help you with that:
>INF: How to Shrink the SQL Server 7.0 Transaction Log
>http://support.microsoft.com/support/kb/Articles/q256/6/50
.asp and/or
>www.sqlserverfaq.com and search
for "sql7shrinklognowork.txt"
>
>--
>Dinesh.
>SQL Server FAQ at
>http://www.tkdinesh.com
>"Randy Hughes" <hughesrandall@.hotmail.com> wrote in
message
>news:245201c373f1$340cc2f0$a301280a@.phx.gbl...
>> Hi,
>> I don't usually support SQL 7 but there is a file on the
>> server called liveside_log.ldf that is taking over 57 GB
>> and the disk is almost full. What are the chances of
this
>> being a corrupt file?
>> thanks,
>> Randy
>
>.
>