Documentation Center

Content Manager Database Job

In order to avoid performance issues with a growing database, the standard Content Manager Database Job generates new statistics for the database and tries to remove all unused objects.

Introduction

The standard Content Manager Database Job contains the following actions:
  • Update the statistics of the database
  • Basic Content Manager Database Job to clean up some basic Content Manager objects
  • Clean up Background Tasks
  • Clean up EventMonitor logging
  • Clean up Baselines
  • Clean up Revisions
  • Clean up Session Tokens

Basic Content Manager Database Job

The basic Content Manager database job groups database actions on basic Content Manager objects.

The job contains the following steps:
  • Cleaning up orphaned document components
  • Cleaning up objects marked for deletion
  • Correcting the value sequences (if necessary)
  • Correcting the rootword columns (if necessary)

Clean up Background Tasks

In an out-of-the-box installation there are two steps installed:

  • The first step removes the logging of all background tasks successfully finished for more than 1 day.
  • The second step removes the logging of all background tasks that have failed for more than 7 days.

Clean up EventMonitor logging

Background tasks, such as publishing and translation management, write their logging in the database. This is the EventMonitor logging.

This logging is cleaned on a regular basis. In an out-of-the-box installation there are three steps installed:
  • The first step removes the logging of all successful events that finished more than a week ago. This also removes the logging of all events which ended with warnings.
  • The second step removes the logging of all busy events older than 4 weeks.
  • The third step removes the logging of all failed events older than 4 weeks.

Clean up Baselines

Since baseline are not explicitly managed anywhere, there is a standard Content Manager job which deletes all unused baselines that are not modified in the last 7 days.

Clean up Revisions

For each change to an object's file level (XML file, image, and so on) a copy of the previous version is kept as a revision. Currently revisions are not explicitly managed anywhere. They are automatically generated and are only visible in the web client. In order to avoid the database growing too large, the revisions of out-of-date objects are removed automatically by the standard Content Manager Database Job.

Clean up session tokens

When a token is submitted to the server, the server returns a cookie with a session token. The validity of this session token is usually around 10 days. A part of this session token is stored in the database, and as it has a significant size, it needs to be cleaned up on a regular basis. The default delay for this cleanup is 20 days.