SYMPTOM:
When using Database Based history list message storage, the size of the DSSCSCONTENT table rapidly grows large in Strategy 9.x.
CAUSE:
The DSSCSCONTENT table stores the "content" for history list messages. When a history list message is exported to a particular format (PDF, Excel etc), the corresponding export content is stored in the database. So if a large number of history list messages are generated for users, and users regularly export from these messages, the size of this table can increase quickly.
To control this size growth, administrators can limit the maximum number of history list messages per user, as well as implement a schedule to clean up old history list messages (which will cause the corresponding export content to be deleted).
Additionally, by default the History List Database feature would also automatically backup report caches that are associated with the history list message to the database. From Strategy 9.0.2 a new setting has been introduced to allow users to select whether the history cache files need to be backed up to the History List database, or whether they can only be retrieved from the file system.
Administrators wishing to verify whether this is the case can check if 'Backup report history caches to database' is selected under Strategy Intelligence Server Configuration > History Settings > General > Repository Type > Database Based:
ACTION:
If the actual history list message cache data does not need to be stored in the database, un-check the 'Backup report history caches to database' check box. This will then utilize the history cache data files stored on the Strategy Intelligence Server disk instead of pulling the data from the database. Note that disabling this setting does not remove existing caches from the History List database.
Users should note that matching only caches only use the file system and are never backed to the History List Database.
