I have several databases for which the log file keeps growing and the VLF's are not being released and are getting into a very large number that is impacting performance. I am running TLOG backups every hour and full backups every night and they are successful. I have even issued a manual CHECKPOINT on the database, ran a LOG backup and then checked the DBCC LOGINFO command the all of the VLF's are still Status of 2.
As per MS's BOL I have even ran the backup a couple of times but no such luck.
I do know that a Jr. DBA here ran a KILL command on an errant process (infinite loop) on a few of these DB's and I saw this KB article http://support.microsoft.com/kb/317375 and it talks about the KILL statement possibly leaving the transaction uncommitted becuase the transaction cancellation occurs, but it does not roll back; therefore, SQL Server cannot truncate every transaction that occurs after this because the aborted transaction is still open but I did a DBCC OPENTRAN and there are no open transactions.
Any thoughts on how to get this back under control or am I just going to have to bite the bullet and take this DB offline and create a new log in order to get the VLF's back to normal?