We have an application provided by an outside vendor that utilizes a SS 2000 database. The database data file is small (346MB) but the log file grows rapidly until it fills up the disk. It increases by about 5GB/day. The vendor is unable to explain why.
The recovery model is full, autogrowth is set to grow by 10MB, unrestricted growth. A full backup is performed on Sunday and a transaction log backup is performed Monday thru Sat. I noticed in the error log that the transaction log backup was failing because
there was not enough room to create the backup. I performed a BACKUP LOG with TRUNCATE ONLY and then shrunk the log file to 100MB. It stayed at that size for the day and then started to grow again at a high rate. Any thoughts on what the issue might be? I
guess I may have to change the recovery model to simple but I would prefer not to do this as it is a production application that I would like to be able to do a point in time recovery if needed.
↧
