The issue could simply be due to the drive upon which the SQL transaction logs reside running out of space.
For other ideas see the following Microsoft Knowledge Base articles:
Article ID: 317375 - A transaction log grows unexpectedly or becomes full on a computer that is running SQL Server:
http://support.microsoft.com/kb/317375/en-us
Article ID: 272318 - Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE
http://support.microsoft.com/kb/272318/en-us
Removing or deleting such files is not recommended since this could damage the SQL instance and the files might get recreated again according to this MS KB article:
http://support.microsoft.com/kb/257855/en-us
The logs are not created by QMM, they are a result of SQL configuration.
The issue could simply be due to the drive upon which the SQL transaction logs reside running out of space.
For other ideas see the following Microsoft Knowledge Base articles:
Article ID: 317375 - A transaction log grows unexpectedly or becomes full on a computer that is running SQL Server:
http://support.microsoft.com/kb/317375/en-us
Article ID: 272318 - Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE
http://support.microsoft.com/kb/272318/en-us
Removing or deleting such files is not recommended since this could damage the SQL instance and the files might get recreated again according to this MS KB article:
http://support.microsoft.com/kb/257855/en-us
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy