--- sourceDocument: Brazil ServiceNow AI Platform Capabilities sourceDocumentLink: https://www.servicenow.com/docs/r/servicenow-platform Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil ServiceNow AI Platform Capabilities ft:clusterId : - platcap bundleId : - platcap workflow : - Platform --- # Managing CMDB data deletion # Managing CMDB data deletion {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Managing CMDB data deletion The Integration Commons for CMDB (sncmdbintutil) store app provides methods to manage deletion of Configuration Management Database (CMDB) records that have been removed from source third-party applications. This ensures that the CMDB stays synchronized by removing outdated or deleted Configuration Items (CIs) from the CMDB tables. Show full answer Show less ## Post-script method This method checks the **Source \[sysobjectsource\]** table for CIs not updated during the last import run for a specific source feed and removes them synchronously from the target CMDB tables one record at a time. It uses a **RecordRemoval** script to support different deletion strategies: * **Hard deletion:** Permanently deletes records from the CMDB, making them unrecoverable---used when data is no longer needed. * **Soft deletion:** Marks records as deleted without removing them, preserving historical data and allowing recovery. * **Optimized soft deletion:** Utilizes the Identification and Reconciliation Engine (IRE) with a specialized table and reconciliation rules for efficient management of deleted records. Administrators can adjust the default limit of 100 records held for optimized soft deletion by creating and setting the **sncmdbintutil.irepayloaditemssize** integer system property within the Integration Commons for CMDB app. This post-script method is commonly used by most Service Graph Connectors to manage CMDB record removal. ## Transform map-based method This method also checks the **Source \[sysobjectsource\]** table for non-updated CIs but removes them using a multi-threaded deletion approach. It concurrently deletes all non-updated CIs within an import set, improving data processing speed. Key components include: * The **Integration Commons Remove Record \[sncmdbintutilremoverecord\]** staging table, which tracks details of non-updated CIs like discovery source, source feed, target record sysid, and target table name. * An on-start script within the Remove Record Transform Map that deletes the records from the target CMDB tables. This method enables faster processing by handling multiple deletions concurrently and is used by specific Service Graph Connectors, such as the SG-Tanium Remove Software data source in the Service Graph Connector for Tanium. The Integration Commons for CMDB (sn_cmdb_int_util) store app uses post-script and transform map methods to remove imported Configuration Management Database (CMDB) records that were deleted later from the source third-party application. ## Post-script method {#cmdb-integ-record-removal__section_tkt_5cb_mbc} The post-script method checks the Source \[sys_object_source\] table for configuration items (CIs) not updated in the last run for a specific source feed. It then removes any non-updated CIs from the associated target CMDB tables synchronously, handling the removal of target records one at a time. Most Service Graph Connectors use the post-script method to manage the removal of any CMDB records. The post-script method uses the RecordRemoval script to handle various record deletion strategies. Hard deletion involves permanently and completely removing records from the CMDB, making them unrecoverable and suitable for data that is no longer needed. Soft deletion marks records as deleted without actually removing them from the CMDB, allowing for potential recovery and preserving historical data. Optimized soft deletion, managed by the Identification and Reconciliation Engine (IRE), enhances this soft deletion approach by using a specialized table, such as the extension attributes table, and applying reconciliation rules to manage deleted records more efficiently. By default, the table can hold up to 100 records at a time, but as a user with the admin role, you can adjust this limit by setting the sn_cmdb_int_util.ire_payload_items_size system property. This property is not available by default and you must create this property of type integer within the Integration Commons for CMDB (sn_cmdb_int_util) store app. For more information, see [Add a system property](https://www.servicenow.com/docs/access?context=t_AddAPropertyUsingSysPropsList&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US). ## Transform map-based method {#cmdb-integ-record-removal__section_bvk_vcb_mbc} The transform map-based method checks the Source \[sys_object_source\] table for configuration items (CIs) not updated in the last run for a specific source feed. It then utilizes the multi-threaded deletion approach to remove any non-updated CIs from the associated target CMDB tables concurrently, handling the removal of all target records within an import set at once. Multiple import sets are created to store target record data within the Integration Commons Remove Record \[sn_cmdb_int_util_remove_record\] staging table enabling multi-threaded deletion of records. Therefore, reducing the data processing time. The Integration Commons Remove Record \[sn_cmdb_int_util_remove_record\] staging table tracks non-updated CIs by storing target record details including the discovery source, source feed, target table sys_id, and target table name of these CIs. The on-start script defined within the Remove Record Transform Map then deletes the records from the associated target tables. The transform map-based method is used by a Service Graph Connector to improve the data processing time. For example, the SG-Tanium Remove Software data source within the Service Graph Connector for Tanium removes software data using the transform map-based method. See [Service Graph Connector for Tanium](https://www.servicenow.com/docs/M4JJ98l_wgVg~lFnL15rQQ "Use the Service Graph Connector for Tanium to bring in hardware, software, and software usage data from a Tanium environment into your ServiceNow instance.").