Hello - I have a SQL Server 2005 Enterprise instance with the recovery mode set to SIMPLE.
It would run out of space on a 500 GB drive that it was sharing with the mdf, so I moved the mdf.
Today the log grew to fill the 500 GB drive.
Its a product called COMPUWARE.
If I limit the size of the transaction log, will that help with filling the drive but just end up with a full log?
Do I need to issue checkpoints by creating a job?
How do I avoid the log growing in Simple mode? The advice I found to add more space did not work. Its a 3rd party software and I can't change the code.
Any advice appreciated
Jaon & Jack are correct. Also check on what SQL Server is waiting before it can truncate the log.
Use this query ..
--WHERE [name] = N'DB_Name';
If you have large active transactions or replication, TLog doesn't get truncated immediately and it grows to a large size.