November 10, 2006 at 12:03 pm
I have a database (actually 4) that have abnormally large log files. For example, there is one database that has a 102 MB mdf file and 6.7 GB ldf file. The recovery model is simple. It has been this way for at least three days. If I try to shrink the log file, I can see that there is only 1% free space. So it appears that something is not truncating correctly. None of these databases see large transactions.
I even tried changing the recovery model to full, performing a full database backup, perform a transaction log backup (made sure that 'truncate the transaction log' was checked), and the free space was still only 1% free.
Later today, I will detach the db, delete the log file, and then re-attach the db to resolve this issue. But I have seen it occur once or twice on other servers. What could be causing this issue?
November 10, 2006 at 6:28 pm
I think uncommitted transaction running long time lead to this. You can try to find is it exist?
November 13, 2006 at 8:21 am
The active connections to these databases only occur maybe once or twice a day and so far, I haven't seen any long running transactions.
November 14, 2006 at 5:12 am
Can you please check error log and see if below is applicable?
FIX: Automatic checkpoints on some SQL Server 2000 databases do not run as expectedhttp://support.microsoft.com/kb/909369/en-us
November 14, 2006 at 9:21 am
Do you realize that you are in the SQL 2005 Admin forum? That KB only applies to SQL 2000.
Matt
November 14, 2006 at 3:42 pm
I have only seen long running queries cause this.
November 15, 2006 at 6:10 am
Matt,
My apologies.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply