Hi Phil,

You must issue BACKUP LOG in order to trigger log truncation. The log backup
which is done as part of BACKUP DATABASE does not include truncation.

The more often you back the log up, the smaller it can be - and the longer &
more hassle it will take to roll the database forward if you need to recover
- standard kind of trade-off.

Check under BACKUP LOG in BOL.

Charles

> -----Original Message-----
> From: Phil Shuttleworth [SMTP:Phil.[Email Address Removed] Sent: Tuesday, November 19, 2002 3:41 PM
> To: LazyDBA.com Discussion
> Subject: Transaction log space
>
> Hallo DBA's,
>
> I have a problem with one of our SQL Server 7.0 databases, in that the
> Transaction log seems to be growing out of control.
>
> The figures are as follows:-
>
> Data space Used Free Total
>
> Database 416.13 MB 26.88Mb 443.00 MB
>
> Transaction log space 2,652.24 MB 126.50 MB 2,778.74 MB
>
> As you can see, the Transactiion log space (used) is about 6 times the
> size
> of the Data space (used), and the transaction log free space is also out
> of
> proportion to a similar amount. This has been growing steadily over the
> past few weeks.
>
> Does anyone know how to reduce this to a reasonable size, please?
>
>
> Phil Shuttleworth
>
> DBA, IT Services
> University of Central England, BIRMINGHAM B42 2SU, UK
> Tel: +44(0)121 331 5664 Fax: +44(0)121 356 2875
> E-mail: Phil.[Email Address Removed]
>
> ---------------------------------------------------------------------
> TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
> To unsubscribe, e-mail: mssqldba-[Email Address Removed] For additional commands, e-mail: mssqldba-[Email Address Removed]MS Sql Server LazyDBA home page