One of our customers has been having disk spaces issues, this has not been helped by the fact that they have a large SQL Server 2000 log file for one of our databases. I couldn't work out why it was so large, as our automated backup should truncate the log files on a daily basis. What I didn't know was that once a log file has disk space allocated to it, it doesn't give it back - instead you must run DBCC SHRINKFILE(databasename_log, 2). The customer had run without backups working for several weeks, and so consequently the log file had grown quite large, and a larger than necessary amount of disk space had been allocated.
comments powered by Disqus