Why does my SQL Server log show that it's still full? - I have truncated it.

A. A. The reason for this is that all the tools that interrogate logspace - e.g. dbcc sqlperf, sp_spaceused and SQL EM all just look at the systemcatalog information in sysindexes - the dpages column. In SQL 6.5 and earlierthis information is NOT kept up to date, so it is constantly wrong. The reasonit is not kept updated is that it would cause a performance bottleneck.

The easiest way to correct the information is :-
dbcc checktable(syslogs)
go
checkpoint
go

The information will then be correct until the next update/delete/inserttransaction is issued.

If your log REALLY is full - i.e. you're getting a 1105 error on syslogs,then try a "dump transaction dbname with no_log". If this stilldoesn't fix it, then one of the following is occuring.

See Q110139 and Q184499 for more information on syslogs filling up and howto resolve them.