Best Practices for Deleting Tables and Records

These sections describe best practices and general recommendations to consider prior to deleting database tables:

•Identifying Criteria for Deleting Tables and Records

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.