Show TOC

Database Table MaintenanceLocate this document in the navigation structure

Database tables store logins, and persist configurations, transactions, and session data. Logging tables require regular archiving when traffic volume is high.

The information presented here is intended to help the DBA incorporate application tables into the overall database maintenance plan. As always, regular backups are essential for recovery in the event of unexpected failure.

Note

The DBA should review these guidelines, and define archiving and purging schedules based on company policy.

Table 1: Logging Tables
Table Name Description Archive and Purge
M_CORE_STATUS_LOG Engine logs Purge based on the TIMESTAMP2 column.
M_LOGIN_HISTORY User logins Purge based on the TIMESTAMP2 column.
M_MESSAGE_LOGS Size increases with number of subscribers and traffic Purge based on the TIMESTAMP2 column.
M_MESSAGE_RECEIVERS Size increases with number of subscribers and traffic Purge based on MARKED_DELETED = 1 AND if there are no references in the M_MESSAGE_LOG table.
M_MESSAGE_ATTRIBUTES Number of rows increase with traffic and session data Purge before purging the M_SESSIONS table, and based on the SESSIONS_ID column.
M_SESSIONS Number of rows increase with traffic and session data Purge based on the CLOSED_DATE column.
M_SMAPP_TRANSITION_LOG Number of rows increase with traffic and session data Purge based on the TIMESTAMP2 column.