Sitecore Stack Exchange is a question and answer site for developers and end users of the Sitecore CMS and multichannel marketing software. It only takes a minute to sign up.
Sign up to join this community
Is there any special procedure to clear up large log files in Sitecore databases? Our integration server has a huge (25GB) log file which I would like to dispose of, but not sure of the procedure.
On an aside, is a very large log file symptomatic of any particular problems?
A very large log file is symptomatic of the problem of no backups taking place. Under normal circumstances SQL log files get truncated on backup.
It is quite normal that a CI environment gets quite many updates, and if your SQL is running in "Full" mode, this will grow your transaction log.
I would propose setting it to "simple". It will be slightly quicker and you'd not have unlimited growth.
Full Recovery Model without log backups is bad.
So, that's the most common reason for uncontrolled log growth? Answer: Being in Full Recovery mode without having any log backups.
This happens all the time to people.
Why is this such a common mistake?
Why does it happen all the time? Because each new database gets its initial recovery model setting by looking at the model database.
Model's initial recovery model setting is always Full Recovery Model - until and unless someone changes that. So you could say the "default Recovery Model" is Full. Many people are not aware of this and have their databases running in Full Recovery Model with no log backups, and therefore a transaction log file much larger than necessary. This is why it is important to change defaults when they don't work for your organization and its needs)
It depends how you've set up your database. You can set the recovery model to simple to get rid of most of the log file content. Go to the database with SQL Management Studio, right click on the database and select properties. In the popup, select the Options tab and change the recovery model accordingly.
Alternatively, you can do this with a SQL command as well:
ALTER DATABASE YOURDB SET RECOVERY SIMPLE;
If you don't want to fiddle with the recovery model, then you'll need to take a backup to flush the database transaction log.
Afterwards, you may need to shrink the database.
DBCC SHRINKDATABASE (YOURDB, 10);
GO
