Size issues with your repository Clean up the logs and get more space

Clean logs in the repository

Sometimes the repository database become very large. This is normally due to the logs. Thankfully there is some ways to remove old data.

Clean the execution log

It can be removed from the logs in the Repository Administration Tool. A period needs to be chosen as well. Ideally choose every thing until the first of January of the current year.

When a period have been chosen, it shows you the data and projects. It is possible to specify what project is used as well.

To select all of them. Start by marking the bottom line, then go to the top line and mark that while pressing shift. Now press the check box and all lines are chosen and they can be deleted.

Other logs

We previously had a request where cleaning up the schedule logs were not enough. It was still too big. We have a system table database that is called sysssislog and it contains data regarding all executions where ssis is used and is one of the largest tables in the repository.

It is possible to shrink this as well, even though it is a more advanced job. I have a script that removes all fields not containing error messages.

delete from dbo.sysssislog where event <> 'OnError'

It just needs to be executed against your repository and it will remove all lines that does not contain error information.

Was this article helpful?
1 out of 1 found this helpful


  • 3
    Stuart Cuthbertson

    I would like to echo @Rasmus's request from April 2018. Knowing how to clean the Execution Log manually as described above is helpful, but does not go far enough for us.

    I would also like to be able to set up an automated batch job/task of some sort to do this periodically (e.g. every week or month), picking any logs older than <N> days or weeks. 

    I am confident creating such a task via an MS SQL Server Agent Job, but I would want an assurance from TX support staff that this would be safe, appropriate and supported, with confirmation of exactly which tables can be targeted. 

  • 3
    Rasmus Remmer Bielidt

    Thanks for the guide, it is very helpful.

    In our case it is not the database space that is the problem, rather the VERY long time taken to open up the execution log on objects that are frequently executed.

    How can this be set in a batch job?

    Is it enough to delete the obsoleted records in the following tables:


    I suppose this could be done with a script running with appropriate intervals.



  • 2
    Jan De Dycker

    Another shout here for this feature request, would love to have it automated.

    A simple script in this KB we could copy-paste would be a good temporary fix imho.

  • 1
    Andri Páll Heiðberg

    Same here.

    When the execution logs become an issue the GUI is not able to handle the cleanup. Having a script with some options to clean up the execution logs correctly outside the UI is necessary.

    Edited by Andri Páll Heiðberg
Please sign in to leave a comment.