Excessive amount of "m2m_blacklist_search_suggestion" records related to sys_update_xml and sys_update_version recordsIssue 🔹 By default, "m2m_blacklist_search_suggestion" table has update-set tracking enabled; there is no suppression property configured, so every data change is versioned. Since "m2m_blacklist_search_suggestion" is auto-populated daily by the "Build Search Suggestions" job and provides no configuration value, suppressing version tracking will simply prevent thousands of meaningless sys_update_version records from accumulating.🔹 Please note that by suppressing version tracking, you lose historical config data for that table. If someone ever needs to audit how the blacklist changed, it won't be visible in sys_update_version. However, this is a very low risk but I just wanted to bring it to your attention.ReleaseAll releasesResolution🔹 Please refer to the following documentation to see how to suppress version tracking (this solution addresses only "sys_update_version" table):https://www.servicenow.com/docs/bundle/zurich-application-development/page/build/team-development/task/t_SuppressVersions.html  🔹 We need to remove the dictionary attribute "update_ sync" for "sys_update_xml" table. The following script will modify "update_sync" attribute of "m2m_blacklist_search_suggestion" table: var gr = new GlideRecord('sys_dictionary'); gr.get('ed7cc2ecc3811110a5592c4ce0013114'); gr.attributes = "update_synch=false,no_audit_delete=true"; gr.setWorkflow(false); gr.update();