Skip to main content

When archiving old records in FSM, we came across the below tables which has high number of rows in DB. 

Table                                                      Number of rows 

MX_U                                                     3853707649
THREESIXTY_OUTPUT_HISTORY    1203634
PERSON_LOGIN_HISTORY                482363
CONTACT                                              1408553

 

  1. What is the use of table MX_U ? Can we cleanup old records ? 
  2. Is there any built-in cleanup mechanism for  THREESIXTY_OUTPUT_HISTORY and PERSON_LOGIN_HISTORY ?  If no, should we consider cleaning up old records? 
  3. It seems that the CONTACT table also holds the same records as present in TASK_CONTACT table. When archiving, the TASK_CONTACT are getting archived but not from the CONTACT table. How can we archive CONTACT records as well ? 
  1. As quoted from Aaron Sleight:  “That table (MX_U) is used internally for usage tracking purposes that could aid in troubleshooting.  The data does not need to be persisted long term though, so if you are finding that it is consuming too much storage in the database, you can safely truncate the table periodically without fear of doing harm elsewhere.”
  2. There is no built-in mechanism for these two tables, as well as quite a few others.  If desired, you could create a Scheduled Process to periodically delete records of a certain age.
  3. The data in the Contact table is not considered to be transactional, as the Task Contact table is.  You can configure Metadata to archive Contact data if desired, however the archiving process will remove the source data records.  So if those contacts are still valid for the Place, Contact, Product, Project, etc., for which they were created, they would need to be added back when needed.
Terms & ConditionsCookie settings