Best Practices for Deleting Tables and Records

these sections describe best practices and general recommendations to consider prior to deleting database tables identifying the tables to delete docid\ txmg4bqvllhbzlxneo1kcidentifying criteria for deleting tables and records docid\ txmg4bqvllhbzlxneo1kc after you are familiar with these practices and have followed the described recommendations, see the "about archiving and deleting data from the ivanti databases" topic in the in the ivanti service manager online help identifying the tables to delete identifying which tables to delete depends on customer specific criteria in general, deleting primary tables (for example, the incident , task , journal , delete , or other tables) results in the biggest performance improvement some tables are candidates for deleting in most situations table name primary key foreign key description audit business object name parentlink recid multiple tables that contain audit information generated by ivanti service manager the information is used by self service, the workflow engine, and the escalation engine an example table name is audit incident frs data escalation watch parentlink recid contains escalation tracking information frs data workflow instance recid parentlink recid contains workflow execution progress information frs data workflow history workflowinstancelink recid contains workflow execution history information the most commonly deleted transactional data tables are listed in the following table parent business objects have primary keys child business objects have foreign keys business objects that can be both parent and child have primary and foreign keys table name primary key foreign key description attachment recid parentlink recid contains attachments displayed in the attachments tab for major business objects (such as incident) displays and manages all documents or files that are related to a particular business object contains the file name, file path, creator's name, and creation date fusionattachments recid a system business object stored inside an attachment containing the actual attachment block frs myitem secondparentlink recid contains my item records the records contain references to incident, service request, and approval requests displayed in the my items tab in self service journal parentlink recid contains notes, email messages, and voice activities displayed in the activity history tab for major business objects (such as incident) task recid parentlink recid contains task information that is displayed in the task tab for major business objects (such as incident) information pertains to general, computer provisioning, and software installation tasks identifying criteria for deleting tables and records you should only delete inactive records do not delete active records that contain data that can be referenced there are two ways to determine whether a record is inactive based on time only select a cutoff date or time, and if the record was not created or modified after the cutoff date or time, consider it inactive this method is commonly used for records that do not have a lifecycle or different possible statuses (such as the audit history business object) with this method, you specify a date and time to determine if the record is active based on time and status select a cutoff date or time and one or more statuses (or lifecycle stages) if the record was not created or modified after the cutoff date or time, or if the record meets the status criteria that you specify, consider it inactive this method is commonly used for records that have a lifecycle or different possible statuses (such as the task business object) with this method, you specify both a date and time and a status to determine if the record is active deleting records and tables from the ivanti service manager databases for information about deleting records and tables from the ivanti service manager database, see the "about archiving and deleting data from the ivanti databases" topic in the in the ivanti service manager online help