SDL LiveContent Architect Database Job

In order to avoid performance issues by a growing database, the standard SDL LiveContent Architect Database Job generates new statistics for the database and tries to remove all unused objects.

Introduction

The standard SDL LiveContent Architect Database Job contains the following actions:
  • Update the statistics of the database
  • Basic SDL LiveContent Architect Database Job to cleanup some basic SDL LiveContent Architect objects
  • Cleanup EventMonitor logging
  • Cleanup Search Results
  • Cleanup Baselines
  • Cleanup Revisions

Basic SDL LiveContent Architect Database Job

The basic SDL LiveContent Architect database job groups database actions on basic SDL LiveContent Architect objects.

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

Cleanup 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 two (2) 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 failed events older than 4 weeks. This also removes the logging of all events which are still busy.
The logging of the events is removed using the following algorithm:
  • First process the events which have a parent event and have not changed within the specified period:
    • Delete the successful events
    • Delete the busy events if the parameter DeleteBusy is Y
    • Delete the events which ended with warnings if the parameter DeleteWarnings is Y
    • Delete the failed events if the parameter DeleteFailedEvents is Y
  • Then process all events which have no child events (anymore) and have not changed within the specified period:
    • Delete the successful events
    • Delete the busy events if the parameter DeleteBusy is Y
    • Delete the events which ended with warning if the parameter DeleteWarnings is Y
    • Delete the failed events if the parameter DeleteFailedEvents is Y
  • Finally process the remaining events which no longer have child events and have not changed within the specified period. Normally, these events are the parent events with status CALCULATE.

    Do the following checks for each event
    • Are there any event details with status FAILED?

      Yes, only delete the event if the parameter DeleteFailedEvents is Y.

    • Are there any event details with status WARNING?

      Yes, only delete the event if the parameter DeleteWarnings is Y.

    • If none of the checks above gave result, delete the successful event.

Cleanup Search Results

The standard SDL LiveContent Architect job cleans-up the stored search results which are older than 3 days.

Cleanup Baselines

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

Cleanup 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 SDL LiveContent Architect Database Job.