sql server msde:
Hi NG
We have experienced that the LDF file grow out of proportions. In Microsoft
Knowledge Base we have found some descriptions on how to shrink the file.
Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE
http://support.microsoft.com/kb/272318/EN-US/ How to Shrink the SQL Server 7.0 Transaction Log
http://support.microsoft.com/kb/256650/EN-US/ This works okay but we would like to find the root of the problem instead of
treating the symptoms. Microsoft Knowledge Base describes a couple of issues
that can cause the LDF file to grow. One cause I noticed in all the articles
was an unfinished transaction. In our application we let the system issue
BEGIN TANS and COMMIT statements. I was just wandering if can happen even if
we don't use transactions.
Causes of SQL Transaction Log Filling Up
http://support.microsoft.com/kb/110139/EN-US/ Reasons Why SQL Transaction Log Is Not Being Truncated
http://support.microsoft.com/kb/62866/EN-US/ Transaction Log Partially Truncated
http://support.microsoft.com/kb/80629/EN-US/ Transaction Log Grows Unexpectedly or Becomes Full on SQL Server
http://support.microsoft.com/kb/317375/EN-US/ After reading the articles above I still didn't get a clear answer on how to
debug our application and databases.
I was wondering if there is a way (tool) to analyze the transaction log so
we can see if there is an unfinished transaction blocking the log from being
flushed.
All help will be appreciated.
Thnaks
/RasmusW