I'm doing a bit of maintenance and have noticed my Content Manager event log database (specifically the dbo.EventLog
table) is getting quite large (2million rows taking 1.2Gb).
How do I clean it up?
Tridion Stack Exchange is a question and answer site for Tridion developers and administrators. It only takes a minute to sign up.
Sign up to join this communityI'm doing a bit of maintenance and have noticed my Content Manager event log database (specifically the dbo.EventLog
table) is getting quite large (2million rows taking 1.2Gb).
How do I clean it up?
In the maintenance guide which I wrote somewhere in 2004 for the event log database we gave a SQL statement which you could use to clean it up, as this is the only database where you are allowed to manually clean up (it's content has no influence to the CM server). Julian Wraith also mentioned the same in his article on SDL Tridion World
TRUNCATE TABLE EVENTLOG;
It's very basic, and completely empties the logging table. So as David mentioned, whether you can use is this depending on your business requirements.
Also nice to note perhaps is that in version 2013, this database is completely dropped.
According to LiveContent you should consult your database vendor's documentation to learn how to schedule regular cleanups of the logging database.
In other words, dependent on your business requirements on how long logs need to be kept, you can schedule a task or process to truncate the data or drop & recreate the table/database before it grows beyond capacity. This would most likely end up being something like a simple SQL script.
bin\PurgeTool.exe
) that doesn't require me to write a script. We are talking about the Tridion Event Log Database, not the transaction logs right?
Apr 19, 2013 at 14:29